We have a router running Debian Lenny that has been happily routing IPv6 for several months. Our upstream has advised that our address range is changing, and both are currently operational, so I thought I'd add the second address for testing.
ip -6 addr add 2405:3c00:1:13::2/64 dev eth1
# ping6 2405:3c00:1:13:: (our upstream router) 64 bytes from 2405:3c00:1:13::2: icmp_seq=1 ttl=64 time=0.089 ms
# ip -6 route get 2405:3c00:1:13:: local 2405:3c00:1:13:: from :: via :: dev lo table local proto none src 2405:3c00:1:13::2 metric 0 mtu 16436 advmss 16376 hoplimit 4294967295 # route -6 | grep 2405 2405:3c00:1:13::/64 :: U 256 0 1 eth1 2405:3c00:1:13::/128 :: Un 0 1 0 lo 2405:3c00:1:13::2/128 :: Un 0 1 0 lo
I am curious how the
...13::/128 route arrived. It appears about two seconds after I add the address to the interface. radvd(8) is not enabled on the interface, unsetting
autoconf makes no difference.
Is there any easy way to keep an eye on which process is modifying the routing table? Does anyone have any brilliant ideas about what the culprit might be?