v6 mysteriously unreachable routes (2.2.15pre15)
Rafal Maszkowski
rzm w icm.edu.pl
Pon, 17 Kwi 2000, 23:26:36 MEST
3ffe:8010:22:1::3 is unreachable:
root w 6bone-gw:~,0# /usr/inet6/bin/ping 3ffe:8010:22:1::3
PING 3ffe:8010:22:1::3 (3ffe:8010:22:1::3): 56 data bytes
ping: sendmsg: Network is unreachable
ping: wrote 3ffe:8010:22:1::3 64 chars, ret=-1
ping: sendmsg: Network is unreachable
ping: wrote 3ffe:8010:22:1::3 64 chars, ret=-1
--- 3ffe:8010:22:1::3 ping statistics ---
2 packets transmitted, 0 packets received, 100% packet loss
even though there is a route there:
root w 6bone-gw:~,0# route -A inet6 | grep agar
3ffe:8010:22::2/128 3ffe:8010:22::2 UC 0 975 1 agaran
3ffe:8010:22::2/128 :: U 1024 0 0 agaran
3ffe:8010:22::/126 :: UA 256 99 0 agaran
3ffe:8010:22::/48 fe80::d519:a90a UG 1024 0 0 agaran
fe80::/10 :: UA 256 0 0 agaran
ff00::/8 :: UA 256 0 0 agaran
Deleting /48 twice and adding back helps. I am trying to investigate another
prefixes with the same problem. ip rou list table all shows e.g.:
local 3ffe:8010:28::1 via :: dev lo metric 0 mtu 3924 rtt 300
3ffe:8010:28::2 via 3ffe:8010:28::2 dev bnet metric 0
cache users 1 used 80 age 32sec mtu 1480 rtt 300
3ffe:8010:28::2 dev bnet metric 1024 mtu 1480 rtt 300
3ffe:8010:28::/126 via :: dev bnet proto kernel metric 256 mtu 1480 rtt 300
unreachable 3ffe:8010:28::/48 dev lo metric 1024 error -51 mtu 3924 rtt 300
3ffe:8010:28::/48 via fe80::d4a0:bc01 dev bnet metric 1024 mtu 1480 rtt 300
Where this unreachable /48 could be coming from? Is it my naughty mrtd or what?
Or could it be cached as such when the BGP session wasn't sending it yet? But
why it stays when we finally got it from BGP?
thanks
R.
--
Ale kto by mył ręce po przywitaniu się z mężem? - A. Fedorczyk
Więcej informacji o liście dyskusyjnej 6BONE-PL