networkmanager issue in beta1

English Install/Boot/Login
1

Networkmanager does not start at first login.

In KDE, the plasmoid says it is not started yet.
Logout/Login, it is available and connects

In e17, nm should start via gnome-networkmanager.
At first login, it says “system is not compatible with this version”
At second login, it sees the 3G-Modem I am using, but wants a new configuration and connects then
So I establish connection with KDE and login to e17, seems to be easier than deleting all the entries in nm-configuration

I found a bug-report

https://bugzilla.novell.com/show_bug.cgi?id=800251

and left a comment.

Any similar experiences here?

Martin

2

On 02/05/2013 05:06 PM, martinrehm wrote:
>
> Networkmanager does not start at first login.
>
> In KDE, the plasmoid says it is not started yet.
> Logout/Login, it is available and connects
>
> In e17, nm should start via gnome-networkmanager.
> At first login, it says “system is not compatible with this version”
> At second login, it sees the 3G-Modem I am using, but wants a new
> configuration and connects then
> So I establish connection with KDE and login to e17, seems to be easier
> than deleting all the entries in nm-configuration
>
> I found a bug-report
>
> https://bugzilla.novell.com/show_bug.cgi?id=800251
>
> and left a comment.
>
> Any similar experiences here?

No. In KDE, it works as I expect. The only thing unusual about my configuration
is that all connection possibilities (I have 5 APs) have both the “System
Connection” and “Connect Automatically” boxes are unchecked.

3

I am having what may be a similar problem.

I upgraded from SuSe 12.2 to 12.3 beta, via the downloadable distro dvd. Everything was fine, network wise.

I use a wireless connection, network manager is configured as system connection, connect automatically.

After a recent update from the 12.3 repositories, I found on rebooting the system, that some of my apps and plasmoids were complaining that they could not connect to the network. The network manager plasmoid says the network is connected, but a ping sent from a console window report network not connected. My system is up to date as of this morning.

NetworkManager 0.9.6.4-5.2.1
NetworkManager-gnome 0.9.6.4-2.2.1
NetworkManager-kde4-libs 0.9.0.7-244.3

All the rest are version 0.9.6.0-2.1.1 except -vpnc and -vpnc-gnome which are version 0.9.6.0-3.1.2

If I go back to the network manager plasmoid and uncheck the ‘enable networking’ box, followed by re-checking it, the network restarts and is now available. I have to log out and log in again to get the plasmoids working, but the network is now connected.

Obviously, network manager is missing some crucial steps on its first connection, but I do not know how to fix it. Anyone who can help me, please?

Here is the Network manager log for the first initialization, then my disable/enable request:-

