Network is not configured *till* I log into GDM

[wolfcub]

Binary package hint: network-manager

I'm running Ubuntu 9.04 (Jaunty). I connect to a WEP-enabled wifi network on this system. While recently configuring my system to boot into the console instead of GDM, I discovered that the network is not configured *till* I log into GDM.

At the end of the boot sequence, there's no network on eth1 where the it is normally configured. It gets configured once I log into GDM. Note that I have another Ubuntu system running 9.04 and that system connects to the same network on bootup without issues.

Note: The network should be configured on eth1. The contents of /var/log/syslog are attached. Relevant snippet below.

Before logging into GDM:

Aug 10 09:42:45 Fjords NetworkManager: <info> (eth0): device state change: 1 -> 2
Aug 10 09:42:45 Fjords NetworkManager: <info> (eth0): bringing up device.
Aug 10 09:42:45 Fjords NetworkManager: <info> (eth0): preparing device.
Aug 10 09:42:45 Fjords NetworkManager: <info> (eth0): deactivating device (reason: 2).
Aug 10 09:42:45 Fjords NetworkManager: <info> Unmanaged Device found; state CONNECTED forced. (see http://bugs.launchpad.net/bugs/191889)
Aug 10 09:42:45 Fjords NetworkManager: <info> Unmanaged Device found; state CONNECTED forced. (see http://bugs.launchpad.net/bugs/191889)
Aug 10 09:42:45 Fjords NetworkManager: <info> (eth1): device state change: 1 -> 2
Aug 10 09:42:45 Fjords NetworkManager: <info> (eth1): bringing up device.
Aug 10 09:42:45 Fjords NetworkManager: <info> (eth1): preparing device.
Aug 10 09:42:45 Fjords NetworkManager: <info> (eth1): deactivating device (reason: 2).
Aug 10 09:42:45 Fjords NetworkManager: <info> (eth1): device state change: 2 -> 3
Aug 10 09:42:45 Fjords kernel: [ 33.482254] eth0: link down
Aug 10 09:42:45 Fjords kernel: [ 33.482362] ADDRCONF(NETDEV_UP): eth0: link is not ready
Aug 10 09:42:45 Fjords nm-system-settings: Added default wired connection 'Auto eth0' for /org/freedesktop/Hal/devices/net_00_16_d3_40_cb_2c
Aug 10 09:42:45 Fjords NetworkManager: <info> (eth1): supplicant interface state: starting -> ready
Aug 10 09:42:46 Fjords avahi-daemon[2947]: Registering new address record for fe80::216:6fff:fe97:cd84 on eth1.*.
Aug 10 09:42:51 Fjords kernel: [ 40.297487] [drm:i915_get_vblank_counter] *ERROR* trying to get vblank count for disabled pipe 0
Aug 10 09:42:55 Fjords kernel: [ 43.960160] eth1: no IPv6 routers present

After logging into GDM:
Aug 10 09:44:33 Fjords NetworkManager: <info> Activation (eth1) starting connection 'Auto O2wireless358AD3'
Aug 10 09:44:33 Fjords NetworkManager: <info> (eth1): device state change: 3 -> 4
Aug 10 09:44:33 Fjords NetworkManager: <info> Activation (eth1) Stage 1 of 5 (Device Prepare) scheduled...
Aug 10 09:44:33 Fjords NetworkManager: <info> Activation (eth1) Stage 1 of 5 (Device Prepare) started...
Aug 10 09:44:33 Fjords NetworkManager: <info> Activation (eth1) Stage 2 of 5 (Device Configure) scheduled...
Aug 10 09:44:33 Fjords NetworkManager: <info> Activation (eth1) Stage 1 of 5 (Device Prepare) complete.
Aug 10 09:44:33 Fjords NetworkManager: <info> Activation (eth1) Stage 2 of 5 (Device Configure) starting...
Aug 10 09:44:33 Fjords NetworkManager: <info> (eth1): device state change: 4 -> 5
Aug 10 09:44:33 Fjords NetworkManager: <info> Activation (eth1/wireless): access point 'Auto O2wireless358AD3' has security, but secrets are required.
Aug 10 09:44:33 Fjords NetworkManager: <info> (eth1): device state change: 5 -> 6
Aug 10 09:44:33 Fjords NetworkManager: <info> Activation (eth1) Stage 2 of 5 (Device Configure) complete.
Aug 10 09:44:33 Fjords NetworkManager: <info> Activation (eth1) Stage 1 of 5 (Device Prepare) scheduled...
Aug 10 09:44:33 Fjords NetworkManager: <info> Activation (eth1) Stage 1 of 5 (Device Prepare) started...
Aug 10 09:44:33 Fjords NetworkManager: <info> (eth1): device state change: 6 -> 4
Aug 10 09:44:33 Fjords NetworkManager: <info> Activation (eth1) Stage 2 of 5 (Device Configure) scheduled...
Aug 10 09:44:33 Fjords NetworkManager: <info> Activation (eth1) Stage 1 of 5 (Device Prepare) complete.
Aug 10 09:44:33 Fjords NetworkManager: <info> Activation (eth1) Stage 2 of 5 (Device Configure) starting...
Aug 10 09:44:33 Fjords NetworkManager: <info> (eth1): device state change: 4 -> 5
Aug 10 09:44:33 Fjords NetworkManager: <info> Activation (eth1/wireless): connection 'Auto O2wireless358AD3' has security, and secrets exist. No new secrets needed.
Aug 10 09:44:33 Fjords NetworkManager: <info> Config: added 'ssid' value 'O2wireless358AD3'
Aug 10 09:44:33 Fjords NetworkManager: <info> Config: added 'scan_ssid' value '1'
Aug 10 09:44:33 Fjords NetworkManager: <info> Config: added 'key_mgmt' value 'NONE'
Aug 10 09:44:33 Fjords NetworkManager: <info> Config: added 'auth_alg' value 'OPEN'
Aug 10 09:44:33 Fjords NetworkManager: <info> Config: added 'wep_key0' value '<omitted>'
Aug 10 09:44:33 Fjords NetworkManager: <info> Config: added 'wep_tx_keyidx' value '0'
...

... and so on till inteface eth1 is fully configured.

Contents of /etc/network/interfaces file on both computers are same:

pine@Fjords:~$ cat /etc/network/interfaces
auto lo
iface lo inet loopback

[wolfcub (nagulesan)]

I've figured out why the network was configured on my other Ubuntu system, and am consequently able to do the same on this system: "Available to all users" option was selected on the default connection in the Network Manager applet. This enabled the system to configure the network even though I'm not logged in through GDM. I've verified that the network gets configured on this system too when the option is turned on.

On a side note, it would be nice if available networks could be detected and configured via console in a similar manner to how the Network Manager applet behaves. I guess that now my network is auto-configured so I can turn off GDM during boot and still remotely connect to the system.

[wolfcub (nagulesan)]

Leaving this open as I don't see an option to close this bug-report ..

[komputes (komputes)]

@wolfclub - Marking as invalid (equivalent to the bug being voided/closed). If you find that you need to re-open the bug, simply change the status back to new. Thank you.