You are not logged in.
I have a wired (enp0s20u2) and a wireless (wlp2s0) networkcard connected to the same network. The networking is managed by NetworkManager 0.9.8.9. The routing tables are the following:
$ ip route show
default via 192.168.0.1 dev enp0s20u2 proto static
192.168.0.0/24 dev enp0s20u2 proto kernel scope link src 192.168.0.9 metric 1
192.168.0.0/24 dev wlp2s0 proto kernel scope link src 192.168.0.10 metric 9
$ ip -6 route show
2a02:908:e513:d900::/64 dev enp0s20u2 proto kernel metric 256 expires 1084883sec
2a02:908:e513:d900::/64 dev wlp2s0 proto kernel metric 256 expires 1084883sec
fe80::/64 dev enp0s20u2 proto kernel metric 256
fe80::/64 dev wlp2s0 proto kernel metric 256
default via fe80::ce35:40ff:fee5:8ccd dev enp0s20u2 proto ra metric 1024 expires 1777sec
default via fe80::ce35:40ff:fee5:8ccd dev wlp2s0 proto ra metric 1024 expires 1777sec
With IPv4 the wired connection gets a lower metric wich is fine.
But with IPv6 both connections get the same metric and since there is no other criterion for choosing a source address (according to RFC3484) the source address and interface gets chosen randomly.
Is this a bug or is this expected behaviour?
Offline
That looks explosive. Does it even work okay?
I'm not sure, but why not define a metric in NM?
fs/super.c : "Self-destruct in 5 seconds. Have a nice day...\n",
Offline
Yes it works okay.
I can't find any option to define a metric in network manager
Offline