Yes, the loopback iface error was a typo... As for your second question, no I haven't been able to get the interface to associate using iwconfig. The driver has "ordering" problems ( ie. the wireless ioctls need to be called in a particular order ). I'm going to report this as a bug to Intel ( reported against the moblin- kernel...home to the Marvell WLAN drivers ), although I don't have many hopes for any kind of quick resolution from them.
I can get the interface to associate using wpa_supplicant and a hard- coded config file. Lool and I just discussed on IRC and one possibility for this device is to translates the IF_WIRELESS_* variables in the script /etc/network/if-pre-up.d/wireless-tools to IF_WPA_* variables. This would cause the wpa_supplicant script to do the right thing ( I *think* ). That said, one question Lool and I both had was why there are wpa_supplicant scripts in both /if-pre-up.d and /if-up.d? Finally, although there may be an underlying driver problem in my particular case, I also mentioned that nobody else in our office here could make their laptops associate with the AP in question via "Manual Configuration", so it feels like there *may* be a more fundamental bug lurking... -- [hardy] ifup fails to trigger association with WEP access points https://bugs.launchpad.net/bugs/240520 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
