So I've tested intrepid alpha5, and I'm still not getting LEAP
connectivity under for my iwl3945.  Using network-manager, I've gotten
the following results:

Using the direct LEAP setting, dmesg reports:
[  279.949236] wlan0: authenticate with AP 00:11:92:5a:d4:90
[  280.148097] wlan0: authenticate with AP 00:11:92:5a:d4:90
[  280.348081] wlan0: authenticate with AP 00:11:92:5a:d4:90
[  280.548067] wlan0: authentication with AP 00:11:92:5a:d4:90 timed out
<4 lines repeat>

Using the WPA-Enterprise -> LEAP setting, network-manager crashes:
[  444.452851] nm-connection-e[8416]: segfault at 6c620069 ip b7386742 sp 
bff694c0 error 4 in libglib-2.0.so.0.1707.0[b732d000+b5000]

Manually, I'm having problems.  I picked up a USB network stick (zd1211)
that works GREAT under wicd and network-manager on my hardy
installation.  I'd been trying to run wpa_supplicant manually, while the
zd1211 works under wicd and network-manager, I can't get EITHER the
zd1211 OR the iwl3945 working using the manual wpa_supplicant
configuration, on EITHER hardy OR intrepid.

If someone can give me some input on the configuration file, I'd be most 
grateful. 
My current configuration is attached, if anyone can give some advice.  Do I 
need to kill networking (or network-manager or wicd) before using manual 
configuration?

A few other notes - I don't have a group 'wheel', so someone (on
launchpad) had recommending setting ctrl_interface_group=0.

If there's anything else goofy that's inhibiting me, that I'm messing up
here, please let me know.

But in any case, LEAP is still not working out-of-the-box using network-
manager.


** Attachment added: "wpa_supplicant.conf_clean"
   http://launchpadlibrarian.net/17536557/wpa_supplicant.conf_clean

-- 
LEAP broken for iwl3945 under hhardy
https://bugs.launchpad.net/bugs/209920
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to