Re: Cannot connect to any WLAN with NM-Fedora 7-ndiswrapper
- From: "Andrew Pegram" <deltafox1229 gmail com>
- To: "Dan Williams" <dcbw redhat com>
- Cc: NetworkManager-list gnome org
- Subject: Re: Cannot connect to any WLAN with NM-Fedora 7-ndiswrapper
- Date: Sun, 14 Oct 2007 16:01:47 -0400
Sorry I took so long getting back to you. I've attached the iwevent output as well as the relevant section of the syslog.
On 10/12/07, Dan Williams
<dcbw redhat com> wrote:On Fri, 2007-10-12 at 00:07 -0400, Andrew Pegram wrote:
> Hello all
>
> I don't know if it actually went out the last time I sent this, so I'm
> sending it again (sorry for the repeat, if it is one).
>
> I'm having an issue with connecting to wireless networks through NM.
> It will connect to wired networks just fine, but it refuses to connect
> to any type of wireless network (secured WEP/WPA or unsecured). I have
> checked the syslog and found the following warning (sensitive
> information removed):
>
> Oct 6 23:42:06 <Hostname> NetworkManager: <WARN>
> nm_device_802_11_wireless_set_essid(): error setting ESSID to '' for
> device wlan0: Invalid argument
>
> I know that the program can read the ESSID from the network because
> earlier in the log, it has:
>
> Oct 6 23:41:44 <Hostname> NetworkManager: <info> User
> Switch: /org/freedesktop/NetworkManager/Devices/wlan0 / VCU
>
> ('VCU' is the ESSID)
>
> I've tried reinstalling everything to do with NetworkManager and
> ndiswrapper, and nothing seems to be working. If I haven't posted
> enough information, I can post everything in the log from the time I
> select the WLAN in the drop-down menu until it stops trying to
> connect.
During an association attempt, can you run the program "iwevent" (it
might be in /sbin or /usr/sbin) and reply with it's output?
Thanks!
Dan
> Thank you for your time,
> Andrew
> _______________________________________________
> NetworkManager-list mailing list
>
NetworkManager-list gnome org
> http://mail.gnome.org/mailman/listinfo/networkmanager-list
Waiting for Wireless Events from interfaces...
15:41:25.286166 wlan0 Set Encryption key:off
15:41:25.286639 wlan0 Set Mode:Managed
15:41:26.684941 wlan0 Set Mode:Managed
15:41:26.742400 wlan0 Set Mode:Managed
15:41:26.744203 wlan0 Set Frequency:2.412 GHz (Channel 1)
15:41:26.765227 wlan0 Set ESSID:"Arby's"
15:41:46.671592 wlan0 Set Mode:Managed
15:41:46.671777 wlan0 Set Frequency:2.412 GHz (Channel 1)
15:41:46.692185 wlan0 Set ESSID:"Arby's"
15:41:46.756163 wlan0 Set Encryption key:off
15:41:46.757378 wlan0 Set Mode:Managed
Oct 14 15:47:21 <Hostname> NetworkManager: <info> User Switch: /org/freedesktop/NetworkManager/Devices/wlan0 / Arby's
Oct 14 15:47:21 <Hostname> NetworkManager: <info> Deactivating device wlan0.
Oct 14 15:47:21 <Hostname> NetworkManager: <WARN> nm_device_802_11_wireless_set_essid(): error setting ESSID to '' for device wlan0: Invalid argument
Oct 14 15:47:21 <Hostname> NetworkManager: <info> Device wlan0 activation scheduled...
Oct 14 15:47:21 <Hostname> NetworkManager: <info> Activation (wlan0) started...
Oct 14 15:47:21 <Hostname> NetworkManager: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) scheduled...
Oct 14 15:47:21 <Hostname> NetworkManager: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) started...
Oct 14 15:47:21 <Hostname> NetworkManager: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) scheduled...
Oct 14 15:47:21 <Hostname> NetworkManager: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) complete.
Oct 14 15:47:21 <Hostname> NetworkManager: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) starting...
Oct 14 15:47:21 <Hostname> NetworkManager: <info> Activation (wlan0/wireless): access point 'Arby's' is unencrypted, no key needed.
Oct 14 15:47:23 <Hostname> NetworkManager: <info> SUP: sending command 'INTERFACE_ADD wlan0 wext /var/run/wpa_supplicant '
Oct 14 15:47:23 <Hostname> NetworkManager: <info> SUP: response was 'OK'
Oct 14 15:47:23 <Hostname> NetworkManager: <info> SUP: sending command 'AP_SCAN 1'
Oct 14 15:47:23 <Hostname> NetworkManager: <info> SUP: response was 'OK'
Oct 14 15:47:23 <Hostname> NetworkManager: <info> SUP: sending command 'ADD_NETWORK'
Oct 14 15:47:23 <Hostname> NetworkManager: <info> SUP: response was '0'
Oct 14 15:47:23 <Hostname> NetworkManager: <info> SUP: sending command 'SET_NETWORK 0 ssid 417262792773'
Oct 14 15:47:23 <Hostname> NetworkManager: <info> SUP: response was 'OK'
Oct 14 15:47:23 <Hostname> NetworkManager: <info> SUP: sending command 'SET_NETWORK 0 key_mgmt NONE'
Oct 14 15:47:23 <Hostname> NetworkManager: <info> SUP: response was 'OK'
Oct 14 15:47:23 <Hostname> NetworkManager: <info> SUP: sending command 'ENABLE_NETWORK 0'
Oct 14 15:47:23 <Hostname> NetworkManager: <info> SUP: response was 'OK'
Oct 14 15:47:23 <Hostname> NetworkManager: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) complete.
Oct 14 15:47:26 <Hostname> NetworkManager: <info> Old device 'wlan0' activating, won't change.
Oct 14 15:47:43 <Hostname> NetworkManager: <info> Activation (wlan0/wireless): association took too long (>20s), failing activation.
Oct 14 15:47:43 <Hostname> NetworkManager: <info> Activation (wlan0) failure scheduled...
Oct 14 15:47:43 <Hostname> NetworkManager: <info> Activation (wlan0) failed for access point (Arby's)
Oct 14 15:47:43 <Hostname> NetworkManager: <info> Activation (wlan0) failed.
Oct 14 15:47:43 <Hostname> NetworkManager: <info> Deactivating device wlan0.
Oct 14 15:47:43 <Hostname> NetworkManager: <WARN> nm_device_802_11_wireless_set_essid(): error setting ESSID to '' for device wlan0: Invalid argument
Oct 14 15:47:44 <Hostname> NetworkManager: <info> nm-netlink-monitor.c - nm_netlink_monitor_event_handler (724) netlink reports device wlan0 link now 0
Oct 14 15:47:46 <Hostname> NetworkManager: <info> nm-netlink-monitor.c - nm_netlink_monitor_event_handler (724) netlink reports device wlan0 link now 0
Oct 14 15:47:46 <Hostname> kernel: ADDRCONF(NETDEV_UP): wlan0: link is not ready
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]