26 Jul
2015
26 Jul
'15
3:15 p.m.
Subject:
Re: [44net] Iperf server - kk7kx
From:
Assi Friedman <assi(a)kiloxray.com>
Date:
07/26/2015 12:23 AM
To:
AMPRNet working group <44net(a)hamradio.ucsd.edu>
Based off the output of the munge script, those two addresses take
different paths:
/sbin/ip route add 44.137.41.96/28 via 89.18.172.156 dev tunl0 onlink
/sbin/ip route add 44.137.0.0/16 via 213.222.29.194 dev tunl0 onlink
Ok... THAT explains something!
This is *old* data. That 44.137.41.96/28 entry was removed on April 25th this
year, and you still have it in your table.
The 44.137.41.96/28 network should now be routed via the 44.137.0.0/16 entry,
as I have moved this network from a tunnel route to a radio link to our Dutch HAMNET
which connects to internet via a national gateway for 44.137.0.0/16.
It looks like your method of managing routes only adds and modifies entries, but
never deletes them. I'm interested in what method you are using, and if you maybe
have copied it from someone else who also still uses this. It would explain some of
the broken routing we are facing.
Of course when some route no longer appears in the encap table, you should make
sure you also delete it from your local routing table. Else you will have more and
more incorrect routes as a result.
Maybe it is better to switch to using ampr-ripd, which would not have this problem.
Rob