Re: [44net] Portal doesn't allow IPIP anycast via 44net

This is a legacy setting that emerged from the munge script and just perpetuated, and actually had no side effects, except the fact that 44.0.0.1 is not reachable from a ampr machine. And it wrongly gave birth to the idea that unknown networks would be forwrded by the amprgw using it as a default gateway. 73s de 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 lleachii(a)aol.com Sent: Friday, April 11, 2014 06:22 To: 44net(a)hamradio.ucsd.edu Subject: Re: [44net] Portal doesn't allow IPIP anycast via 44net ... - (bad practice) packets destined for invalid 44IPs are now forwarded on to AMPRGW instead of dropped by the local GW (recall, only BGP subnets who DO NOT want to run RIP44 and IPENCAP would need this reconfiguration and only your subnet needs this exception) -KB3VWG _________________________________________ 44Net mailing list 44Net(a)hamradio.ucsd.edu http://hamradio.ucsd.edu/mailman/listinfo/44net