2013-02-08T10:22:55.773247-05:00 linux-fzs3 NetworkManager[577]: <info> disable requested (sleeping: no enabled: yes)
2013-02-08T10:22:55.773691-05:00 linux-fzs3 NetworkManager[577]: <info> sleeping or disabling…
2013-02-08T10:22:55.774453-05:00 linux-fzs3 NetworkManager[577]: <info> (eth0): now unmanaged
2013-02-08T10:22:55.775241-05:00 linux-fzs3 NetworkManager[577]: <info> (eth0): device state change: unavailable → unmanaged (reason ‘sleeping’) [20 10 37]
2013-02-08T10:22:55.775929-05:00 linux-fzs3 NetworkManager[577]: <info> (eth0): cleaning up…
2013-02-08T10:22:55.776620-05:00 linux-fzs3 NetworkManager[577]: <info> (eth0): taking down device.
2013-02-08T10:22:55.779746-05:00 linux-fzs3 NetworkManager[577]: <info> (wlan0): now unmanaged
2013-02-08T10:22:55.780136-05:00 linux-fzs3 NetworkManager[577]: <info> (wlan0): device state change: activated → unmanaged (reason ‘sleeping’) [100 10 37]
2013-02-08T10:22:55.851721-05:00 linux-fzs3 NetworkManager[577]: <info> (wlan0): deactivating device (reason ‘sleeping’) [37]
2013-02-08T10:22:56.052157-05:00 linux-fzs3 NetworkManager[577]: <info> (wlan0): canceled DHCP transaction, DHCP client pid 1141
2013-02-08T10:22:56.062374-05:00 linux-fzs3 NetworkManager[577]: <info> Clearing nscd hosts cache.
2013-02-08T10:22:56.063270-05:00 linux-fzs3 NetworkManager[577]: sent invalidate(hosts) request, exiting
2013-02-08T10:22:56.063640-05:00 linux-fzs3 NetworkManager[577]: <info> (wlan0): cleaning up…
2013-02-08T10:22:56.063984-05:00 linux-fzs3 NetworkManager[577]: <info> (wlan0): taking down device.
2013-02-08T10:22:59.520880-05:00 linux-fzs3 NetworkManager[577]: <info> enable requested (sleeping: no enabled: no)
2013-02-08T10:22:59.521290-05:00 linux-fzs3 NetworkManager[577]: <info> waking up and re-enabling…
2013-02-08T10:22:59.521619-05:00 linux-fzs3 NetworkManager[577]: <info> WWAN now enabled by management service
2013-02-08T10:22:59.522470-05:00 linux-fzs3 NetworkManager[577]: <info> (eth0): now managed
2013-02-08T10:22:59.523265-05:00 linux-fzs3 NetworkManager[577]: <info> (eth0): device state change: unmanaged → unavailable (reason ‘managed’) [10 20 2]
2013-02-08T10:22:59.524113-05:00 linux-fzs3 NetworkManager[577]: <info> (eth0): bringing up device.
2013-02-08T10:22:59.705149-05:00 linux-fzs3 NetworkManager[577]: <info> (eth0): preparing device.
2013-02-08T10:22:59.706327-05:00 linux-fzs3 NetworkManager[577]: <info> (eth0): deactivating device (reason ‘managed’) [2]
2013-02-08T10:22:59.711723-05:00 linux-fzs3 NetworkManager[577]: <info> (wlan0): now managed
2013-02-08T10:22:59.711766-05:00 linux-fzs3 NetworkManager[577]: <info> (wlan0): device state change: unmanaged → unavailable (reason ‘managed’) [10 20 2]
2013-02-08T10:22:59.711786-05:00 linux-fzs3 NetworkManager[577]: <info> (wlan0): bringing up device.
2013-02-08T10:22:59.941722-05:00 linux-fzs3 NetworkManager[577]: <info> (wlan0): preparing device.
2013-02-08T10:22:59.942294-05:00 linux-fzs3 NetworkManager[577]: <info> (wlan0): deactivating device (reason ‘managed’) [2]
2013-02-08T10:22:59.951831-05:00 linux-fzs3 NetworkManager[577]: <info> (wlan0) supports 5 scan SSIDs
2013-02-08T10:22:59.952471-05:00 linux-fzs3 NetworkManager[577]: <info> (wlan0): supplicant interface state: starting → ready
2013-02-08T10:22:59.952974-05:00 linux-fzs3 NetworkManager[577]: <info> (wlan0): device state change: unavailable → disconnected (reason ‘supplicant-available’)
20 30 42]
2013-02-08T10:22:59.953500-05:00 linux-fzs3 NetworkManager[577]: <warn> Trying to remove a non-existant call id.
2013-02-08T10:22:59.954001-05:00 linux-fzs3 NetworkManager[577]: <info> (wlan0): supplicant interface state: ready → inactive
2013-02-08T10:22:59.954532-05:00 linux-fzs3 NetworkManager[577]: <info> (wlan0) supports 5 scan SSIDs
2013-02-08T10:23:00.353644-05:00 linux-fzs3 NetworkManager[577]: <info> Auto-activating connection ‘NETGEAR’.
2013-02-08T10:23:00.354744-05:00 linux-fzs3 NetworkManager[577]: <info> Activation (wlan0) starting connection ‘NETGEAR’
2013-02-08T10:23:00.356685-05:00 linux-fzs3 NetworkManager[577]: <info> (wlan0): device state change: disconnected → prepare (reason ‘none’) [30 40 0]
2013-02-08T10:23:00.360386-05:00 linux-fzs3 NetworkManager[577]: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) scheduled…
2013-02-08T10:23:00.360432-05:00 linux-fzs3 NetworkManager[577]: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) started…
2013-02-08T10:23:00.360449-05:00 linux-fzs3 NetworkManager[577]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) scheduled…
2013-02-08T10:23:00.360534-05:00 linux-fzs3 NetworkManager[577]: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) complete.
2013-02-08T10:23:00.361286-05:00 linux-fzs3 NetworkManager[577]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) starting…
2013-02-08T10:23:00.361826-05:00 linux-fzs3 NetworkManager[577]: <info> (wlan0): device state change: prepare → config (reason ‘none’) [40 50 0]
2013-02-08T10:23:00.362260-05:00 linux-fzs3 NetworkManager[577]: <info> Activation (wlan0/wireless): connection ‘NETGEAR’ requires no security. No secrets needed.
2013-02-08T10:23:00.362686-05:00 linux-fzs3 NetworkManager[577]: <info> Config: added ‘ssid’ value ‘NETGEAR’
2013-02-08T10:23:00.363121-05:00 linux-fzs3 NetworkManager[577]: <info> Config: added ‘scan_ssid’ value ‘1’
2013-02-08T10:23:00.363549-05:00 linux-fzs3 NetworkManager[577]: <info> Config: added ‘key_mgmt’ value ‘NONE’
2013-02-08T10:23:00.363919-05:00 linux-fzs3 NetworkManager[577]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) complete.
2013-02-08T10:23:00.364211-05:00 linux-fzs3 NetworkManager[577]: <info> Config: set interface ap_scan to 1
2013-02-08T10:23:00.370598-05:00 linux-fzs3 NetworkManager[577]: <info> (wlan0): supplicant interface state: inactive → scanning
2013-02-08T10:23:00.842726-05:00 linux-fzs3 NetworkManager[577]: <info> (wlan0): supplicant interface state: scanning → authenticating
2013-02-08T10:23:00.849361-05:00 linux-fzs3 NetworkManager[577]: <info> (wlan0): supplicant interface state: authenticating → associating
2013-02-08T10:23:00.856770-05:00 linux-fzs3 NetworkManager[577]: <info> (wlan0): supplicant interface state: associating → completed
2013-02-08T10:23:00.857342-05:00 linux-fzs3 NetworkManager[577]: <info> Activation (wlan0/wireless) Stage 2 of 5 (Device Configure) successful. Connected to wireless network ‘NETGEAR’.
2013-02-08T10:23:00.857819-05:00 linux-fzs3 NetworkManager[577]: <info> Activation (wlan0) Stage 3 of 5 (IP Configure Start) scheduled.
2013-02-08T10:23:00.858361-05:00 linux-fzs3 NetworkManager[577]: <info> Activation (wlan0) Stage 3 of 5 (IP Configure Start) started…
2013-02-08T10:23:00.858865-05:00 linux-fzs3 NetworkManager[577]: <info> (wlan0): device state change: config → ip-config (reason ‘none’) [50 70 0]
2013-02-08T10:23:00.859389-05:00 linux-fzs3 NetworkManager[577]: <info> Activation (wlan0) Beginning DHCPv4 transaction (timeout in 45 seconds)
2013-02-08T10:23:00.859901-05:00 linux-fzs3 NetworkManager[577]: <info> dhclient started with pid 6667
2013-02-08T10:23:00.860392-05:00 linux-fzs3 NetworkManager[577]: <info> Activation (wlan0) Stage 3 of 5 (IP Configure Start) complete.
2013-02-08T10:23:00.873614-05:00 linux-fzs3 NetworkManager[577]: <info> (wlan0): DHCPv4 state changed nbi → preinit
2013-02-08T10:23:00.927750-05:00 linux-fzs3 NetworkManager[577]: <info> (wlan0): DHCPv4 state changed preinit → reboot
2013-02-08T10:23:00.927777-05:00 linux-fzs3 NetworkManager[577]: <info> address 192.168.1.4
2013-02-08T10:23:00.927784-05:00 linux-fzs3 NetworkManager[577]: <info> prefix 24 (255.255.255.0)
2013-02-08T10:23:00.927790-05:00 linux-fzs3 NetworkManager[577]: <info> gateway 192.168.1.1
2013-02-08T10:23:00.927863-05:00 linux-fzs3 NetworkManager[577]: <info> nameserver ‘192.168.1.1’
2013-02-08T10:23:00.928132-05:00 linux-fzs3 NetworkManager[577]: <info> Activation (wlan0) Stage 5 of 5 (IPv4 Configure Commit) scheduled…
2013-02-08T10:23:00.928401-05:00 linux-fzs3 NetworkManager[577]: <info> Activation (wlan0) Stage 5 of 5 (IPv4 Commit) started…
2013-02-08T10:23:01.928904-05:00 linux-fzs3 NetworkManager[577]: <info> (wlan0): device state change: ip-config → activated (reason ‘none’) [70 100 0]
2013-02-08T10:23:02.036003-05:00 linux-fzs3 NetworkManager[577]: <info> Clearing nscd hosts cache.
2013-02-08T10:23:02.040774-05:00 linux-fzs3 NetworkManager[577]: sent invalidate(hosts) request, exiting
2013-02-08T10:23:02.041320-05:00 linux-fzs3 NetworkManager[577]: <info> Policy set ‘NETGEAR’ (wlan0) as default for IPv4 routing and DNS.
2013-02-08T10:23:02.041807-05:00 linux-fzs3 NetworkManager[577]: <info> Activation (wlan0) successful, device activated.
2013-02-08T10:23:02.044368-05:00 linux-fzs3 NetworkManager[577]: <info> Activation (wlan0) Stage 5 of 5 (IPv4 Commit) complete.
2013-02-08T10:23:02.065591-05:00 linux-fzs3 nm-dispatcher.action: Script ‘/etc/NetworkManager/dispatcher.d/nfs’ exited with error status 2.
2013-02-08T10:30:01.561782-05:00 linux-fzs3 /usr/sbin/cron[7920]: pam_unix(crond:session): session opened for user root by (uid=0)
2013-02-08T10:45:01.587343-05:00 linux-fzs3 /usr/sbin/cron[8305]: pam_unix(crond:session): session opened for user root by (uid=0)

