NM not resetting
- From: Neal Becker <ndbecker2 gmail com>
- To: networkmanager-list gnome org
- Subject: NM not resetting
- Date: Thu, 19 Jul 2007 09:20:07 -0400
I have problems sporadically with NM and madwifi. Sometimes a link is not
established (don't know why). Following this, attempts to connect will
always fail. This seems to be because
Jul 18 16:36:15 nbecker4 NetworkManager: <info> Old device 'ath0'
activating, won't change.
The only way to fix this seems to be (using knetworkmanager), disable
wireless, then re-enable it.
Here is the successful sequence after re-enable:
Jul 18 16:39:58 nbecker4 NetworkManager: <info> User request to enable
wireless.
Jul 18 16:40:06 nbecker4 NetworkManager: <info> User
Switch: /org/freedesktop/NetworkManager/Devices/ath0 / linksys
Jul 18 16:40:06 nbecker4 NetworkManager: <info> Deactivating device ath0.
Jul 18 16:40:06 nbecker4 dhcdbd: message_handler: message handler not found
under /com/redhat/dhcp/ath0 for sub-path ath0.dbus.get.reason
Jul 18 16:40:06 nbecker4 NetworkManager: <info> Device ath0 activation
scheduled...
Jul 18 16:40:06 nbecker4 NetworkManager: <info> Activation (ath0)
started...
Jul 18 16:40:06 nbecker4 NetworkManager: <info> Activation (ath0) Stage 1
of 5 (Device Prepare) scheduled...
Jul 18 16:40:06 nbecker4 NetworkManager: <info> Activation (ath0) Stage 1
of 5 (Device Prepare) started...
Jul 18 16:40:06 nbecker4 NetworkManager: <info> Activation (ath0) Stage 2
of 5 (Device Configure) scheduled...
Jul 18 16:40:06 nbecker4 NetworkManager: <info> Activation (ath0) Stage 1
of 5 (Device Prepare) complete.
Jul 18 16:40:06 nbecker4 NetworkManager: <info> Activation (ath0) Stage 2
of 5 (Device Configure) starting...
Jul 18 16:40:06 nbecker4 NetworkManager: <info> Activation (ath0/wireless):
access point 'linksys' is encrypted, and a key exists. No new key needed.
Jul 18 16:40:06 nbecker4 NetworkManager: <info> nm-netlink-monitor.c -
nm_netlink_monitor_event_handler (724) netlink reports device ath0 link now
1
Jul 18 16:40:06 nbecker4 NetworkManager: <info> nm-netlink-monitor.c -
nm_netlink_monitor_event_handler (724) netlink reports device ath0 link now
1
Jul 18 16:40:07 nbecker4 NetworkManager: <info> SUP: sending
command 'INTERFACE_ADD ath0 wext /var/run/wpa_supplicant '
Jul 18 16:40:07 nbecker4 NetworkManager: <info> nm-netlink-monitor.c -
nm_netlink_monitor_event_handler (724) netlink reports device ath0 link now
0
Jul 18 16:40:07 nbecker4 NetworkManager: <info> SUP: response was 'OK'
Jul 18 16:40:07 nbecker4 NetworkManager: <info> SUP: sending
command 'AP_SCAN 1'
Jul 18 16:40:07 nbecker4 NetworkManager: <info> SUP: response was 'OK'
Jul 18 16:40:07 nbecker4 NetworkManager: <info> SUP: sending
command 'ADD_NETWORK'
Jul 18 16:40:07 nbecker4 NetworkManager: <info> SUP: response was '0'
Jul 18 16:40:07 nbecker4 NetworkManager: <info> SUP: sending
command 'SET_NETWORK 0 ssid 6c696e6b737973'
Jul 18 16:40:07 nbecker4 NetworkManager: <info> SUP: response was 'OK'
Jul 18 16:40:07 nbecker4 NetworkManager: <info> SUP: sending
command 'SET_NETWORK 0 key_mgmt NONE'
Jul 18 16:40:07 nbecker4 NetworkManager: <info> SUP: response was 'OK'
Jul 18 16:40:07 nbecker4 NetworkManager: <info> SUP: sending
command 'SET_NETWORK 0 auth_alg SHARED'
Jul 18 16:40:07 nbecker4 NetworkManager: <info> SUP: response was 'OK'
Jul 18 16:40:07 nbecker4 NetworkManager: <info> SUP: sending
command 'SET_NETWORK 0 wep_key0 <key>'
Jul 18 16:40:07 nbecker4 NetworkManager: <info> SUP: response was 'OK'
Jul 18 16:40:07 nbecker4 NetworkManager: <info> SUP: sending
command 'SET_NETWORK 0 wep_tx_keyidx 0'
Jul 18 16:40:07 nbecker4 NetworkManager: <info> SUP: response was 'OK'
Jul 18 16:40:07 nbecker4 NetworkManager: <info> SUP: sending
command 'ENABLE_NETWORK 0'
Jul 18 16:40:07 nbecker4 NetworkManager: <info> SUP: response was 'OK'
Jul 18 16:40:07 nbecker4 NetworkManager: <info> Activation (ath0) Stage 2
of 5 (Device Configure) complete.
Jul 18 16:40:08 nbecker4 avahi-daemon[2362]: Joining mDNS multicast group on
interface ath0.IPv6 with address fe80::215:6dff:fe53:1cbd.
Jul 18 16:40:08 nbecker4 avahi-daemon[2362]: New relevant interface
ath0.IPv6 for mDNS.
Jul 18 16:40:08 nbecker4 avahi-daemon[2362]: Registering new address record
for fe80::215:6dff:fe53:1cbd on ath0.*.
Jul 18 16:40:13 nbecker4 NetworkManager: <info> nm-netlink-monitor.c -
nm_netlink_monitor_event_handler (724) netlink reports device ath0 link now
1
Jul 18 16:40:13 nbecker4 NetworkManager: <info> nm-device.c -
nm_device_set_active_link (596) device ath0 link state set to 1
Jul 18 16:40:13 nbecker4 NetworkManager: <info> Activation (ath0/wireless)
Stage 2 of 5 (Device Configure) successful. Connected to access
point 'linksys'.
Jul 18 16:40:13 nbecker4 NetworkManager: <info> Activation (ath0) Stage 3
of 5 (IP Configure Start) scheduled.
Jul 18 16:40:13 nbecker4 NetworkManager: <info> Activation (ath0) Stage 3
of 5 (IP Configure Start) started...
Jul 18 16:40:14 nbecker4 NetworkManager: <info> Activation (ath0) Beginning
DHCP transaction.
Jul 18 16:40:14 nbecker4 NetworkManager: <info> Activation (ath0) Stage 3
of 5 (IP Configure Start) complete.
Jul 18 16:40:14 nbecker4 NetworkManager: <info> DHCP daemon state is now 12
(successfully started) for interface ath0
Jul 18 16:40:14 nbecker4 dhclient: wifi0: unknown hardware address type 801
Jul 18 16:40:14 nbecker4 NetworkManager: <info> DHCP daemon state is now 1
(starting) for interface ath0
Jul 18 16:40:14 nbecker4 dhclient: wifi0: unknown hardware address type 801
Jul 18 16:40:14 nbecker4 dhclient: DHCPDISCOVER on ath0 to 255.255.255.255
port 67 interval 8
Jul 18 16:40:15 nbecker4 dhclient: DHCPOFFER from 192.168.1.1
Jul 18 16:40:15 nbecker4 dhclient: DHCPREQUEST on ath0 to 255.255.255.255
port 67
Jul 18 16:40:15 nbecker4 dhclient: DHCPACK from 192.168.1.1
Jul 18 16:40:15 nbecker4 NetworkManager: <info> DHCP daemon state is now 2
(bound) for interface ath0
Jul 18 16:40:15 nbecker4 NetworkManager: <info> Activation (ath0) Stage 4
of 5 (IP Configure Get) scheduled...
Jul 18 16:40:15 nbecker4 NetworkManager: <info> Activation (ath0) Stage 4
of 5 (IP Configure Get) started...
Jul 18 16:40:15 nbecker4 dhcdbd: message_handler: message handler not found
under /com/redhat/dhcp/ath0 for sub-path ath0.dbus.get.host_name
Jul 18 16:40:15 nbecker4 dhcdbd: message_handler: message handler not found
under /com/redhat/dhcp/ath0 for sub-path ath0.dbus.get.domain_name
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]