amprgw has recently logged several discarded packets like the following:
Apr 24 18:44:03 <local0.info> amprgw ipipd[1518]: IBCAST: len 149, os 208.110.114.235, od 169.228.66.251, is 44.135.193.18, id 255.255.255.255, ttl 64, proto 17
encapped packets aren't supposed to send to the broadcast address (255.255.255.255).
Apr 24 18:44:05 <local0.info> amprgw ipipd[1518]: ISRC0: len 122, os 77.138.34.39, od 169.228.66.251, is 0.0.0.0, id 255.255.255.255, ttl 64, proto 17
encapped packets aren't supposed to come from address 0.0.0.0 and encapped packets aren't supposed to send to the broadcast address (255.255.255.255).
Apr 24 18:44:06 <local0.info> amprgw ipipd[1518]: TIMXCEED: len 52, os 85.234.252.133, od 169.228.66.251, is 44.165.53.254, id 224.0.0.9, ttl 1, proto 17
Looks like a routing loop on RIP packets.
Ah well, variety is the spice of life... - Brian
Brian.
Belows IP's belong to SR3BBS gateway which _IS OFF LINE_ for a long time!
44.165.53.254 - mikrotik.sr3bbs.ampr.org 85.234.252.133 - public IP for 44.165.53.0/24 ( subnetregistered on portal.ampr.org )
There are 14 hosts from this subnet registered in DNS but _NONE_ of them reachable at all!
Best regards.
If SR3BBS subnet is permanently offline, it should be deleted from the portal. On the other hand, if they're unreachable because their router is misconfigured, they'd probably appreciate having some help in getting things put right. - Brian
On Tue, Apr 25, 2017 at 10:37:04AM +0200, SP2L wrote:
Belows IP's belong to SR3BBS gateway which _IS OFF LINE_ for a long time!
44.165.53.254 - mikrotik.sr3bbs.ampr.org 85.234.252.133 - public IP for 44.165.53.0/24 ( subnetregistered on portal.ampr.org )
There are 14 hosts from this subnet registered in DNS but _NONE_ of them reachable at all! Best regards. Tom - SP2L On 25/04/17 03:56, Brian Kantor wrote:
Apr 24 18:44:06 <local0.info> amprgw ipipd[1518]: TIMXCEED: len 52, os 85.234.252.133, od 169.228.66.251, is 44.165.53.254, id 224.0.0.9, ttl 1, proto 17
Looks like a routing loop on RIP packets.
-
Brian Kantor -
SP2L