4

This log starts with disable request. There is no information what happened before.

Did you check with ifconfig, netstat -r etc the actual state of network when ping failed?

5

On Tue, 05 Feb 2013 23:06:01 GMT
martinrehm <martinrehm@no-mx.forums.opensuse.org> wrote:

> Networkmanager does not start at first login.
>
> In KDE, the plasmoid says it is not started yet.
> Logout/Login, it is available and connects

You’re doing better than I am, KDE Network Manager won’t start for me in
RC1. To get connected, every time I have to select “network connections”
from the Kickoff menu edit the wireless device, get a message saying “no
agents were available for this request,” - where’s 007 when he’s
needed? - ignore it, type in my password, go through the OK’s, then
finally get connected.

Is Network Manager related to PHB?
If that goes over anyone’s head, see http://dilbert.com/

–
Graham P Davis, Bracknell, Berks.
openSUSE 12.3-RC1 (64-bit); KDE 4.10.00; AMD Phenom II X2 550 Processor;
Video: nVidia GeForce 210 (using nouveau driver);
Sound: ATI SBx00 Azalia (Intel HDA); Wireless: BCM4306

6

I deleted the NetworkManager log file and restarted the system so I could get a clear copy of what is going on.

The system booted as usual, ifconfig shows wlan0 connected and netstat -r shows the router is set up to my wireless router. Ping says it can’t reach the network.

I do the business of disabling/re-enabling the network via the NM plasma applet. The network is now working.

Here is the log from Network Manager:-

