Undeletable and unchangeable "auto eth0" connection

[Kpykcb]

Binary package hint: network-manager-gnome

Default "Auto eth0" connection cannot be deleted or modified, so any time when system start
this connection autostart first, this is borring.

So that is the way i'm do.
On tray applet press RightMouseButton(Menu)>Change connections>Wired>Auto eth0, Press Delete.
Connection deteted, but after restart of system created again, with autostart enabled.
The same with modification, after reboot, to modified "Auto eth0" added new default "Auto eth0", with autostart enabled.

I'm expecting that no default connection will be created, if I have configured some already.
kpykc/~> lsb_release -rd
Description: Ubuntu 8.10
Release: 8.10
kpykc/~> apt-cache policy network-manager-gnome
network-manager-gnome:
  Встановлено: 0.7~~svn20081020t000444-0ubuntu1
  Кандидат: 0.7~~svn20081020t000444-0ubuntu1
  Таблиця версій:
 *** 0.7~~svn20081020t000444-0ubuntu1 0
        500 http://ua.archive.ubuntu.com intrepid/main Packages
        100 /var/lib/dpkg/status
kpykc/~> dpkg -l | gr network-manager
ii network-manager 0.7~~svn20081018t105859-0ubuntu1 network management framework daemon
ii network-manager-gnome 0.7~~svn20081020t000444-0ubuntu1 network management framework (GNOME frontend
ii network-manager-pptp 0.7~~svn20081015t024626-0ubuntu1.8.10.1 network management framework (PPTP plugin)

Same problem in ALTLinux bugtrack: https://bugzilla.altlinux.org/show_bug.cgi?id=17807

They fixed it, so new connection created if no other connections associated with eth0 interface.

[Denis Rut'kov (dendron2000)]

I confirm that. I wonder why it is still not fixed.

[Alexander Sack (asac)]

this was a bug in NM daemon and is fixed in jaunty

[Denis Rut'kov (dendron2000)]

Unfortunately no, it is not fixed in jaunty.

[Glenn Brumfield (gbrumfield)]

network manager 0.7.996 in Ubuntu alpha 6 still will not release auto eth0 if it detects a wired connection.

My case: I use a USB wireless card to connect to the internet. If I run Ubuntu in VirtualBox, metwork manager detects the virtual wired connection to VirtualBox and refuses to allow me to deselect auto eth0. Network manager detects the wireless USB card but refuses to use it as long as it detects the virtual wired connection. I can connect to the wireless router in the host system (Ubuntu 8.04.3) and pass it along to the guest system on auto eth0. If I deselect auto eth0 in the guest system, it claims to disconnect then immediately reconnects, preventing me from using the USB wireless card.

I run Ubuntu Karmic alpha 6 in VirtualBox 3.0.6 on Ubuntu 8.04.3.

[c.fischer (cflp)]

I use Kubuntu Karmic and can confirm this issue.

Also i fail to see why this is rated as "medium" rather than "high".
Networking is of central importance to a system today.
I need to switch network settings easily in order to work professionally with my system in varying environments, hence the need for a management utility. This includes static wired setups.
I need to have a static ip, in order to serve stuff from my system to the local network.
Currently this means _after each logoff/reboot_:
1. I have to log in
2. I have to change the active connection (from Auto eth0)
3. I have to stay logged in (e.g. over night, so other devices can acces the system via static IP) as opposed to log off and let the system run on log-in-screen.

tl;dr:
It might seem like a minor problem, yet it has a lot of consequences.

<rant>
Network management worked in Kubuntu 8.04, afaic.
I find the persistance of this bug rather disappointing.
<rant off>

[cwsupport (netsupport)]

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.

[Mathieu Trudel-Lapierre (cyphermox)]

Looking through the code, this really looks fixed if not in Karmic, then definitely in Lucid and later releases. That's what the "no-auto-default=<mac address>," key in /etc/NetworkManager/nm-system-settings.conf is for, and is automatically added when Auto eth0 is created so that it doesn't get re-added if deleted.

Since we're talking wildly different code between 0.7 and 0.8, please open a new bug using ubuntu-bug (and tell us the number here) if you see that it is still broken in Karmic or Lucid.