Le 2013-12-19 11:46, Phil Mayers a écrit :
What does "ip -6 route" show on an affected box?
Ok, this is getting really strange. Maybe the "userspace RA listener"
has just kicked in, because IPv6 is working, but config is still funny.
A reboot doesn't change this, so it's a stable situation.
[simon@porto ~]$ ip -6 addr show scope global
3: em1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qlen 1000
inet6 2620:0:230:c000:3e97:eff:fe0b:dd8a/128 scope global dynamic
valid_lft 2587315sec preferred_lft 2587315sec
[simon@porto ~]$ ip -6 route
[...]
2620:0:230:8000::2 via fe80::217:31ff:fe4d:f047 dev em1 proto static metric 1
2620:0:230:c000::65 via fe80::217:31ff:fe4d:f047 dev em1 proto static metric 1
2620:0:230:c000:3e97:eff:fe0b:dd8a dev em1 proto kernel metric 256 expires
2587222sec
2620:0:230:c000::/64 dev em1 proto static metric 1
fe80::/64 dev em1 proto kernel metric 256
default via fe80::217:31ff:fe4d:f047 dev em1 proto static metric 1024
So my working hypothesis is that I did something that started the
userspace RA listener and now things are working as intended by the
NetworkManager devs. A bit funny-looking to me, but it still works.
Thanks all,
Simon
--
DTN made easy, lean, and smart --> http://postellation.viagenie.ca
NAT64/DNS64 open-source --> http://ecdysis.viagenie.ca
STUN/TURN server --> http://numb.viagenie.ca
