Disconnected static wired network initially treated as connected

Still same behaviour in kernel -8 and -9.

Have found that a suspend / resume cycle will give priority to the wireless network.

From rudimentary analysis of conditions, I suspect somehow on boot the wired connection is being detected as live, kicking in the override. A re-detection of the status is done on resume and this fixes it.

as /init.d/NetworkManager restart doesn't fix it, I am a bit stuck. I have no idea how this system works, or what package is responsible for setting connection hardware priority, or what causes a re-detection.

Changed title to something more accurate

Also notice there is no way to edit the settings presented in NetworkManager. A /init.d/NetworkManager restart makes no difference.

I tell a lie, there is, but it seems to require you add something first. Very odd as you would think you should have to be SU to delete existing settings.

Would you mind trying the current development code in the Network Manager PPA (https://launchpad.net/~network-manager/+archive/trunk)?

Also, when you see this problem, would you please run nm-tool, and report the results?

In a state where the problem occurs

In a stat with problem after install from
https://launchpad.net/~network-manager/+archive/trunk

State after resume before development trunk install

State after resume after development trunk install

Is this your /etc/network/interfaces file?

auto lo
iface lo inet loopback

iface eth0 inet static
address 134.219.128.31
netmask 255.255.252.0
gateway 134.219.128.1

auto eth0

Can you explain why you have configured eth0 that way? I believe that it may be confusing NetworkManager.

I do agree that there seems to be an error in terms of eth0 initially being considered conected when a cable is not present. Please confirm: that's the problem, yes? On an initial boot, without a cable being plugged into the wired port, eth0 is considered connected?

Yes that is the file

As for configured that way, I recognize the IP as one I was using a year or so ago so it is probably a legacy of then.
this current system is an upgrade of a jaunty install, itself an upgrade of an intrepid install iirc. The system was working fine with whatever settings there are / were for the past months, pre Karmic Alpha 3 iirc; so any manual configuration of such settings would have been long enough ago for me to not remember. (certainly as I haven't been in that IP range since May)

yes on initial boot, Network manager (via icon) is showing an Ethernet connection when there is no cable present.

Fixed by suspend-resume or plugging and removing a cable. Then normal behavior

Try removing all references to eth0 from /e/n/i and reboot. Please let us know if it starts working. I still don't like that it is marking a non-existent wired connection as present, but let's see what that change does for you. It should recognize the eth0 hardware, and since *nothing* is in /e/n/i, it should make it auto for you, and manage it.

That seems to have fixed the issues for me, it now shows no wired connection on boot.

wired kicks in correctly upon connecting to a DHCP enables system, and drops off and reverts to wireless as expected when the cable is removed.

Thanks

Is there any help I can provide in discovering the source of the phantom live connection?

> Is there any help I can provide in discovering the source of the phantom live connection?

I believe that we already know the source of the problem, thanks to your nm-tool output. It would certainly be helpful if you would test it when it hits the PPA.

Thanks. :-)

upstream commit: 0bbf8c530746c6171aa3a36e2b25a166adf49a04

This bug was fixed in the package network-manager - 0.8~a~git.20091005t192303.1d28ad1-0ubuntu1

---------------
network-manager (0.8~a~git.20091005t192303.1d28ad1-0ubuntu1) karmic; urgency=low

  * upstream snapshot 2009-10-05 19:23:03 (GMT)
    + 1d28ad1aa54bacf6b6b64582ee7c41d9728d7304
  * fixed upstream
    - LP: #413622 - Network manager does not unmanage devices configured as
      "mapping" in /etc/network/interfaces
    - LP: #413967 - Network manager does not connect wlan0 on startup
    - LP: #417719 - Disconnected static wired network initially treated as
      connected
    - LP: #422597 - 802.11x fails for wired connections (wireless works)
    - LP: #438771 - Creating a wireless or DSL connection fails with
      "Error editing connection: property '%s' / '%s' invalid: %d"
    - LP: #443423 - Connection properties are not stored
    - LP: #439221 - cannot create wireless Wpa & Wpa2 connection with GUI
    - LP: #441668 - network-manager does not save modifications on GSM
      connections
    - LP: #438454 - NetworkManager fails to set IP and route information entered

  [ Mathieu Trudel <email address hidden> ]
  * updated pkcs11 smartcard patch
    - updated debian/patches/lp120363_smartcard_pkcs11.patch
  * add new 802.1x symbols to libnm-util1.symbols
    - update debian/libnm-util1.symbols

  [ Alexander Sack <email address hidden> ]
  * drop cherry-pick now applied upstream
    - delete debian/patches/lp436884.patch
    - update debian/patches/series
  * extend apport hook to also append /etc/NetworkManager/nm-system-settings.conf
    - update debian/source_network-manager.py

 -- Alexander Sack <email address hidden> Mon, 05 Oct 2009 23:46:01 +0200