Bug 970293 - Activates both wired and wireless devices
Summary: Activates both wired and wireless devices
Alias: None
Product: Fedora
Classification: Fedora
Component: NetworkManager
Version: 19
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
Assignee: Dan Williams
QA Contact: Fedora Extras Quality Assurance
Depends On:
TreeView+ depends on / blocked
Reported: 2013-06-03 21:50 UTC by Enrico Scholz
Modified: 2015-02-18 11:11 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2015-02-18 11:11:59 UTC
Type: Bug

Attachments (Terms of Use)

Description Enrico Scholz 2013-06-03 21:50:14 UTC
Description of problem:

NetworkManager activates both wired and wireless devices at the same time. This causes ambiguous routing tables like

# ip route
default via dev eth0  proto static dev eth0  proto kernel  scope link  src dev wlan0  proto kernel  scope link  src 

and makes it impossible to use the same ip address for both devices.

With setup above, data can be sent over the slow wireless interface, although fast ethernet is available.  There is created unneeded radiation and power consumption too.

There should be added some configuration option (e.g. redundancy/failover pools of interfaces with adjustable priorities) so that only one interface is active at a time.

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


Comment 1 Karel Volný 2013-06-04 12:19:06 UTC
this has already been discussed in bug #454955 ... but things have changed over time, maybe it could be reconsidered?

having to disable autoconnecting to wifi and then connecting manually if no ethernet is available is a royal PITA :-(

btw, one of the ways how to automate is here:

... could we at least get this dispatcher script preinstalled, and a GUI checkbox to activate/deactivate it, if there is no better solution on the NM roadmap?

Comment 2 Enrico Scholz 2013-06-04 16:07:49 UTC
Every GUI solution is not an option for me because login requires NFS mounted /home which requires network.  And not every laptop has a physical rfkill switch.

The script idea looks promising; I will see how it will work for my use case (the ultimate goal is to use the same ip address for eth0 and wlan0 because NFS does not behave well when client address changes)

Comment 3 Dan Williams 2013-06-04 16:33:18 UTC
The routes not getting assigned the right priorities was a bug which was fixed recently upstream and will be in NM updates for fedora soon.  With these new builds you should see a 'metric' item: dev p4p1  proto kernel  scope link  src  metric 1 dev wlan0  proto kernel  scope link  src  metric 9

where the higher metric items will be chosen for traffic and thus the routing is not ambiguous.

Comment 4 Fedora Update System 2013-06-07 22:28:17 UTC
NetworkManager-,network-manager-applet- has been submitted as an update for Fedora 19.

Comment 5 Enrico Scholz 2013-06-08 10:31:53 UTC
ok; routes are not ambiguous anymore.  But it still does not allow to use the same ip address for both interfaces.  Extra power consumption and unneeded radiation are not solved either.

fwiw, the script from comment #1 works perfectly for my use case.  wlan0 gets assigned the MAC of eth0 and both interfaces get same ip from dhcp server.  After removing laptop from docking station (-> eth0 gets disconnected), wlan0 gets up and NFS /home is usable without synchronization delays.  Ditto for placing it on docking station again.

Of curse, script will not cover all use cases (e.g. when there are multiple wireless interfaces) but they are not interesting for me atm.

Comment 6 Fedora Update System 2013-06-09 03:27:54 UTC
NetworkManager-, network-manager-applet- has been pushed to the Fedora 19 stable repository.  If problems still persist, please make note of it in this bug report.

Comment 7 Fedora End Of Life 2015-01-09 22:34:08 UTC
This message is a notice that Fedora 19 is now at end of life. Fedora 
has stopped maintaining and issuing updates for Fedora 19. It is 
Fedora's policy to close all bug reports from releases that are no 
longer maintained. Approximately 4 (four) weeks from now this bug will
be closed as EOL if it remains open with a Fedora 'version' of '19'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 19 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 8 Fedora End Of Life 2015-02-18 11:11:59 UTC
Fedora 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this

Thank you for reporting this bug and we are sorry it could not be fixed.

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