|
Hello guys,
I would like to change route metric on a device without reactivated its connection profile. For example, with nmcli, to change the metric from 100 to 800, I do the following:
nmcli device modify eth0 ipv4.route-metric 800
This works perfectly fine with NetworkManager 1.10.10 and I ended up with a routing table like this one:
default via 10.30.1.254 dev eth0 proto static metric 800 10.30.0.0/16 dev eth0 proto kernel scope link src 10.30.38.49 metric 800
But this doesn't work with NetworkManager 1.12.0 and only the route metric to reach subnet is changed (the one to reach the gateway is not changed):
default via 10.30.1.254 dev eth0 proto static metric 100
10.30.0.0/16 dev eth0 proto kernel scope link src 10.30.38.60 metric 800
Moreover, always with NM 1.12, if I configured my device with a manual IP (ip4.method=manual), the metric change is also correctly propagated to all route that implies the device.
I've raised the logging level of NetworkManager but I did'nt manage to know why the default route is not changed when dhcp setup is involved. I join two log files (one in dhcp and one in manual) to emphasize the moment I execute the nmcli command.
Can you guys please help me or give me some advice to solve this ?
Note: I use internal dhcp client in the NetworkManager conf.
|
Attachment:
dhcp_setup
Description: dhcp_setup
Attachment:
manual_addr_setup
Description: manual_addr_setup