2013-02-08T15:53:10.454519-05:00 linux-fzs3 NetworkManager[589]: <info> NetworkManager (version 0.9.6.4) is starting…
2013-02-08T15:53:10.454915-05:00 linux-fzs3 NetworkManager[589]: <info> Read config file /etc/NetworkManager/NetworkManager.conf
2013-02-08T15:53:10.455241-05:00 linux-fzs3 NetworkManager[589]: <info> WEXT support is enabled
2013-02-08T15:53:10.469233-05:00 linux-fzs3 NetworkManager[589]: <info> VPN: loaded org.freedesktop.NetworkManager.pptp
2013-02-08T15:53:10.469623-05:00 linux-fzs3 NetworkManager[589]: <info> VPN: loaded org.freedesktop.NetworkManager.vpnc
2013-02-08T15:53:10.469904-05:00 linux-fzs3 NetworkManager[589]: <info> VPN: loaded org.freedesktop.NetworkManager.openvpn
2013-02-08T15:53:10.494836-05:00 linux-fzs3 NetworkManager[589]: <info> Loaded plugin ifcfg-suse: (C) 2008 Novell, Inc. To report bugs please use the NetworkManager mailing list.
2013-02-08T15:53:10.495197-05:00 linux-fzs3 NetworkManager[589]: <info> Loaded plugin keyfile: (c) 2007 - 2010 Red Hat, Inc. To report bugs please use the NetworkManager mailing list.
2013-02-08T15:53:10.506255-05:00 linux-fzs3 NetworkManager[589]: keyfile: parsing NETGEAR …
2013-02-08T15:53:10.517361-05:00 linux-fzs3 NetworkManager[589]: keyfile: read connection ‘NETGEAR’
2013-02-08T15:53:10.540259-05:00 linux-fzs3 NetworkManager[589]: <info> trying to start the modem manager…
2013-02-08T15:53:10.544953-05:00 linux-fzs3 NetworkManager[589]: <info> monitoring kernel firmware directory ‘/lib/firmware’.
2013-02-08T15:53:10.546141-05:00 linux-fzs3 NetworkManager[589]: <info> rfkill1: found WiFi radio killswitch (at /sys/devices/pci0000:00/0000:00:1c.3/0000:09:00.0/ieee80211/phy0/rfkill1) (driver iwlwifi)
2013-02-08T15:53:10.548224-05:00 linux-fzs3 NetworkManager[589]: <info> WiFi enabled by radio killswitch; enabled by state file
2013-02-08T15:53:10.548819-05:00 linux-fzs3 NetworkManager[589]: <info> WWAN enabled by radio killswitch; enabled by state file
2013-02-08T15:53:10.560662-05:00 linux-fzs3 NetworkManager[589]: <info> WiMAX enabled by radio killswitch; enabled by state file
2013-02-08T15:53:10.560997-05:00 linux-fzs3 NetworkManager[589]: <info> Networking is enabled by state file
2013-02-08T15:53:10.561301-05:00 linux-fzs3 NetworkManager[589]: <warn> failed to allocate link cache: (-10) Operation not supported
2013-02-08T15:53:10.561588-05:00 linux-fzs3 NetworkManager[589]: <info> (eth0): carrier is OFF
2013-02-08T15:53:10.561866-05:00 linux-fzs3 NetworkManager[589]: <info> (eth0): new Ethernet device (driver: ‘r8169’ ifindex: 2)
2013-02-08T15:53:10.562203-05:00 linux-fzs3 NetworkManager[589]: <info> (eth0): exported as /org/freedesktop/NetworkManager/Devices/0
2013-02-08T15:53:10.562532-05:00 linux-fzs3 NetworkManager[589]: <info> (eth0): now managed
2013-02-08T15:53:10.562828-05:00 linux-fzs3 NetworkManager[589]: <info> (eth0): device state change: unmanaged → unavailable (reason ‘managed’) [10 20 2]
2013-02-08T15:53:10.563103-05:00 linux-fzs3 NetworkManager[589]: <info> (eth0): bringing up device.
2013-02-08T15:53:10.764443-05:00 linux-fzs3 NetworkManager[589]: <info> (eth0): preparing device.
2013-02-08T15:53:10.764916-05:00 linux-fzs3 NetworkManager[589]: <info> (eth0): deactivating device (reason ‘managed’) [2]
2013-02-08T15:53:10.766490-05:00 linux-fzs3 NetworkManager[589]: <info> Added default wired connection ‘Wired connection 1’ for /sys/devices/pci0000:00/0000:00:1c.1/0000:05:00.0/net/eth0
2013-02-08T15:53:10.766880-05:00 linux-fzs3 NetworkManager[589]: <info> (wlan0): using nl80211 for WiFi device control
2013-02-08T15:53:10.767324-05:00 linux-fzs3 NetworkManager[589]: <warn> (wlan0): driver supports Access Point (AP) mode
2013-02-08T15:53:10.767718-05:00 linux-fzs3 NetworkManager[589]: <info> (wlan0): new 802.11 WiFi device (driver: ‘iwlwifi’ ifindex: 3)
2013-02-08T15:53:10.768095-05:00 linux-fzs3 NetworkManager[589]: <info> (wlan0): exported as /org/freedesktop/NetworkManager/Devices/1
2013-02-08T15:53:10.768476-05:00 linux-fzs3 NetworkManager[589]: <info> (wlan0): now managed
2013-02-08T15:53:10.768867-05:00 linux-fzs3 NetworkManager[589]: <info> (wlan0): device state change: unmanaged → unavailable (reason ‘managed’) [10 20 2]
2013-02-08T15:53:10.769315-05:00 linux-fzs3 NetworkManager[589]: <info> (wlan0): bringing up device.
2013-02-08T15:53:11.156408-05:00 linux-fzs3 NetworkManager[589]: <info> (wlan0): preparing device.
2013-02-08T15:53:11.157275-05:00 linux-fzs3 NetworkManager[589]: <info> (wlan0): deactivating device (reason ‘managed’) [2]
2013-02-08T15:53:11.158554-05:00 linux-fzs3 NetworkManager[589]: <warn> /sys/devices/virtual/net/lo: couldn’t determine device driver; ignoring…
2013-02-08T15:53:11.158560-05:00 linux-fzs3 NetworkManager[589]: <warn> /sys/devices/virtual/net/lo: couldn’t determine device driver; ignoring…
2013-02-08T15:53:11.159748-05:00 linux-fzs3 NetworkManager[589]: <info> modem-manager is now available
2013-02-08T15:53:11.979536-05:00 linux-fzs3 NetworkManager[589]: <info> wpa_supplicant started
2013-02-08T15:53:12.847311-05:00 linux-fzs3 NetworkManager[589]: <info> (wlan0) supports 5 scan SSIDs
2013-02-08T15:53:12.847710-05:00 linux-fzs3 NetworkManager[589]: <info> (wlan0): supplicant interface state: starting → ready
2013-02-08T15:53:12.849055-05:00 linux-fzs3 NetworkManager[589]: <info> (wlan0): device state change: unavailable → disconnected (reason ‘supplicant-available’) [20 30 42]
2013-02-08T15:53:12.849067-05:00 linux-fzs3 NetworkManager[589]: <warn> Trying to remove a non-existant call id.
2013-02-08T15:53:12.849074-05:00 linux-fzs3 NetworkManager[589]: <info> (wlan0): supplicant interface state: ready → inactive
2013-02-08T15:53:12.849079-05:00 linux-fzs3 NetworkManager[589]: <info> (wlan0) supports 5 scan SSIDs
2013-02-08T15:53:13.242268-05:00 linux-fzs3 NetworkManager[589]: <info> Auto-activating connection ‘NETGEAR’.
2013-02-08T15:53:13.242293-05:00 linux-fzs3 NetworkManager[589]: <info> Activation (wlan0) starting connection ‘NETGEAR’
2013-02-08T15:53:13.242300-05:00 linux-fzs3 NetworkManager[589]: <info> (wlan0): device state change: disconnected → prepare (reason ‘none’) [30 40 0]
2013-02-08T15:53:13.242307-05:00 linux-fzs3 NetworkManager[589]: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) scheduled…
2013-02-08T15:53:13.245271-05:00 linux-fzs3 NetworkManager[589]: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) started…
2013-02-08T15:53:13.245288-05:00 linux-fzs3 NetworkManager[589]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) scheduled…
2013-02-08T15:53:13.245295-05:00 linux-fzs3 NetworkManager[589]: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) complete.
2013-02-08T15:53:13.245299-05:00 linux-fzs3 NetworkManager[589]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) starting…
2013-02-08T15:53:13.245305-05:00 linux-fzs3 NetworkManager[589]: <info> (wlan0): device state change: prepare → config (reason ‘none’) [40 50 0]
2013-02-08T15:53:13.245309-05:00 linux-fzs3 NetworkManager[589]: <info> Activation (wlan0/wireless): connection ‘NETGEAR’ requires no security. No secrets needed.
2013-02-08T15:53:13.245313-05:00 linux-fzs3 NetworkManager[589]: <info> Config: added ‘ssid’ value ‘NETGEAR’
2013-02-08T15:53:13.245590-05:00 linux-fzs3 NetworkManager[589]: <info> Config: added ‘scan_ssid’ value ‘1’
2013-02-08T15:53:13.245840-05:00 linux-fzs3 NetworkManager[589]: <info> Config: added ‘key_mgmt’ value ‘NONE’
2013-02-08T15:53:13.246077-05:00 linux-fzs3 NetworkManager[589]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) complete.
2013-02-08T15:53:13.246324-05:00 linux-fzs3 NetworkManager[589]: <info> Config: set interface ap_scan to 1
2013-02-08T15:53:13.257087-05:00 linux-fzs3 NetworkManager[589]: <info> (wlan0): supplicant interface state: inactive → scanning
2013-02-08T15:53:16.287283-05:00 linux-fzs3 NetworkManager[589]: <info> (wlan0): supplicant interface state: scanning → authenticating
2013-02-08T15:53:16.293177-05:00 linux-fzs3 NetworkManager[589]: <info> (wlan0): supplicant interface state: authenticating → associating
2013-02-08T15:53:16.335420-05:00 linux-fzs3 NetworkManager[589]: <info> (wlan0): supplicant interface state: associating → completed
2013-02-08T15:53:16.335800-05:00 linux-fzs3 NetworkManager[589]: <info> Activation (wlan0/wireless) Stage 2 of 5 (Device Configure) successful. Connected to wireless network ‘NETGEAR’.
2013-02-08T15:53:16.336084-05:00 linux-fzs3 NetworkManager[589]: <info> Activation (wlan0) Stage 3 of 5 (IP Configure Start) scheduled.
2013-02-08T15:53:16.336460-05:00 linux-fzs3 NetworkManager[589]: <info> Activation (wlan0) Stage 3 of 5 (IP Configure Start) started…
2013-02-08T15:53:16.336756-05:00 linux-fzs3 NetworkManager[589]: <info> (wlan0): device state change: config → ip-config (reason ‘none’) [50 70 0]
2013-02-08T15:53:16.337034-05:00 linux-fzs3 NetworkManager[589]: <info> Activation (wlan0) Beginning DHCPv4 transaction (timeout in 45 seconds)
2013-02-08T15:53:16.337527-05:00 linux-fzs3 NetworkManager[589]: <info> dhclient started with pid 1362
2013-02-08T15:53:16.337869-05:00 linux-fzs3 NetworkManager[589]: <info> Activation (wlan0) Stage 3 of 5 (IP Configure Start) complete.
2013-02-08T15:53:16.502236-05:00 linux-fzs3 NetworkManager[589]: <info> (wlan0): DHCPv4 state changed nbi → preinit
2013-02-08T15:53:18.038273-05:00 linux-fzs3 NetworkManager[589]: <info> (wlan0): DHCPv4 state changed preinit → reboot
2013-02-08T15:53:18.038663-05:00 linux-fzs3 NetworkManager[589]: <info> address 192.168.1.4
2013-02-08T15:53:18.039263-05:00 linux-fzs3 NetworkManager[589]: <info> prefix 24 (255.255.255.0)
2013-02-08T15:53:18.039279-05:00 linux-fzs3 NetworkManager[589]: <info> gateway 192.168.1.1
2013-02-08T15:53:18.041269-05:00 linux-fzs3 NetworkManager[589]: <info> nameserver ‘192.168.1.1’
2013-02-08T15:53:18.041291-05:00 linux-fzs3 NetworkManager[589]: <info> Activation (wlan0) Stage 5 of 5 (IPv4 Configure Commit) scheduled…
2013-02-08T15:53:18.041300-05:00 linux-fzs3 NetworkManager[589]: <info> Activation (wlan0) Stage 5 of 5 (IPv4 Commit) started…
2013-02-08T15:53:19.041331-05:00 linux-fzs3 NetworkManager[589]: <info> (wlan0): device state change: ip-config → activated (reason ‘none’) [70 100 0]
2013-02-08T15:53:19.145634-05:00 linux-fzs3 NetworkManager[589]: <info> Clearing nscd hosts cache.
2013-02-08T15:53:19.147360-05:00 linux-fzs3 NetworkManager[589]: sent invalidate(hosts) request, exiting
2013-02-08T15:53:19.148268-05:00 linux-fzs3 NetworkManager[589]: <info> Policy set ‘NETGEAR’ (wlan0) as default for IPv4 routing and DNS.
2013-02-08T15:53:19.150084-05:00 linux-fzs3 NetworkManager[589]: <info> Activation (wlan0) successful, device activated.
2013-02-08T15:53:19.150105-05:00 linux-fzs3 NetworkManager[589]: <info> Activation (wlan0) Stage 5 of 5 (IPv4 Commit) complete.
2013-02-08T15:53:19.193070-05:00 linux-fzs3 nm-dispatcher.action: Script ‘/etc/NetworkManager/dispatcher.d/nfs’ exited with error status 2.
2013-02-08T15:53:33.118313-05:00 linux-fzs3 NetworkManager[589]: <info> (wlan0): supplicant interface state: completed → disconnected
2013-02-08T15:53:33.221781-05:00 linux-fzs3 NetworkManager[589]: <info> (wlan0): supplicant interface state: disconnected → scanning
2013-02-08T15:53:33.700388-05:00 linux-fzs3 NetworkManager[589]: <info> (wlan0): supplicant interface state: scanning → authenticating
2013-02-08T15:53:33.707839-05:00 linux-fzs3 NetworkManager[589]: <info> (wlan0): supplicant interface state: authenticating → associating
2013-02-08T15:53:33.714089-05:00 linux-fzs3 NetworkManager[589]: <info> (wlan0): supplicant interface state: associating → completed
2013-02-08T15:53:54.136093-05:00 linux-fzs3 /usr/sbin/cron[5446]: (CRON) INFO (running with inotify support)

