#1004 closed enhancement (obsolete)
Wired connection should override wireless
Reported by: | CarolineM | Owned by: | tomeu |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | Sugar | Version: | Unspecified |
Severity: | Major | Keywords: | |
Cc: | sascha_silbe | Distribution/OS: | Unspecified |
Bug Status: | Unconfirmed |
Description
- Connect to wireless
- Plug in wired network
Actual behavior
says its connected to both, seems to be still connect to wireless, can't disconnect from wireless.
Desired behavior.
I would think wired should override wireless
Change History (7)
comment:1 Changed 14 years ago by tomeu
- Milestone changed from Unspecified by Release Team to 0.88
- Priority changed from Unspecified by Maintainer to Normal
- Summary changed from Connecting to both wireless and wired networks has problems to Wired connection should override wireless
- Type changed from defect to enhancement
comment:2 Changed 14 years ago by garycmartin
- Milestone changed from 0.88 to 0.90
- Severity changed from Unspecified to Major
comment:3 Changed 14 years ago by sascha_silbe
Would be nice if someone could investigate whether NetworkManager (the upstream component Sugar relies on for the actual work) needs to be fixed or whether we need to tweak something inside Sugar.
comment:4 Changed 14 years ago by sascha_silbe
- Cc sascha_silbe added
comment:5 Changed 14 years ago by sascha_silbe
According to Gnome#609794, NetworkManager should already prefer the wired connection for the default route (i.e. for most traffic).
comment:6 Changed 12 years ago by sascha_silbe
- Resolution set to obsolete
- Status changed from new to closed
Personal experience shows that this is already the case with current versions of NetworkManager. Please reopen with precise information for reproducing the issue if you encounter it again.
Pushing out to 0.90, but seems like work is needed on this given how some of the pilot classes are likely set-up. I've seen some chatter on 'disconnect from wireless' but not sure where it's at (that option was visible in UI but never hooked up to working code).