21 Apr
2017
21 Apr
'17
1:07 p.m.
Hi Tom,
Those routes are correct and are BGP routed endpoint host routes.
They are generated by ampr-ripd starting with version 1.16 to allow you
to reach those subnets via tunnel.
Marius, YO2LOJ
On 2017-04-21 17:05, SP2L wrote:
(Please trim inclusions from previous messages)
_______________________________________________
Brian, Marius et al.
Brian, is my gateway still been misbehaving?
Brian's post dated Apr 20th 15:48UTC comprised my public IP address
87.251.250.110
This alerted me enough to search for possible culprit.
Checked thorughly present routing table on my server.
To my astonishment I spotted following entries:
44.130.121.2 via 192.168.0.1 dev eth0 proto 44 onlink.
44.130.122.2 via 192.168.0.1 dev eth0 proto 44 onlink.
44.130.124.2 via 192.168.0.1 dev eth0 proto 44 onlink.
44.131.14.255 via 192.168.0.1 dev eth0 proto 44 onlink.
From April 5th I started using ampr-ripd-1.16
Yesterday, after I spotted above totally wrong entries
I returned to ampr-ripd-1.15
From this very moment I do not see such routes anymore.
Please note: neither before nor after I swapped ampr-ripd,
encap.txt file generated by ampr-ripd _DID NOT_
contained such wrong entries!
Server operating system is: systemd Debian-8.7 32bit - updated to date.
Best regards.
Tom - SP2L
_________________________________________
44Net mailing list
44Net(a)hamradio.ucsd.edu
http://hamradio.ucsd.edu/mailman/listinfo/44net