MichaelIT, this bug report is being closed due to your last comment
https://bugs.launchpad.net/netbook-remix/+bug/365466/comments/8
regarding you no longer have the hardware. For future reference you can
manage the status of your own bugs by clicking on the current status in
the yellow line and then choosing a new status in the revealed drop down
box. You can learn more about bug statuses at
https://wiki.ubuntu.com/Bugs/Status. Thank you again for taking the time
to report this bug and helping to make Ubuntu better. Please submit any
future bugs you may find.
** No longer affects: linux (Ubuntu)
** Project changed: netbook-remix => linux (Ubuntu)
** Changed in: linux (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/365466
Title:
can't connect to WPA/WPA2 Enterprise UNR on eee901
Status in “linux” package in Ubuntu:
Invalid
Bug description:
Device: eee PC 901, linux SSD. Running UNR jaunty, installed late March and
regular updates (currently 21 April).
Fails to connect to Enterprise (LEAP) WPA and WPA2 networks (Both WPA & WPA2
are available, I tried both). SSIDs are not broadcast.
Apr 23 10:34:37 eeepc901 NetworkManager: <info> Activation (ra0) Stage 2 of
5 (Device Configure) complete.
Apr 23 10:34:37 eeepc901 NetworkManager: <info> Config: set interface
ap_scan to 2
Apr 23 10:34:37 eeepc901 NetworkManager: <info> (ra0): supplicant connection
state: disconnected -> scanning
Apr 23 10:34:37 eeepc901 NetworkManager: <info> (ra0): supplicant connection
state: scanning -> associating
Apr 23 10:35:17 eeepc901 kernel: [ 163.440160] ===>rt_ioctl_giwscan. 4(4)
BSS returned, data->length = 304
Apr 23 10:35:37 eeepc901 NetworkManager: <info> (ra0): supplicant connection
state: associating -> disconnected
Apr 23 10:35:37 eeepc901 NetworkManager: <info> (ra0): supplicant connection
state: disconnected -> scanning
Apr 23 10:35:37 eeepc901 NetworkManager: <info> (ra0): supplicant connection
state: scanning -> associating
Apr 23 10:35:38 eeepc901 NetworkManager: <info> Activation (ra0/wireless):
association took too long.
Apr 23 10:35:38 eeepc901 NetworkManager: <info> (ra0): device state change:
5 -> 6
Apr 23 10:35:38 eeepc901 NetworkManager: <info> Activation (ra0/wireless):
asking for new secrets
Apr 23 10:35:38 eeepc901 NetworkManager: <info> (ra0): supplicant connection
state: associating -> disconnected
Apr 23 10:35:42 eeepc901 NetworkManager: <WARN> get_secrets_cb(): Couldn't
get connection secrets: applet-device-wifi.c.1539
(get_secrets_dialog_response_cb): canceled.
Apr 23 10:35:42 eeepc901 NetworkManager: <info> (ra0): device state change:
6 -> 9
Apr 23 10:35:42 eeepc901 NetworkManager: <info> Activation (ra0) failed for
access point (myssid)
On the access point I see only the following activity (MAC address removed):
Apr 23 09:30:13 UTC: %DOT11-6-ASSOC: Interface Dot11Radio0, Station
xxxx.xxxx.xxxx Associated KEY_MGMT[WPAv2]
Apr 23 09:30:56 UTC: %DOT11-6-DISASSOC: Interface Dot11Radio0,
Deauthenticating Station xxxx.xxxx.xxxx Reason: Sending station has left the BSS
On the upstream ACS server I see no logs at all for this connection
attempt.
Syslog from boot to initial failure attached; note network SSID
changed to "myssid" and LEAP username changed to "myusername".
/etc/network/interfaces contains:
========
auto lo
iface lo inet loopback
========
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/365466/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
