subject:"\[Bug 279262\] Re\: \[regression\] devices\/interfaces not set to auto in \/etc\/network\/interfaces get blacklisted in 0.7 \(intrepid\) but were managed in 0.6 \(hardy and before\)"

[Bug 279262] Re: [regression] devices/interfaces not set to auto in /etc/network/interfaces get blacklisted in 0.7 (intrepid) but were managed in 0.6 (hardy and before)

2011-01-06 Thread Adam Porter

One problem as I see it is that the Network Manager applets/widgets
should have a simple option to changed unmanaged devices to managed.
All it takes is for a managed=true line in nm-settings.conf to be
changed to managed=false and Network Manager is stuck!  The only way
to fix it is to fix that configuration file, and if a user can't get
online to find the solution, he'll be stuck!  (And probably will switch
to Windows, too.)

This or a similar problem happened when I ran nm-applet in KDE because
of plasma-widget-networkmanager's inability to handle DSL PPPoE
connections.  Suddenly after rebooting, the line in the conf file was
set to managed=false, and the widget lacks the ability to return the
device to managed mode, and so I couldn't get online.  Deleting the file
and restarting NM fixes it, or doing:

$(sudo sed -i s/managed=false/managed=true/g /etc/NetworkManager/nm-
system-settings.conf  sudo restart network-manager)

fixes it also.

I remember encountering this bug over a year ago when testing a newer
release of Kubuntu...and so I stayed with Hardy.  But here we are in
Maverick and the bug is still there.  *sigh*

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/279262

Title:
  [regression] devices/interfaces not set to auto in /etc/network/interfaces 
get blacklisted in 0.7 (intrepid) but were managed in 0.6 (hardy and before)

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 279262] Re: [regression] devices/interfaces not set to auto in /etc/network/interfaces get blacklisted in 0.7 (intrepid) but were managed in 0.6 (hardy and before)

2010-06-16 Thread cwsupport

Just a quick bit of info as I saw a similar problem...which may or may
not have been related on 9.10.

The problem as I see it was caused by have a static ip setup on eth0 -
but the network manager was 'swiping' the connection and attempting dhcp
(which is not available on the particular network).  I found that the
following changes to my /etc/network/interfaces cured problems.

1. On lines following iface use a tab to indent not spaces.
2. Between keywords and data (i.e. netmask 255.255.0.0) use a single space not 
multiple spaces.

After a reboot this cured my problems.

-- 
[regression] devices/interfaces not set to auto in /etc/network/interfaces 
get blacklisted in 0.7 (intrepid) but were managed in 0.6 (hardy and before)
https://bugs.launchpad.net/bugs/279262
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 279262] Re: [regression] devices/interfaces not set to auto in /etc/network/interfaces get blacklisted in 0.7 (intrepid) but were managed in 0.6 (hardy and before)

2009-04-26 Thread cristian

I upgraded to Jaunty final release and the bug still persist. is someone
working at this or like in intrepid the bug will persist until the next
release.

-- 
[regression] devices/interfaces not set to auto in /etc/network/interfaces 
get blacklisted in 0.7 (intrepid) but were managed in 0.6 (hardy and before)
https://bugs.launchpad.net/bugs/279262
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 279262] Re: [regression] devices/interfaces not set to auto in /etc/network/interfaces get blacklisted in 0.7 (intrepid) but were managed in 0.6 (hardy and before)

2009-04-26 Thread Dave Jakeman

I too have a static IP address config and got hit by this problem
attempting to upgrade from 8.04 to 9.04 (via 8.10).  So I wiped and did
a clean install of 9.04 and static IP configuration then worked fine.
Not a fix for those that want to upgrade though.

-- 
[regression] devices/interfaces not set to auto in /etc/network/interfaces 
get blacklisted in 0.7 (intrepid) but were managed in 0.6 (hardy and before)
https://bugs.launchpad.net/bugs/279262
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Re: [Bug 279262] Re: [regression] devices/interfaces not set to auto in /etc/network/interfaces get blacklisted in 0.7 (intrepid) but were managed in 0.6 (hardy and before)

2009-04-01 Thread Nausser

Really the easiest way is to just do a ip address reservation for your
NIC's MAC address on your DHCP server. That way when this long drawn
out bug is finally fixed, you won't have to do any special re-config
of anything.

On Thu, Dec 4, 2008 at 9:14 AM, Alexander Sack a...@jwsdot.com wrote:
On Sat, Nov 08, 2008 at 07:44:40PM -, Dave Jakeman wrote:
Just back from wiping/installing 8.10 (full) and trying to set up my
static wired connections.

On the first attempt, I configured my connections and they were accepted
without a read-only error. Couldn't get onto the internet though.
Went back to check, and both connection definitions had vanished.
Reconfigured them again and this time renamed them from auto eth0 and
auto eth1 to Wired Ethernet 1 and Wired Ethernet 2. This time,
they were stored and I could surf with Firefox. On reboot though, both
the connections had disappeared again.

Auto connections are read-only. Its a bug that you dont get an
error. You need to create new connections if you want to do your own stuff.

- Alexander

--
[regression] devices/interfaces not set to auto in /etc/network/interfaces
get blacklisted in 0.7 (intrepid) but were managed in 0.6 (hardy and before)
https://bugs.launchpad.net/bugs/279262
You received this bug notification because you are a direct subscriber
of a duplicate bug.

Status in “network-manager” source package in Ubuntu: Triaged
Status in network-manager in Ubuntu Intrepid: Won't Fix

Bug description:
the regression here is that devices are unmanaged even though they dont have
a auto eth0 line in /etc/network/interfaces

Here an example of an interfaces configuration that should not set the
devices in unmanaged mode
https://bugs.edge.launchpad.net/ubuntu/+source/network-manager/+bug/279262/comments/14

To reproduce:
use the /etc/network/interfaces configuration from the above comment and see
that after restart the device is unmanaged in intrepid, but managed in hardy
(0.6).

The code we shipped in NM 0.6 that shows that auto connections were
blacklisted is:

for (curr_b = ifparser_getfirst (); curr_b; curr_b = curr_b-next) {
if ((!strcmp (curr_b-type, auto) || !strcmp (curr_b-type,
allow-hotplug))
strstr (curr_b-name, iface))
blacklist = TRUE;
}

The proposed patch is committed to the ubuntu.0.7 branch (see Related
Branches section in this bug) and can be seen here:
http://bazaar.launchpad.net/~network-manager/network-manager/ubuntu.0.7/annotate/2957?file_id=012ifupdownunmanagea-20081022120139-7rgnlk84604f1ysu-1

Test packages with that patch are available:
https://edge.launchpad.net/~network-manager/+archive

Impact:
1. no impact for new users
2. no impact for users that installed in gutsy or later and didnt modify
their /etc/network/interfaces (e.g. through gnome network-admin)
3. users with dhcp that installed before that will most likely see their
interface as being unmanaged and not upped on startup even though those
interfaces were previously managed by NM. Note: we transitioned those old
installs in gutsy to NM by commenting just the auto ethX lines in
/etc/network/interfaces.

54 matches

Mail list logo