FS#41477 - [networkmanager] duplicate scope link routes
Attached to Project:
Arch Linux
Opened by Daniel Wendler (BMRMorph) - Tuesday, 05 August 2014, 14:45 GMT
Last edited by Jan de Groot (JGC) - Wednesday, 11 October 2017, 08:32 GMT
Opened by Daniel Wendler (BMRMorph) - Tuesday, 05 August 2014, 14:45 GMT
Last edited by Jan de Groot (JGC) - Wednesday, 11 October 2017, 08:32 GMT
|
Details
Description:
in latest NetworkManager there are 2 scope link routes when establishing an connection, one with an metric and one without: ip r default via 10.114.100.1 dev wifi0 proto static metric 1024 10.114.100.0/24 dev wifi0 proto kernel scope link src 10.114.100.24 10.114.100.0/24 dev wifi0 proto kernel scope link src 10.114.100.24 metric 303 it makes no difference if this is an wifi or an cabled connection: ip r default via 10.114.100.1 dev lan0 proto static metric 1024 10.114.100.0/24 dev lan0 proto kernel scope link src 10.114.100.24 10.114.100.0/24 dev lan0 proto kernel scope link src 10.114.100.24 metric 202 As we have an 1to1 mapping MAC to IP adress over both connection types my whole routing table looks then: ip r default via 10.114.100.1 dev lan0 proto static metric 1024 10.114.100.0/24 dev lan0 proto kernel scope link src 10.114.100.24 10.114.100.0/24 dev wifi0 proto kernel scope link src 10.114.100.24 10.114.100.0/24 dev lan0 proto kernel scope link src 10.114.100.24 metric 202 10.114.100.0/24 dev wifi0 proto kernel scope link src 10.114.100.24 metric 303 This behavior breakes my connections as the scope link routes without metric are used round robin. The problem could be resolved if i delete the scope link routes without metric. Additional info: * Version: extra/networkmanager (0.9.10.0-2) Steps to reproduce: Connect any network and show routing table. |
This task depends upon
Closed by Jan de Groot (JGC)
Wednesday, 11 October 2017, 08:32 GMT
Reason for closing: Fixed
Additional comments about closing: dhcp is internal by default now.
Wednesday, 11 October 2017, 08:32 GMT
Reason for closing: Fixed
Additional comments about closing: dhcp is internal by default now.
extra/networkmanager 0.9.10.0-4
As i don't have the problem bevor the specific Network Manager version, there must be something there.
Maybe someone have an hint to prevent inserting routes without metric.
nm-dhcp-helper does
Yes you are right.
For my part I think you can close the bug.
As a workaround I suggest using the internal dhcp client of NetworkManager :
https://mail.gnome.org/archives/networkmanager-list/2014-December/msg00030.html
It can be done by addind the following line in the [main] section of /etc/NetworkManager/NetworkManager.conf
dhcp=internal
https://wiki.archlinux.org/index.php/NetworkManager#Configure_NetworkManager_to_use_a_specific_DHCP_client
By the way, since networkmanager-1.0.0-2 and the default usage of dhclient things become even more strange,
as with this client i got unpredictable metric settings on all route (default and scope link) every time i trigger an UP/DOWN event.
So as this is an upstream Problem, this bug could be closed.