Subject: Re: [44net] Tunnel mesh is (mostly) down From: "Marius Petrescu" marius@yo2loj.ro Date: 01/05/2015 10:54 PM

To: "'AMPRNet working group'" 44net@hamradio.ucsd.edu

Yes, the latest version drops subnets for which the gateway is set inside their own subnet, sice this breaks routing.

Marius

-----Original Message----- From:44net-bounces+marius=yo2loj.ro@hamradio.ucsd.edu [mailto:44net-bounces+marius=yo2loj.ro@hamradio.ucsd.edu] On Behalf Of Rob Janssen Sent: Monday, January 05, 2015 22:28 To:44net@hamradio.ucsd.edu Subject: Re: [44net] Tunnel mesh is (mostly) down

... It could be that the latest version that I now downloaded hides that problem with 44.140.0.1 but I can easily see if other routes are appearing/disappearing regularly. ...

Rob

There is still something wrong with that network. Now that the 44.140.0.1 gateway is rejected, a gateway 192.16.126.18 inconsistently appears in the route table (sometimes it is there, sometimes it isn't). But that gateway is not listed at all in the portal! In the portal there is a gateway at 44.140.0.1 that advertises to be the gateway for subnet 44.140.0.0/16, of course wrong. The 192.16.126.18 would be fine, but it does not appear in the gateway listing at portal.ampr.org. But it is broadcast (occasionally) in the RIP broadcast. Difficult to follow what is going on here, I would say there is insufficient error checking somewhere.

Rob