Pretty sure this was resolved at some point, either way, not a bug now
** Changed in: network-manager (Ubuntu)
Status: Expired => Invalid
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/673772
Title:
RFC: Wi-Fi should not be the default route/gateway when copper is in
use
Status in “network-manager” package in Ubuntu:
Invalid
Bug description:
Binary package hint: network-manager
Opening this up at mtrudel's request...
I've found that on any of the laptops I use at home (all running 10.10
at this point) that both the copper and wi-fi network connections are
used. I opened an original bug asking for a way to turn wi-fi off
when copper is present and back on when it's disconnected or not
present. Windows handles that splendidly (surprisingly) and I find it
a useful feature.
HOWEVER, more problematic than my wishful thinking is that when I have
both wi-fi and copper running, the wi-fi is always chosen as the
default outbout route. It should not be. For example, I connect my
GigE copper port to my GigE LAN infrastructure, but NetworkManger also
enables wi-fi by default. So, when I send packets out, they default
out of the wireless device operating at 802.11g speeds instead of out
my copper card at GigE speeds.
This can cause quite a bottleneck especially when moving large amounts
of data around (e.g. ISO files, image directories, backups, etc). Not
to mention the fact that it ties up my entire wireless network until
I'm done with whatever I'm working on.
So, after discussion with Mathieu, we both agree that the default
route should not be wireless, unless no copper connection is present.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/673772/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : [email protected]
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
