On 2016-09-20T00:37:26+0200, Olaf Schreck <chakl@syscall.de> wrote: > > As someone else asked, showing us the output of 'ip -6 a' and 'ip -6 > > r' could be helpful. > > Ok, sorry. I don't see anything special here: Thanks. You said it breaks when you configure eth1 though. What is the configuration you are putting on eth1 that causes the breakage? > # ip -6 ro > 2a01:4f8:191:XXXX::/64 dev eth0 proto kernel metric 256 > fe80::/64 dev eth0 proto kernel metric 256 > fe80::/64 dev eth1 proto kernel metric 256 > fe80::/64 dev vif1.0 proto kernel metric 256 > fe80::/64 dev vif2.0 proto kernel metric 256 > fe80::/64 dev vif3.0 proto kernel metric 256 > fe80::/64 dev vif4.0 proto kernel metric 256 > default via fe80::1 dev eth0 metric 1024 > > # ip -6 ad > 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 16436 > inet6 ::1/128 scope host > valid_lft forever preferred_lft forever > 2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qlen 1000 > inet6 2a01:4f8:191:XXXX::4/64 scope global > valid_lft forever preferred_lft forever > inet6 fe80::5246:5dff:fe9f:f752/64 scope link > valid_lft forever preferred_lft forever > 3: eth1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qlen 1000 > inet6 fe80::6a05:caff:fe18:596/64 scope link > valid_lft forever preferred_lft forever > 4: vif1.0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qlen 32 > inet6 fe80::fcff:ffff:feff:ffff/64 scope link > valid_lft forever preferred_lft forever > 5: vif2.0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qlen 32 > inet6 fe80::fcff:ffff:feff:ffff/64 scope link > valid_lft forever preferred_lft forever > 6: vif3.0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qlen 32 > inet6 fe80::fcff:ffff:feff:ffff/64 scope link > valid_lft forever preferred_lft forever > 7: vif4.0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qlen 32 > inet6 fe80::fcff:ffff:feff:ffff/64 scope link > valid_lft forever preferred_lft forever -- Kenyon Ralph
Attachment:
signature.asc
Description: Digital signature