Re: [44net] Bogus route entries From: "Marius Petrescu" marius@yo2loj.ro Date: 11/25/2014 07:26 PM

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

Hello,

With the last apr-ripd version (1.13), this entry (or any other having the gateway inside its own subnet) gets ignored and can be direct routed (since it is BGP-ed). Unlike the entry 44.140.0.0/24 via some public IP which does not work. I would prefer to see it as it is via 44.140.0.1...

Marius, YO2LOJ

Ok I must tell I have not yet installed the latest version, I am using 1.12 with the -x option and I noted this one (as it appears near the top of the list) is coming and going all the time.

I captured a trace and this entry was not among the RIP entries sent at that time. So the problem is somewhere upstream, not in ampr-ripd.

Next tuesday we will move our gateway to the datacenter of our ISP and we will start doing BGP routing of 44.137 (permission from ARDC is already obtained), so then I will update ampr-ripd and see what I can do to have entries like this working OK.

But this time my main question is why is this route changing all the time even when it is not updated in the portal? (unlike the French one and now a Spanish one where users apparently are experimenting and do not understand the system so they insert and delete their entry all the time until it works)

Rob