Re: [44net] AMPRNet Interoperability with BGP

For those using ampr-ripd, the latest version (1.13) does NOT set a route if the gateway falls inside its own 44net subnet, actually preventing those situations. The condition for it to work is, of course, NOT to have a default 44/8 route via ampr-gw, so that unknown 44net destination are NAT-ed to the gateway's public IP. Marius, YO2LOJ -----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 09:46 To: AMPRNet working group Subject: Re: [44net] AMPRNet Interoperability with BGP (Please trim inclusions from previous messages) _______________________________________________ On Tue, Jun 16, 2015 at 11:01 PM, Brian Kantor <Brian(a)ucsd.edu> wrote: A more robust check would be to ping whatever gateway IP is entered. If a reply is received, allow it, if not, report the error to the user ("no route to host", etc.). Also check that the IP is not within its own subnet. I'd be impressed if someone succeeded in passing the first test and not the second, but not surprised. (If you're one of those who blocks ICMP, you're intentionally breaking things and you can deal with your own mess.) Tom KD7LXL _________________________________________ 44Net mailing list 44Net(a)hamradio.ucsd.edu http://hamradio.ucsd.edu/mailman/listinfo/44net