Re: [44net] Overlapping gateway subnets

Yup, good point. I might have missed that. Thanks. -----Original Message----- From: 44net-bounces+n6mef=mefox.org(a)hamradio.ucsd.edu [mailto:44net-bounces+n6mef=mefox.org@hamradio.ucsd.edu] On Behalf Of Marc, LX1DUC Sent: Friday, March 29, 2013 12:13 PM To: 44net(a)hamradio.ucsd.edu Subject: Re: [44net] Overlapping gateway subnets (Please trim inclusions from previous messages) _______________________________________________ -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 29/03/2013 19:59, Brian Kantor wrote: As far as I can tell it works. There is a route 44.161.0.0/16 for LX, but I have been experimenting with longer (more specific) prefixes (44.161.229.0/25, 44.161.202.0/24, 44.161.203.0/24) and it works fine (so far) within the IPIP mesh. The only thing you might need to test is connectivity from the network with the shorter prefix towards the network with the longer prefix. The gateway with the covering (shorter) prefix might be configured to handle this traffic locally instead of forwarding it via the IPIP mesh or a direct interconnect or ... You may also want to handle the occasional packet arriving at the wrong gateway and forward it to the other gateway. 73 de Marc _________________________________________ 44Net mailing list 44Net(a)hamradio.ucsd.edu http://hamradio.ucsd.edu/mailman/listinfo/44net http://www.ampr.org/donate.html