FS#41395 - [networkmanager] Default Route doesn't change when switching to DHCP

Attached to Project: Arch Linux
Opened by tangxinfa (tangxinfa) - Wednesday, 30 July 2014, 10:20 GMT
Last edited by Jan de Groot (JGC) - Tuesday, 14 June 2016, 06:44 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Jan de Groot (JGC)
Jan Alexander Steffens (heftig)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:
IPv4->Addresses set to "Manual", the "Gateway" is the "Default Route"; When IPv4->Addresses change to "Automatic (DHCP)", the "Default Route" not change.


Additional info:
networkmanager 0.9.10.0-2


Steps to reproduce:
1. Configure Wired IPv4 Settings to "Manual".
Address: 192.168.90.18
Netmask: 255.255.255.0
Gateway: 192.168.90.2
2. Reconnect to take effect.
IP Address: 192.168.90.18
Default Route: 192.168.90.2
3. Configure Wired IPv4 Settings to "Automatic (DHCP)".
NOT empty the Manual settings(Address, Netmask, Gateway).
4. Reconnect to take effect.
IP Address: 192.168.111.100
Default Route: 192.168.90.2 <--------------- BUG
DNS: 192.168.111.1
5. Configure Wired IPv4 Settings to "Automatic (DHCP)" again.
empty the manual settings(Address, Netmask, Gateway).
6. Reconnect to take effect.
IP Address: 192.168.111.100
Default Route: 192.168.111.1 <--------------- OK
DNS: 192.168.111.1
This task depends upon

Closed by  Jan de Groot (JGC)
Tuesday, 14 June 2016, 06:44 GMT
Reason for closing:  Fixed
Comment by Samantha McVey (samcv) - Thursday, 09 June 2016, 09:54 GMT
networkmanager was at version 0.9.10.0 when this bug was submitted. It is now at 1.2.2. Without more evidence It seems like it was originally an issue with networkmanager and possibly not with the arch package itself, and unless the original poster says this is still an issue I think this should be closed. I wasn't able to find any recent (within the last 2 years) bug reports about issues with regard to setting the route except when the person was using vpn, not on a standard connection. I'm assuming this bug is no longer present, but if the bug opener is still around please update us on the status. Thank you.
Comment by tangxinfa (tangxinfa) - Tuesday, 14 June 2016, 02:58 GMT
I tested with NetworkManager 1.2.2, the bug is gone.

Please close this bug report, thanks:)

Loading...