21 Apr
2017
21 Apr
'17
11:12 a.m.
Yes, it's still trying to use amprgw to get to a host on network 44
from network 44:
Apr 21 08:08:11 <local0.debug> amprgw ipipd[71490]: DEST44: len 37, os
87.251.250.110, od 169.228.66.251, is 44.165.2.2, id 44.165.129.254, ttl 63, proto 93
I don't think it should be doing this.
- Brian
On Fri, Apr 21, 2017 at 05:05:51PM +0300, SP2L wrote:
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