adsmith's script doesn't work on Precise so I've reworked it and removed
the dependency on naming interfaces. My script will act whenever any
"eth*" interface comes or goes. It also logs to
"/var/log/NetworkManager.log".
Install to /etc/NetworkManager/prefer_wired_over_radio.sh
Once copied to tha
I actually like the new behaviour better, the old behaviour annoyed me
because I often need to work with two active connections to different
networks.
--
brings up both wired and wireless interfaces; hard to pick just one through the
UI
https://bugs.launchpad.net/bugs/262152
You received this bu
Here is an easy fix. Put this script early in both /etc/network/if-up.d
and /etc/network/if-down.d.
** Attachment added: "bring down wifi when eth0 is up, and reverse."
http://launchpadlibrarian.net/31502979/00abe-notboth
--
brings up both wired and wireless interfaces; hard to pick just one
Another issue in Jaunty is that there is an occasion where Jaunty will not
recognize a cross over cable.
On Fri, May 29, 2009 at 11:07 PM, David S.
wrote:
> This bug is still present in Jaunty.
>
> --
> brings up both wired and wireless interfaces; hard to pick just one through
> the UI
> https:
This bug is still present in Jaunty.
--
brings up both wired and wireless interfaces; hard to pick just one through the
UI
https://bugs.launchpad.net/bugs/262152
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing li
the routing issues with multiple devices should be fixed in jaunty.
** Changed in: network-manager (Ubuntu)
Status: Triaged => Won't Fix
--
brings up both wired and wireless interfaces; hard to pick just one through the
UI
https://bugs.launchpad.net/bugs/262152
You received this bug noti
This fix didnt go in intrepid right?? when will this be fixed?
--
brings up both wired and wireless interfaces; hard to pick just one through the
UI
https://bugs.launchpad.net/bugs/262152
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Yes, and in some cases it's the policy of the network administrator to
strictly forbid connecting to both wired and wireless in the same
building. If they are different subnets, you have the potential to act
as a network bridge (yes I know this takes effort, but the potential is
still there). We ha
There is a similar report of Fedora:
https://bugzilla.redhat.com/show_bug.cgi?id=454955
There the devs say it is intended behavior for NM to connect to all networks
that are marked "auto connect".
However, I think there should be an option to only allow one connection at a
time, with some prior
@jasonwc:
wajig worked. The held state is honoured by both update-manager and synaptic,
which was exactly what I was looking for. And wajig is a very cool utility;
I'll be installing it on ALL of my machines, whether I need to hold packages at
specific versions or not.
I've updated my pptp rant
William,
There's a simpler solution.
apt-get install wajig
wajig hold package
--
brings up both wired and wireless interfaces; hard to pick just one through the
UI
https://bugs.launchpad.net/bugs/262152
You received this bug notification because you are a member of Ubuntu
Bugs, which is subsc
@ Dmik: Simple is a relative word, but here goes: The first workaround I
did to restore 0.6 behavior was to add Hardy's repositories back into
software sources, then use aptitude to downgrade all five related
packages to 0.6.x and mark them Held at the older version. That worked
fine, but it was an
In many cases it's not so much annoying as wasting resources (there is
absolutely no point to have two active connections to the same router).
I think that the default (one active connection at a time, wired
preferred) should be restored. Of course, there are situations when
several connections sho
I notice the new Eject icons in nautilus' sidebar for removable devices
and wonder if network manager's connection list could have something
similar.
--
brings up both wired and wireless interfaces; hard to pick just one through the
UI
https://bugs.launchpad.net/bugs/262152
You received this bug
I think bug 278485 is related. NM seems in general unable to handle well
more than one connection at a time.
--
brings up both wired and wireless interfaces; hard to pick just one through the
UI
https://bugs.launchpad.net/bugs/262152
You received this bug notification because you are a member of
An additional problem is that if both wired and wireless are enabled,
the icon only indicates the status of the wired network, although I was
connected to a (very weak) wireless connection.
--
brings up both wired and wireless interfaces; hard to pick just one through the
UI
https://bugs.launchp
This is a regression from previous behavior, which I got used to as the
reporter mentions. Under Hardy/Gutsy, you only got one nm-managed
interface brought up out of several available (wired and wireless), with
wired preferred. When you unplug wired, it brings up wireless.
So, it's doing it for
Yes, it is, because I want network-manager to connect to wireless
automatically when I unplug the Ethernet cable.
ifconfig and route -n are attached. eth0 is Ethernet, eth1 is wireless.
Note that network-manager has given both eth0 and eth1 (excluding the
link-local route) the same metric.
** Att
is your wireless connection marked as "connect automatically" in
connection-editor?
--
brings up both wired and wireless interfaces; hard to pick just one through the
UI
https://bugs.launchpad.net/bugs/262152
You received this bug notification because you are a member of Ubuntu
Bugs, which is su
quite annoying, i agree.
** Changed in: network-manager (Ubuntu)
Importance: Undecided => Medium
Status: New => Triaged
Target: None => ubuntu-8.10-beta
--
brings up both wired and wireless interfaces; hard to pick just one through the
UI
https://bugs.launchpad.net/bugs/262152
20 matches
Mail list logo
