ampr-ripd does not set a route for 44.0.0.1, because that IP is not reachable via the tunnel, only via the internet.
On 2017-04-25 01:29, Rob Janssen wrote:
(Please trim inclusions from previous messages) _______________________________________________
Yes, there was an off-by-one error in the count of entries in the last packet. This error was not present when we were sending in gateway major order, but was there in packet-major-order which change I made early today. It has been corrected. Please check the next RIP update and see if that fixes things.
Ok, now I get the correct RIP packet :-) But the entry still does not appear in the route table... :-(
IP Address: 44.2.2.0, Metric: 1 Address Family: IP (2) Route Tag: 4 IP Address: 44.2.2.0 (44.2.2.0) Netmask: 255.255.255.0 (255.255.255.0) Next Hop: 24.52.189.1 (24.52.189.1) Metric: 1 IP Address: 44.0.0.1, Metric: 1 Address Family: IP (2) Route Tag: 4 IP Address: 44.0.0.1 (44.0.0.1) Netmask: 255.255.255.255 (255.255.255.255) Next Hop: 169.228.66.251 (169.228.66.251) Metric: 144.0.0.0/8 via 213.222.29.193 dev eth0 src 44.137.0.1 44.2.2.0/24 via 24.52.189.1 dev tunl0 proto ampr-ripd metric 4 onlink
So now I can continue local debugging to see what is going wrong... It fails both on the gateway (running latest ampr-ripd) and the Raspberry Pi (running earlier version). It does not appear in /var/lib/ampr-ripd/encap.txt either. Never assume there is only one bug...
Rob _________________________________________ 44Net mailing list 44Net@hamradio.ucsd.edu http://hamradio.ucsd.edu/mailman/listinfo/44net