44net August 2013

44net@mailman.ampr.org

47 participants
68 discussions

Re: [44net] 44Net Digest, Vol 2, Issue 116

by Rob Janssen

> Subject: > Re: [44net] dd-wrt and ipip > From: > lleachii(a)aol.com > Date: > 08/13/2013 05:04 PM > > To: > 44net(a)hamradio.ucsd.edu > > > All, > > I think the reason that nodes on the 44 Network cannot reach me is that my router is not allowing connections from the Internet to pass through. > > My setup: > > Router 1 > WAN 76.114.216.250 <> LAN 192.168.x.x <> > > Router 2 > WAN 192.168.x.2 <> LAN 192.168.y.x > > AMPRGW > 192.168.y.5 > > In trying to setup IPTABLES commands to allow IPIP traffic, I've had no success thus far. > > On Router1: > iptables -t filter -I INPUT -p ipip -j ACCEPT > iptables -t filter -I FORWARD -p ipip -j ACCEPT > iptables -t nat -I PREROUTING -i vlan1 -p ipip -j DNAT --to-destination 192.168.x.2 > > On Router2: > > iptables -t filter -I INPUT -p ipip -j ACCEPT > iptables -t filter -I FORWARD -p ipip -j ACCEPT > iptables -t nat -I PREROUTING 1 -s 169.228.66.251 -p ipip -i vlan1 -j DNAT --to-destination 192.168.y.5 > iptables -t nat -I PREROUTING 2 -p ipip -i vlan1 -j DNAT --to-destination 192.168.y.5 > > Any ideas? > Your problem is the protocol number used for encapsulation, I think. The "ipip" protocol is protocol 94, the one that was registered mistakenly at a time when protocol 4, which does exactly the same, already existed. Now the protocol 4 is used, which is in /etc/protocols under its name "ip". So use -p ip or just -p 4. Rob

10 years, 8 months

Cisco/juniper configs?

by Bryan Fields

Greetings, I've been doing some work to get the IPIP tunnel information into a router on a daily basis, has anyone else automated this? I was wondering how the reachability of this from the global routing table of the public internet works, if at all. Everything I've been reading says this is all separate, but we do interconnect at a couple locations. I must admit I'm new to this, but is 44/8 intended to be totally separate a la the GRX network? Granted my use of this space is for high speed wireless networks on the ham bands, I have little interest in the 9.6 kilobaud TCP/IP packet radio. I've got some of the 900MHz FHSS gear hacked to run in a narrower channel, and I've been experimenting with running some of the 5ghz units in the ham band at 5cm (5mhz channel is able to do about 10mbit/s). My intention is to have it all work across hardware routers, ie cisco/ALU/juniper rather than maintain a bunch of linux boxes. Thoughts? -- Bryan Fields 727-409-1194 - Voice 727-214-2508 - Fax http://bryanfields.net

10 years, 8 months

Trouble setting static route with ampr-ripd

by Neil Johnson

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

10 years, 8 months

Re: [44net] Trouble setting static route with ampr-ripd

by Pieter Luteijn

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.

10 years, 8 months

SIP Service on AMPRnet

by Marc, LX1DUC

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

10 years, 8 months

Why rip44d?

by Michael E. Fox - N6MEF

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

10 years, 8 months

bad ip address?

by Don Moore

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

10 years, 8 months

FW: Ampernet

by Kutche, Jerry (Mitchell) USA

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

10 years, 8 months

Re: [44net] "Invalid Gateway Address"

by Pieter Luteijn

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

10 years, 8 months

"Invalid Gateway Address"

by Neil Johnson

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

10 years, 8 months

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

44net August 2013