That's an interesting idea, however the point of having both up is to provide a fallback for wired through wireless. Perhaps the issue is rather more that your wifi connection gets the default route, which should not be happening if wired is connected.
I think this proposition should ideally be discussed on the NetworkManager mailing list (see http://live.gnome.org/NetworkManager/) rather than a bug report here, so that a patch could benefit more people. Can you open a separate bug for the wifi default gateway so we can look into it? Le 6 oct. 2010 09:05, "Jeff Lane" <[email protected]> a écrit : > Public bug reported: > > Binary package hint: network-manager > > Just a wishlist item for perhaps Natty. But it would be super if we > could add the logic to disable or at least not auto-connect a wi-fi > connection when there is an existing copper connection, or a copper > connection is found. > > For example, when I boot my system with my GigE Network card connected > to my GigE switch and infrastructure, my 802.11n wifi should not also > connect (which, for whatever reason, becomes the default route in and > out of the system). > > ProblemType: Bug > DistroRelease: Ubuntu 10.10 > Package: network-manager 0.8.1+git.20100810t184654.ab580f4-0ubuntu2 > ProcVersionSignature: Ubuntu 2.6.35-22.33-generic 2.6.35.4 > Uname: Linux 2.6.35-22-generic x86_64 > NonfreeKernelModules: nvidia > Architecture: amd64 > CRDA: Error: [Errno 2] No such file or directory > Date: Wed Oct 6 08:54:52 2010 > IfupdownConfig: > auto lo > iface lo inet loopback > InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027) > IpRoute: > 192.168.1.0/24 dev eth0 proto kernel scope link src 192.168.1.139 metric 1 > 169.254.0.0/16 dev eth0 scope link metric 1000 > default via 192.168.1.1 dev eth0 proto static > Keyfiles: Error: [Errno 2] No such file or directory > ProcEnviron: > LANG=en_US.utf8 > SHELL=/bin/bash > SourcePackage: network-manager > > ** Affects: network-manager (Ubuntu) > Importance: Undecided > Status: New > > > ** Tags: amd64 apport-bug maverick > > -- > RFC: Ensure Wi-Fi is not used when copper is connected > https://bugs.launchpad.net/bugs/655706 > You received this bug notification because you are subscribed to > network-manager in ubuntu. > > Status in “network-manager” package in Ubuntu: New > > Bug description: > Binary package hint: network-manager > > Just a wishlist item for perhaps Natty. But it would be super if we could add the logic to disable or at least not auto-connect a wi-fi connection when there is an existing copper connection, or a copper connection is found. > > For example, when I boot my system with my GigE Network card connected to my GigE switch and infrastructure, my 802.11n wifi should not also connect (which, for whatever reason, becomes the default route in and out of the system). > > ProblemType: Bug > DistroRelease: Ubuntu 10.10 > Package: network-manager 0.8.1+git.20100810t184654.ab580f4-0ubuntu2 > ProcVersionSignature: Ubuntu 2.6.35-22.33-generic 2.6.35.4 > Uname: Linux 2.6.35-22-generic x86_64 > NonfreeKernelModules: nvidia > Architecture: amd64 > CRDA: Error: [Errno 2] No such file or directory > Date: Wed Oct 6 08:54:52 2010 > IfupdownConfig: > auto lo > iface lo inet loopback > InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027) > IpRoute: > 192.168.1.0/24 dev eth0 proto kernel scope link src 192.168.1.139 metric 1 > 169.254.0.0/16 dev eth0 scope link metric 1000 > default via 192.168.1.1 dev eth0 proto static > Keyfiles: Error: [Errno 2] No such file or directory > ProcEnviron: > LANG=en_US.utf8 > SHELL=/bin/bash > SourcePackage: network-manager > > -- RFC: Ensure Wi-Fi is not used when copper is connected https://bugs.launchpad.net/bugs/655706 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
