Re: [44net] AMPRNet Interoperability with BGP

I can confirm this. HamWAN's setup, advertizing 44.24.241.0/24 via 44.24.221.1 worked flawless under the condition to drop that nonfunctional default 44/8 to ampr-gw route and NAT that traffic as any other internet traffic to the public IP. But since nobody wants to drop that route... Whatever. Btw, not a single setup tutorial talks about setting that 44/8 via ampr-gw. Marius -----Original Message----- From: 44net-bounces+marius=yo2loj.ro(a)hamradio.ucsd.edu [mailto:44net-bounces+marius=yo2loj.ro@hamradio.ucsd.edu] On Behalf Of Tom Hayward Sent: Wednesday, June 17, 2015 04:56 To: AMPRNet working group Subject: Re: [44net] AMPRNet Interoperability with BGP BTW, HamWAN used to be "in the RIP list". The entry was deleted by an AMPR administrator because he thought it wasn't working. We were using 44.24.221.1 as the gateway address. This address was advertised via BGP, accessible from the internet at large, and intentionally NOT advertised via RIP so that other gateways would not try to contact it inside an IPIP packet. This setup was spot-checked from a number of other AMPR systems and proven to work. The only case where it didn't work is when administrators added a static 44/8 route to their gateway. Note that there is no 44/8 route in the RIP/encap list. We're at a bit of a stalemate now. We'd have to reconfigure things a bit and utilize another IP address from our ISP to get it running on a non-44 gateway IP. The simpler solution (and one that serves all BGP networks) is to work towards solving the underlying BGP/IPIP interoperability problem that started this thread. Tom KD7LXL _________________________________________ 44Net mailing list 44Net(a)hamradio.ucsd.edu http://hamradio.ucsd.edu/mailman/listinfo/44net