Bug 452922 - Update metrics to ensure routing is correct with multiple interfaces
Update metrics to ensure routing is correct with multiple interfaces
Product: Fedora
Classification: Fedora
Component: NetworkManager (Show other bugs)
i386 Linux
low Severity medium
: ---
: ---
Assigned To: Dan Williams
Fedora Extras Quality Assurance
: Reopened
Depends On:
  Show dependency treegraph
Reported: 2008-06-25 17:25 EDT by Aidan Skinner
Modified: 2009-02-14 15:29 EST (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2009-02-14 15:29:18 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
grep NetworkManager /var/log/messages (40.02 KB, text/plain)
2008-06-25 17:25 EDT, Aidan Skinner
no flags Details

  None (edit)
Description Aidan Skinner 2008-06-25 17:25:15 EDT
Description of problem:
When I plug in an ethernet cable to my thinkpad z61 network manager dhcps
correctly, but does not drop the wireless connection and apps continue to use
it. I have to disable wireless to use the cable I just plugged in. 

Version-Release number of selected component (if applicable):

How reproducible:
Happens every time

Steps to Reproduce:
1. Connect to wlan 
2. Plug in ethernet cable
3. Watch icon change to indicate wired
Actual results:
Network uses wlan0

Expected results:
Network uses eth0

Additional info:
Wireless is Intel PRO/Wireless 3945ABG
Ethernet is Broadcom BCM5752M
Comment 1 Aidan Skinner 2008-06-25 17:25:15 EDT
Created attachment 310298 [details]
grep NetworkManager /var/log/messages
Comment 2 Aidan Skinner 2008-06-28 05:31:52 EDT
This also happens on my Thinkpad T41, atheros AR5212 wlan and Intel 82540EP ethernet
Comment 3 Dan Williams 2008-07-02 19:19:49 EDT
This is by design and one of the major features of 0.7; NetworkManager keeps
available devices up so that your apps don't break when you switch.  It changes
the default route so that new connections will use the new default device. 
What's the output of '/sbin/route -n' in your situation?
Comment 4 Aidan Skinner 2008-07-16 21:08:43 EDT
Ok, that makes sense (and is rather nifty), but it sounds like the new
connections aren't defaulting properly.

[aidan@thoughtful ~]$ /sbin/route  -n
Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface   U     0      0        0 wlan0   U     0      0        0 eth0         UG    0      0        0 eth0

(this would be less of a problem without #453278)
Comment 5 Dan Williams 2008-07-17 09:35:04 EDT
Yeah, we probably need to update metrics to ensure that eth0 is really being used.
Comment 6 Dan Williams 2009-02-14 15:29:18 EST
This functionality got into NM on 2008-09-30.  Should be long-since fixed.

Note You need to log in before you can comment on or make changes to this bug.