Because of space limitations in the message, the log follows in a continuation

There has to be something going on that the first connection misses.

Anyone got a clue as to what it is missing. Can I provide any more information to help solve this one?

7

log file continuation:-

2013-02-08T16:00:01.195096-05:00 linux-fzs3 /usr/sbin/cron[5742]: pam_unix(crond:session): session opened for user root by (uid=0)
2013-02-08T16:01:13.165269-05:00 linux-fzs3 NetworkManager[589]: <info> disable requested (sleeping: no enabled: yes)
2013-02-08T16:01:13.166957-05:00 linux-fzs3 NetworkManager[589]: <info> sleeping or disabling…
2013-02-08T16:01:13.166968-05:00 linux-fzs3 NetworkManager[589]: <info> (eth0): now unmanaged
2013-02-08T16:01:13.166972-05:00 linux-fzs3 NetworkManager[589]: <info> (eth0): device state change: unavailable → unmanaged (reason ‘sleeping’) [20 10 37]
2013-02-08T16:01:13.166976-05:00 linux-fzs3 NetworkManager[589]: <info> (eth0): cleaning up…
2013-02-08T16:01:13.166979-05:00 linux-fzs3 NetworkManager[589]: <info> (eth0): taking down device.
2013-02-08T16:01:13.171279-05:00 linux-fzs3 NetworkManager[589]: <info> (wlan0): now unmanaged
2013-02-08T16:01:13.171298-05:00 linux-fzs3 NetworkManager[589]: <info> (wlan0): device state change: activated → unmanaged (reason ‘sleeping’) [100 10 37]
2013-02-08T16:01:13.243612-05:00 linux-fzs3 NetworkManager[589]: <info> (wlan0): deactivating device (reason ‘sleeping’) [37]
2013-02-08T16:01:13.444906-05:00 linux-fzs3 NetworkManager[589]: <info> (wlan0): canceled DHCP transaction, DHCP client pid 1362
2013-02-08T16:01:13.455792-05:00 linux-fzs3 NetworkManager[589]: <info> Clearing nscd hosts cache.
2013-02-08T16:01:13.458455-05:00 linux-fzs3 NetworkManager[589]: sent invalidate(hosts) request, exiting
2013-02-08T16:01:13.458474-05:00 linux-fzs3 NetworkManager[589]: <info> (wlan0): cleaning up…
2013-02-08T16:01:13.458976-05:00 linux-fzs3 NetworkManager[589]: <info> (wlan0): taking down device.
2013-02-08T16:01:19.800705-05:00 linux-fzs3 NetworkManager[589]: <info> enable requested (sleeping: no enabled: no)
2013-02-08T16:01:19.801124-05:00 linux-fzs3 NetworkManager[589]: <info> waking up and re-enabling…
2013-02-08T16:01:19.801735-05:00 linux-fzs3 NetworkManager[589]: <info> WWAN now enabled by management service
2013-02-08T16:01:19.802475-05:00 linux-fzs3 NetworkManager[589]: <info> (eth0): now managed
2013-02-08T16:01:19.802721-05:00 linux-fzs3 NetworkManager[589]: <info> (eth0): device state change: unmanaged → unavailable (reason ‘managed’) [10 20 2]
2013-02-08T16:01:19.802971-05:00 linux-fzs3 NetworkManager[589]: <info> (eth0): bringing up device.
2013-02-08T16:01:19.985291-05:00 linux-fzs3 NetworkManager[589]: <info> (eth0): preparing device.
2013-02-08T16:01:19.986357-05:00 linux-fzs3 NetworkManager[589]: <info> (eth0): deactivating device (reason ‘managed’) [2]
2013-02-08T16:01:19.993418-05:00 linux-fzs3 NetworkManager[589]: <info> (wlan0): now managed
2013-02-08T16:01:19.993451-05:00 linux-fzs3 NetworkManager[589]: <info> (wlan0): device state change: unmanaged → unavailable (reason ‘managed’) [10 20 2]
2013-02-08T16:01:19.993470-05:00 linux-fzs3 NetworkManager[589]: <info> (wlan0): bringing up device.
2013-02-08T16:01:20.222366-05:00 linux-fzs3 NetworkManager[589]: <info> (wlan0): preparing device.
2013-02-08T16:01:20.222935-05:00 linux-fzs3 NetworkManager[589]: <info> (wlan0): deactivating device (reason ‘managed’) [2]
2013-02-08T16:01:20.236749-05:00 linux-fzs3 NetworkManager[589]: <info> (wlan0) supports 5 scan SSIDs
2013-02-08T16:01:20.237428-05:00 linux-fzs3 NetworkManager[589]: <info> (wlan0): supplicant interface state: starting → ready
2013-02-08T16:01:20.237900-05:00 linux-fzs3 NetworkManager[589]: <info> (wlan0): device state change: unavailable → disconnected (reason ‘supplicant-available’) [20 30 42]
2013-02-08T16:01:20.238324-05:00 linux-fzs3 NetworkManager[589]: <warn> Trying to remove a non-existant call id.
2013-02-08T16:01:20.238608-05:00 linux-fzs3 NetworkManager[589]: <info> (wlan0): supplicant interface state: ready → inactive
2013-02-08T16:01:20.238875-05:00 linux-fzs3 NetworkManager[589]: <info> (wlan0) supports 5 scan SSIDs
2013-02-08T16:01:20.660379-05:00 linux-fzs3 NetworkManager[589]: <info> Auto-activating connection ‘NETGEAR’.
2013-02-08T16:01:20.662311-05:00 linux-fzs3 NetworkManager[589]: <info> Activation (wlan0) starting connection ‘NETGEAR’
2013-02-08T16:01:20.663284-05:00 linux-fzs3 NetworkManager[589]: <info> (wlan0): device state change: disconnected → prepare (reason ‘none’) [30 40 0]
2013-02-08T16:01:20.663305-05:00 linux-fzs3 NetworkManager[589]: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) scheduled…
2013-02-08T16:01:20.663395-05:00 linux-fzs3 NetworkManager[589]: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) started…
2013-02-08T16:01:20.665925-05:00 linux-fzs3 NetworkManager[589]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) scheduled…
2013-02-08T16:01:20.665949-05:00 linux-fzs3 NetworkManager[589]: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) complete.
2013-02-08T16:01:20.665957-05:00 linux-fzs3 NetworkManager[589]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) starting…
2013-02-08T16:01:20.665962-05:00 linux-fzs3 NetworkManager[589]: <info> (wlan0): device state change: prepare → config (reason ‘none’) [40 50 0]
2013-02-08T16:01:20.665967-05:00 linux-fzs3 NetworkManager[589]: <info> Activation (wlan0/wireless): connection ‘NETGEAR’ requires no security. No secrets needed.
2013-02-08T16:01:20.665973-05:00 linux-fzs3 NetworkManager[589]: <info> Config: added ‘ssid’ value ‘NETGEAR’
2013-02-08T16:01:20.665977-05:00 linux-fzs3 NetworkManager[589]: <info> Config: added ‘scan_ssid’ value ‘1’
2013-02-08T16:01:20.665982-05:00 linux-fzs3 NetworkManager[589]: <info> Config: added ‘key_mgmt’ value ‘NONE’
2013-02-08T16:01:20.666198-05:00 linux-fzs3 NetworkManager[589]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) complete.
2013-02-08T16:01:20.666496-05:00 linux-fzs3 NetworkManager[589]: <info> Config: set interface ap_scan to 1
2013-02-08T16:01:20.678522-05:00 linux-fzs3 NetworkManager[589]: <info> (wlan0): supplicant interface state: inactive → scanning
2013-02-08T16:01:21.137120-05:00 linux-fzs3 NetworkManager[589]: <info> (wlan0): supplicant interface state: scanning → authenticating
2013-02-08T16:01:21.145269-05:00 linux-fzs3 NetworkManager[589]: <info> (wlan0): supplicant interface state: authenticating → associating
2013-02-08T16:01:21.152177-05:00 linux-fzs3 NetworkManager[589]: <info> (wlan0): supplicant interface state: associating → completed
2013-02-08T16:01:21.153623-05:00 linux-fzs3 NetworkManager[589]: <info> Activation (wlan0/wireless) Stage 2 of 5 (Device Configure) successful. Connected to wireless network ‘NETGEAR’.
2013-02-08T16:01:21.155022-05:00 linux-fzs3 NetworkManager[589]: <info> Activation (wlan0) Stage 3 of 5 (IP Configure Start) scheduled.
2013-02-08T16:01:21.156555-05:00 linux-fzs3 NetworkManager[589]: <info> Activation (wlan0) Stage 3 of 5 (IP Configure Start) started…
2013-02-08T16:01:21.157919-05:00 linux-fzs3 NetworkManager[589]: <info> (wlan0): device state change: config → ip-config (reason ‘none’) [50 70 0]
2013-02-08T16:01:21.159233-05:00 linux-fzs3 NetworkManager[589]: <info> Activation (wlan0) Beginning DHCPv4 transaction (timeout in 45 seconds)
2013-02-08T16:01:21.160627-05:00 linux-fzs3 NetworkManager[589]: <info> dhclient started with pid 6001
2013-02-08T16:01:21.161949-05:00 linux-fzs3 NetworkManager[589]: <info> Activation (wlan0) Stage 3 of 5 (IP Configure Start) complete.
2013-02-08T16:01:21.176896-05:00 linux-fzs3 NetworkManager[589]: <info> (wlan0): DHCPv4 state changed nbi → preinit
2013-02-08T16:01:22.708765-05:00 linux-fzs3 NetworkManager[589]: <info> (wlan0): DHCPv4 state changed preinit → reboot
2013-02-08T16:01:22.708772-05:00 linux-fzs3 NetworkManager[589]: <info> address 192.168.1.4
2013-02-08T16:01:22.708778-05:00 linux-fzs3 NetworkManager[589]: <info> prefix 24 (255.255.255.0)
2013-02-08T16:01:22.708785-05:00 linux-fzs3 NetworkManager[589]: <info> gateway 192.168.1.1
2013-02-08T16:01:22.708806-05:00 linux-fzs3 NetworkManager[589]: <info> nameserver ‘192.168.1.1’
2013-02-08T16:01:22.709146-05:00 linux-fzs3 NetworkManager[589]: <info> Activation (wlan0) Stage 5 of 5 (IPv4 Configure Commit) scheduled…
2013-02-08T16:01:22.709974-05:00 linux-fzs3 NetworkManager[589]: <info> Activation (wlan0) Stage 5 of 5 (IPv4 Commit) started…
2013-02-08T16:01:23.709622-05:00 linux-fzs3 NetworkManager[589]: <info> (wlan0): device state change: ip-config → activated (reason ‘none’) [70 100 0]
2013-02-08T16:01:23.816985-05:00 linux-fzs3 NetworkManager[589]: <info> Clearing nscd hosts cache.
2013-02-08T16:01:23.820271-05:00 linux-fzs3 NetworkManager[589]: sent invalidate(hosts) request, exiting
2013-02-08T16:01:23.820296-05:00 linux-fzs3 NetworkManager[589]: <info> Policy set ‘NETGEAR’ (wlan0) as default for IPv4 routing and DNS.
2013-02-08T16:01:23.820302-05:00 linux-fzs3 NetworkManager[589]: <info> Activation (wlan0) successful, device activated.
2013-02-08T16:01:23.822864-05:00 linux-fzs3 NetworkManager[589]: <info> Activation (wlan0) Stage 5 of 5 (IPv4 Commit) complete.
2013-02-08T16:01:23.852507-05:00 linux-fzs3 nm-dispatcher.action: Script ‘/etc/NetworkManager/dispatcher.d/nfs’ exited with error status 2.

8

It looks like the problem is that the routing table has not been set up properly. There is no default gateway. The wireless network is up and connected. I can ping the router, but nothing else gets sent out.

I have tried to do route commands to set up the gateway, but none that I have produced are accepted by route. Route either complains about my command or says, ‘no device’.

9

Yes, that seems to be the problem. I finally figured out how to get the route command to work. This was by putting the address and name of my router into the /etc/hosts file. Then I issued the command :-

route add default gw wlrouter

and then I can connect into the Internet.

So it definitely seems that the problem is that the default route is not being set up by the initial call on network management. The connectivity is, but not the routing.

Should I raise this as a bug?

10

Seems like you should.

11

I came across this problem last year with 12.1 and also 12.2 (possibly after a big update). I never did track down the exact problem, so didn’t put in a bug report, but it seemed to be something to do with an incomplete routing table.

The problem only occurred with WiFi and the workaround was to use ifup instead of Network Manager. Wired connection was ok with NW. Looks as if the problem is still there in 12.3.