44net

44net@mailman.ampr.org

3194 discussions

bad ip address?
by Don Moore 09 Aug '13

09 Aug '13

Whoever is operating (if valid) 176.9.140.86 name = ampr-gw.fks-de.ham.lu please cease and desist sending data using the following encap line. 11:30:13.339166 IP 176.9.140.86 > 192.168.1.150: IP 0.0.0.0.5678 > 255.255.255.255.5678: UDP, length 115 (ipip-proto-4) 73, Don - ve3zda

2 1

FW: Ampernet
by Kutche, Jerry (Mitchell) USA 09 Aug '13

09 Aug '13

fyi Looks like we have a another software available that can participate in the Amprnet! coming online soon.. :) 73 Jerry N9LYA Subject: Re: Ampernet On 09/08/13 04:28, Rod McCosker wrote: Paula, We are back from Queensland & XR32 Version D [Alpha Testing] - now works as my Ampernet Gateway 44.136.16.2 - with TinyXP We have to update the Ampernet registery with a few new local entries. There are no AXUDP or IPUDP links setup from the Gateway, only the ENCAP.TXT file It looks like - We may not have a seperate gateway laptop, but integrate the gateway into the main XR32, Will have to think about this. However from VK2DOT-3 the Gateway XR32, we can connect via Ampernet to - ZL2AQY 44.147.38.42 VK6HGR 44.136.204.77 N9LYA 44.48.0.46 regards rod..../// Hi Rod, Are we any closer to seeing the new version ? Regards ..... Peter

2 1

Re: [44net] "Invalid Gateway Address"
by Pieter Luteijn 09 Aug '13

09 Aug '13

How are you trying to use this address? Could it be that your inadvertantly trying to set your default gateway to this address. An off-subnet default gateway is usually 'invalid'.. P. Sent from a mobile, sorry for any typoes... -------- Original message -------- From: Neil Johnson <neil.johnson(a)erudicon.com> Date: 2013/08/08 22:11 (GMT+01:00) To: AMPRNet working group <44net(a)hamradio.ucsd.edu> Subject: [44net] "Invalid Gateway Address" When I try to add it, it says "Invalid Gateway IP Address" Neil Johnson -N0SFH

3 2

"Invalid Gateway Address"
by Neil Johnson 08 Aug '13

08 Aug '13

I just received a static IP from my ISP, but I can't use it for a gateway. When I try to add it, it says "Invalid Gateway P Address" The address is 108.160.233.78. Does it have to be pingable ? Any ideas ? -- Neil Johnson -N0SFH http://erudicon.com

1 0

Re: [44net] Why rip44d?
by Brian Kantor 07 Aug '13

07 Aug '13

Seems to me that encap routes learned by rip44 should be fairly persistant - I'd say they shouldn't expire for a day or three or more. Perhaps a week? Unless replaced by a newer route for the same subnet, of course. That way if the rip sender (amprgw) should happen to go away for a while, things will still function. And you'd have time to switch over to using the encap file if the outage were to be prolonged. There's no harm in having a dormant route in your table for a while when a gateway permanently goes away. What's the maximum rip44 route expiration time setting? You could, of course, decide to NEVER expire them. With daemon modification, they could be persistent across reboots and only purged when manually selected. - Brian

3 4

rip44d / kernel multicast support
by Heikki Hannikainen 07 Aug '13

07 Aug '13

I think the lack of multicast support in some Linux kernel builds makes the Perl rip44d fail for some users. Linux 2.6 certainly supports multicast, it's been in the kernel for a long while (at least in kernel 1.2 it was there, and probably before that). Some distributions apparently haven't compiled in the multicast code. If you're having problems with rip44d not receiving RIP packets, and you're not one of those having a NAT/DMZ router of some sort in front of the gateway, please check if your kernel has multicast enabled: http://unix.stackexchange.com/questions/25872/how-can-i-know-if-ip-multicas… I can probably add raw socket support to rip44d, mimicking what Marius did in his C version, to work around it, if this is indeed a problem. One alternative is to run the C daemon on those systems, of course! - Hessu, OH7LZB On Tue, Aug 6, 2013 at 2:08 AM, Brian Rogers <n1uro(a)n1uro.ampr.org> wrote: > On Sat, 2013-08-03 at 11:46 +0300, Marius Petrescu spake: >> I added an option to use raw sockets instead of multicast to the daemon. >> This is needed on systems that do not support multicast properly. >> On system where it works, there is no need to upgrade. > > Thank you Marius - it's definately now doing what it needs to do! Good > job! With my 10 yr old system running a P-III I'm lucky to have a circa > 2009 setup running. I don't know why on earth though this 2.6 kernel > doesn't support multicast.

10 20

Running on RPi. Still got issues
by Mark Phillips 07 Aug '13

07 Aug '13

Hi folks, So I was able to compile Maiko's latest JNOS code for my RPi and it appears to function correctly. I have one of John Hansen's TNC-Pi's which also seems to work using the I2CKISS stuff. I have the AGW remote modem stuff working. I was even able to get the encap stuff working via my pFsense FW with the aid of this rather useful posting http://forum.pfsense.org/index.php?topic=64060.0 and the encap.txt file. However, whilst I'm receiving UCSD's RIP broadcasts at my FW they are not making it through to JNOS. I've tried forwarding UDP port 520 however that does not seem to work as pFsense traps the RIP session as an IPIP session. This further confuses me as IPIP sessions are correctly sent to JNOS per the above. I have also tried activating the RIP daemon in pFsense and then getting JNOS to ask for a RIP update but that doesn't seem to work either. Ideas? Thanks Mark, G7LTT/NI2O Randolph, NJ

2 1

Thanks IP GURUS
by Demetre SV1UY 06 Aug '13

06 Aug '13

Hi all, KUDOS to all IP Gurus who helped me reinstall our ATHnet AMPRnet GATEWAY in Athens, Greece. Special thanks to Marc, Tom, Brian N1URO and Brian Kantor whose comments and WEB PAGES helped. An easy iptables script would also be a good help to us but I think that I am OK at the moment using UFW and also Brian N1URO's ideas on how to allow IPIP in my LINUX box using 3 IPTABLES commands I found in his WEB PAGES/POSTINGS. Thanks a lot guys. Your help is much appreciated! -- 73 de SV1UY Demetre Ch. Valaris IP Coordinator for AMPRnet in Greece e-mail: demetre.sv1uy(a)gmail.com Radio e-mail: sv1uy(a)winlink.org (to use my radio e-mail put //WL2K in the beginning of the subject line) http://www.qsl.net/sv1uy

4 3

Re: [44net] Tunnel issues with rip44d
by Pieter Luteijn 06 Aug '13

06 Aug '13

By default rip44d is using the interface tunl0, it seems: my $tunnel_if = 'tunl0'; You seem to be using tun0 in your networking scripts, so i suppose you either need to adjust the default, use the -i option to change the interface used by rip44d, or change the tunnel interface name to match so the rip44d is listening on the right interface. Pieter. Sent from a mobile, sorry for any typoes...

8 10

rip44d problem
by Demetre SV1UY 05 Aug '13

05 Aug '13

Hi all, After running ripp44d for about I see in my routing table that my own subnet 44.154/18 is routed to 87.202.40.155 (my ADSL router's dynamic IP) via tunl0 interface. Is this right? -- 73 de SV1UY Demetre Ch. Valaris IP Coordinator for AMPRnet in Greece e-mail: demetre.sv1uy(a)gmail.com Radio e-mail: sv1uy(a)winlink.org (to use my radio e-mail put //WL2K in the beginning of the subject line) http://www.qsl.net/sv1uy

5 9

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

44net