Ticket #1004 (closed enhancement: obsolete)

Opened 4 years ago

Last modified 19 months ago

Wired connection should override wireless

Reported by: CarolineM Owned by: tomeu
Priority: Normal Milestone: 0.90
Component: sugar Version: Unspecified
Severity: Major Keywords:
Cc: sascha_silbe Distribution/OS: Unspecified
Bug Status: Unconfirmed

Description

1. Connect to wireless
2. 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

 http://www.youtube.com/watch?v=mLsPNpJ7tm8

Change History

Changed 4 years ago by tomeu

  • 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
  • milestone changed from Unspecified by Release Team to 0.88

Changed 3 years ago by garycmartin

  • severity changed from Unspecified to Major
  • milestone changed from 0.88 to 0.90

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).

Changed 3 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.

Changed 3 years ago by sascha_silbe

  • cc sascha_silbe added

Changed 3 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).

Changed 19 months ago by sascha_silbe

  • status changed from new to closed
  • resolution set to obsolete

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.

Note: See TracTickets for help on using tickets.