Whoever owns 44.131.160.1 you need to check your system configuration. It cannot do anything with 255.255.255.255 Below what I am seeing
8:20:25.632390 IP 81.174.253.193 > 192.168.1.150: IP 44.131.160.1.5678 > 255.255.255.255.5678: UDP, length 120 (ipip-proto-4) 08:20:25.635667 IP 192.168.1.150 > 81.174.253.193: IP 44.135.90.2 > 44.131.160.1: ICMP host 255.255.255.255 unreachable, length 36 (ipip-proto-4)
That is the Mikrotik Neighbor Discovery Protocol (MNDP). Of course, it should be turned of for tunnel interfaces (it is enabled by default on all interfaces).
73s de Marius, YO2LOJ
-----Original Message----- From: 44net-bounces+marius=yo2loj.ro@hamradio.ucsd.edu [mailto:44net-bounces+marius=yo2loj.ro@hamradio.ucsd.edu] On Behalf Of Don Moore Sent: Saturday, April 11, 2015 15:25 To: AMPRNet working group Subject: [44net] (no subject)
(Please trim inclusions from previous messages) _______________________________________________ Whoever owns 44.131.160.1 you need to check your system configuration. It cannot do anything with 255.255.255.255 Below what I am seeing
8:20:25.632390 IP 81.174.253.193 > 192.168.1.150: IP 44.131.160.1.5678 > 255.255.255.255.5678: UDP, length 120 (ipip-proto-4) 08:20:25.635667 IP 192.168.1.150 > 81.174.253.193: IP 44.135.90.2 > 44.131.160.1: ICMP host 255.255.255.255 unreachable, length 36 (ipip-proto-4)
Btw Don, broadcast/multicast messages should not be rejected with ICMP unreachable, but dropped, since the may not be addressed to your system, like in this case. Rejecting them just generates useless ICMP traffic, and they could even be legitimate traffic. As a general approach on such cases.
8:20:25.632390 IP 81.174.253.193 > 192.168.1.150: IP 44.131.160.1.5678 > 255.255.255.255.5678: UDP, length 120 (ipip-proto-4) 08:20:25.635667 IP 192.168.1.150 > 81.174.253.193: IP 44.135.90.2 > 44.131.160.1: ICMP host 255.255.255.255 unreachable, length 36 (ipip-proto-4)
-
Don Moore -
Marius Petrescu