Bug 239190

Summary:	Feature request: wired and wireless at the same time
Product:	[Fedora] Fedora	Reporter:	François Kooman <fkooman>
Component:	NetworkManager	Assignee:	Dan Williams <dcbw>
Status:	CLOSED DUPLICATE	QA Contact:
Severity:	medium	Docs Contact:
Priority:	medium
Version:	rawhide	CC:	mb--redhat
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2008-02-12 14:15:21 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description François Kooman 2007-05-05 20:23:14 UTC

Description of problem:

NetworkManager should be able to connect to wired and wireless network at the
same time (using different metric in route table)

How reproducible:

Use NetworkManager with both wired and wireless connection, unwanted behavior
when switching to wireless.

Steps to Reproduce:
1. Start in situation where you are connected to wired network
2. Try to connect to wireless network
3. NetworkManager disables wired network! 
4. Asks for key
5. Connects to wireless network
6. If this fails switch back to wired

Expected results:
1. Start in situation where you are connected to wired network
2. Try to connect to wireless network
4. Asks for key
5. Connects to wireless network with higher metric value in route table
6. If this fails, do nothing

Additional info:

When connected to wireless and wired network wired network is preferred. When
you unplug wired immediate switch to wireless.

The problem now is that when you try to connect to wireless network the wired
connection is disabled before the wireless connection is brought up (unwanted).
They should be both active, or only disconnect wired when the connection to the
wireless network is successful.

Comment 1 Matt Bernstein 2007-10-24 16:14:34 UTC

I would prefer to see this done at layer 2, so that your SSH terminals don't
die. Perhaps this could be achieved with a bridge device, but this is quite hard
to pull off given the dangers of network loops. Maybe wait for RSTP to hit the
Linux kernel?

Comment 2 Dan Williams 2008-02-12 14:15:21 UTC


*** This bug has been marked as a duplicate of 178276 ***