GNOME Bugzilla – Bug 723730
Routing table is not updated when ethernet cable is plugged in
Last modified: 2014-02-06 22:46:07 UTC
Description of problem: If, while connected over wifi, ethernet connection is made, routing table is not properly updated An alternative description: if I boot my laptop with ethernet hooked up and wifi enabled, connections are routed through wifi and/or DNS lookups take a very long time NM version: 0.9.9.0 (Fedora build) How reproducible: Every time Steps to Reproduce: 1. Boot a laptop without ethernet, have it connected to a wifi network 2. Connect ethernet cable (same network) 3. Browse pages/check email/etc. Actual results: Wifi route is stuck as the default in the routing table, so network connection is not working right. Expected results: routing table should become exactly same as it would've been if laptop was booted up with wifi and ethernet enabled and plugged in, respectively. Additional info: Turning wifi off and then back on seems to work around the problem because the wifi interface gateway is removed when wifi is disabled. When re-added, wifi doesn't override ethernet gateway (correct behavior) Ref. Fedora bug https://bugzilla.redhat.com/show_bug.cgi?id=886312
(In reply to comment #0) Could you please show your routing table: ip route I think this is a duplicate of bug 723178
Here's the info right after the bootup: [kostya@mireille ~]$ ip route default via 192.168.1.1 dev p1p1 proto static metric 1024 192.168.0.0/21 dev wlp6s0 proto kernel scope link src 192.168.0.211 192.168.0.0/21 dev p1p1 proto kernel scope link src 192.168.0.216 [kostya@mireille ~]$ ip route show table all default via 192.168.1.1 dev p1p1 proto static metric 1024 192.168.0.0/21 dev wlp6s0 proto kernel scope link src 192.168.0.211 192.168.0.0/21 dev p1p1 proto kernel scope link src 192.168.0.216 broadcast 127.0.0.0 dev lo table local proto kernel scope link src 127.0.0.1 local 127.0.0.0/8 dev lo table local proto kernel scope host src 127.0.0.1 local 127.0.0.1 dev lo table local proto kernel scope host src 127.0.0.1 broadcast 127.255.255.255 dev lo table local proto kernel scope link src 127.0.0.1 broadcast 192.168.0.0 dev wlp6s0 table local proto kernel scope link src 192.168.0.211 broadcast 192.168.0.0 dev p1p1 table local proto kernel scope link src 192.168.0.216 local 192.168.0.211 dev wlp6s0 table local proto kernel scope host src 192.168.0.211 local 192.168.0.216 dev p1p1 table local proto kernel scope host src 192.168.0.216 broadcast 192.168.7.255 dev wlp6s0 table local proto kernel scope link src 192.168.0.211 broadcast 192.168.7.255 dev p1p1 table local proto kernel scope link src 192.168.0.216 local ::1 dev lo proto kernel metric 256 fe80::/64 dev wlp6s0 proto kernel metric 256 fe80::/64 dev p1p1 proto kernel metric 256 unreachable default dev lo table unspec proto kernel metric 4294967295 error -101 local ::1 dev lo table local proto none metric 0 local fe80::67d:7bff:fe03:26ee dev lo table local proto none metric 0 local fe80::76e5:bff:fe4c:e2aa dev lo table local proto none metric 0 ff02::1 dev p1p1 metric 0 cache ff02::1 dev wlp6s0 metric 0 cache ff02::2 dev p1p1 metric 0 cache ff02::c dev wlp6s0 metric 0 cache ff02::16 dev wlp6s0 metric 0 cache ff02::1:ff03:26ee dev wlp6s0 metric 0 cache ff00::/8 dev wlp6s0 table local metric 256 ff00::/8 dev p1p1 table local metric 256 unreachable default dev lo table unspec proto kernel metric 4294967295 error -101 At this point, opening an SSH connection to remote machine is hanging ********************************* When I switch off the wifi with rfkill hardware switch: [kostya@mireille ~]$ ip route default via 192.168.1.1 dev p1p1 proto static metric 1024 192.168.0.0/21 dev p1p1 proto kernel scope link src 192.168.0.216 [kostya@mireille ~]$ ip route show table all default via 192.168.1.1 dev p1p1 proto static metric 1024 192.168.0.0/21 dev p1p1 proto kernel scope link src 192.168.0.216 broadcast 127.0.0.0 dev lo table local proto kernel scope link src 127.0.0.1 local 127.0.0.0/8 dev lo table local proto kernel scope host src 127.0.0.1 local 127.0.0.1 dev lo table local proto kernel scope host src 127.0.0.1 broadcast 127.255.255.255 dev lo table local proto kernel scope link src 127.0.0.1 broadcast 192.168.0.0 dev p1p1 table local proto kernel scope link src 192.168.0.216 local 192.168.0.216 dev p1p1 table local proto kernel scope host src 192.168.0.216 broadcast 192.168.7.255 dev p1p1 table local proto kernel scope link src 192.168.0.216 local ::1 dev lo proto kernel metric 256 fe80::/64 dev p1p1 proto kernel metric 256 unreachable default dev lo table unspec proto kernel metric 4294967295 error -101 local ::1 dev lo table local proto none metric 0 local fe80::67d:7bff:fe03:26ee dev lo table local proto none metric 0 ff02::1 dev p1p1 metric 0 cache ff00::/8 dev p1p1 table local metric 256 unreachable default dev lo table unspec proto kernel metric 4294967295 error -101 At this point, all connections work fine
(In reply to comment #2) > [kostya@mireille ~]$ ip route > default via 192.168.1.1 dev p1p1 proto static metric 1024 > 192.168.0.0/21 dev wlp6s0 proto kernel scope link src 192.168.0.211 > 192.168.0.0/21 dev p1p1 proto kernel scope link src 192.168.0.216 So, indeed you got both routes with identical metric. This is the same as bug 723178. Closing this bug as duplicate. Thank you for taking the effort to report this issue. *** This bug has been marked as a duplicate of bug 723178 ***