44net

44net@mailman.ampr.org

3198 discussions

Trouble setting static route with ampr-ripd
by Neil Johnson 12 Aug '13

12 Aug '13

I've been trying add the following route to my "44" table to insure that local packets get sent out the wireless interface. ip route add 44.50.128.0/24 dev wlan0 table 44 However, I can't get it to be added when the system restarts. Any suggestions would be appreciated. Thanks. -Neil -- Neil Johnson -N0SFH http://erudicon.com

3 6

Re: [44net] Trouble setting static route with ampr-ripd
by Pieter Luteijn 11 Aug '13

11 Aug '13

When adding the route statement to the initialization sequence, make sure the wlan0 interface exists; don't put it too early in the sequence. Perhaps best to add it and its 'del' counterpart to the networking scripts that bring the wlan0 interface up and down, not to the rc-scripts? P. Sent from a mobile, sorry for any typoes... -------- Original message -------- From: Neil Johnson <neil.johnson(a)erudicon.com> Date: 2013/08/11 22:07 (GMT+01:00) To: AMPRNet working group <44net(a)hamradio.ucsd.edu> Subject: [44net] Trouble setting static route with ampr-ripd ip route add 44.50.128.0/24 dev wlan0 table 44 However, I can't get it to be added when the system restarts.

1 0

SIP Service on AMPRnet
by Marc, LX1DUC 10 Aug '13

10 Aug '13

Dear YLs and OMs, I have installed a SIP service on sipwise.ampr.org. It allows SIP users to do voice & video calls, instant messaging (via SIP), screen sharing, etc. There is also support for voicemail, call forwarding and call forking (upto 5 user-agents (devices, softphones, etc) per account). The system accepts calls from outside, try sip:lx1duc@sipwise.ampr.org or sip:+883510001204400@sipwise.ampr.org. (I'm using iNUM numbers to provide a globally unique numeric identifier so that hardware phones can make calls to other stations as well, while it's possible to dial "lx1duc" from a numeric keypad, it's more convenient for the user to actually dial a number H-I-H-I.) I'm using it on my mobile via a softphone right now (I didn't have time to configure my hardware phone), but the plan is to use it on hardware phones in our club shacks in LX. You're welcome to test it and if you want/need your own account please contact me off-list. I'm also interested in peering with other SIP services as well, so if you're running one and you're interested in peering, please contact me off-list. 73 de Marc, LX1DUC

2 3

Why rip44d?
by Michael E. Fox - N6MEF 09 Aug '13

09 Aug '13

This is a serious question: Why is everyone so enamored with and focused on using rip44d? Rip44d disadvantages: 1) Rip44d depends on getting the routes from a single source - amprgw, i.e. a single point of failure. 2) If that single source fails (as it did recently, for more than 12 hours), then the routes are gone, even though all of the other gateways may be completely reachable. 3) If you try to avoid that problem by timing out the routes slowly, then you might as well have a static list. It seems to me that periodic downloading of the encaps file, followed by the ip.munge scripts is a far better approach. Advantages: 1) You can define how often you want to download the file, based on how quickly you want to discover new gateways. For me, once nightly is fine. But it could be more often. 2) If the download of encaps fails, I continue using the same routes I had before until the next download attempt. This happens every once in a while - maybe once a month, for whatever reason. But no connectivity is lost. 3) If amprgw fails, the direct tunnels to all other gateways are unaffected. i.e. Single point of failure eliminated. Disadvantages: None that I can see. So I fail to see why everyone is so enamored with rip44d. Please explain. Thanks much, Michael N6MEF

9 10

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

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

44net