Home » Mailing list archives » linux-kernel » 2008 » August » 2

[2.6.27-rc1] Can't connect to encrypted network

Previous thread: [PATCH] proc: inode number fixlet by Alexey Dobriyan on Friday, August 1, 2008 - 8:30 pm. (1 message)

Next thread: CONFIRM YOUR WEBMAIL.WINTUE.NL ACCOUNT. by webmail.win.tue.nl Helpdesk on Friday, August 1, 2008 - 9:34 pm. (1 message)
[view original message]
From: Justin Madru
Subject: [2.6.27-rc1] Can't connect to encrypted network
Date: Friday, August 1, 2008 - 9:02 pm

Hi,

When I use the 2.6.27-rc1 kernel I can't connect to an encrypted 
network; the connection times out. Connecting to unencrypted works fine.
If I use my distro's kernel (2.6.24) or my build 2.6.26 kernel it is 
able to connect. I'm using Ubuntu 8.4 and an intel 3945 card.
Am I doing something wrong? or is this a regression? I get the following 
in my syslog:

NetworkManager: <debug> [1217605131.709159] 
nm_device_802_11_wireless_get_activation_ap(): Forcing AP '6DTY0'
NetworkManager: <info>  User Switch: 
/org/freedesktop/NetworkManager/Devices/wlan0 / 6DTY0
NetworkManager: <info>  Deactivating device wlan0.
dhclient: There is already a pid file /var/run/dhclient.wlan0.pid with 
pid 4333
dhclient: killed old client process, removed PID file
dhclient: wmaster0: unknown hardware address type 801
dhclient: wmaster0: unknown hardware address type 801
dhclient: DHCPRELEASE on wlan0 to 192.168.1.254 port 67
avahi-daemon[3220]: Withdrawing address record for 192.168.1.5 on wlan0.
avahi-daemon[3220]: Leaving mDNS multicast group on interface wlan0.IPv4 
with address 192.168.1.5.
avahi-daemon[3220]: Interface wlan0.IPv4 no longer relevant for mDNS.
NetworkManager: <info>  Device wlan0 activation scheduled...
NetworkManager: <info>  Activation (wlan0) started...
NetworkManager: <info>  Activation (wlan0) Stage 1 of 5 (Device Prepare) 
scheduled...
NetworkManager: <info>  Activation (wlan0) Stage 1 of 5 (Device Prepare) 
started...
NetworkManager: <info>  Activation (wlan0) Stage 2 of 5 (Device 
Configure) scheduled...
NetworkManager: <info>  Activation (wlan0) Stage 1 of 5 (Device Prepare) 
complete.
NetworkManager: <info>  Activation (wlan0) Stage 2 of 5 (Device 
Configure) starting...
NetworkManager: <info>  Activation (wlan0/wireless): access point 
'6DTY0' is encrypted, but NO valid key exists.  New key needed.
NetworkManager: <info>  Activation (wlan0) New wireless user key 
requested for network '6DTY0'.
NetworkManager: <info>  Activation (wlan0) Stage 2 of 5 (Device ...
[ message continues ]
[view original message]
From: Jasper Bryant-Greene
Subject: Re: [2.6.27-rc1] Can't connect to encrypted network
Date: Friday, August 1, 2008 - 9:14 pm

[snip]

there is almost nothing useful in that log dump :)

can you please show the relevent bits of dmesg when trying to connect to
the encrypted network

also it would probably be a good idea to try connecting using iwconfig
or wpa_supplicant (for wep or wpa) directly rather than using
networkmanager

-jasper

--


[ message continues ]
[view original message]
From: Rafael J. Wysocki
Subject: Re: [2.6.27-rc1] Can't connect to encrypted network
Date: Saturday, August 2, 2008 - 7:41 am

Please test the current -git (2.6.27-rc1-git4 as of today).

Thanks,
Rafael
--


[ message continues ]
[view original message]
From: Justin Madru
Subject: Re: [2.6.27-rc1] Can't connect to encrypted network
Date: Saturday, August 2, 2008 - 6:33 pm

Ok, tested current -git and I was able to connect to the encrypted network.
So, I'm happy :-) ! And 2.6.27 has even fixed a regression I was having 
with 2.6.{25,26}.

Justin Madru
--


[ message continues ]
Previous thread: [PATCH] proc: inode number fixlet by Alexey Dobriyan on Friday, August 1, 2008 - 8:30 pm. (1 message)

Next thread: CONFIRM YOUR WEBMAIL.WINTUE.NL ACCOUNT. by webmail.win.tue.nl Helpdesk on Friday, August 1, 2008 - 9:34 pm. (1 message)