I can definitely add to this. I don't know if wpa_supplicant is having an issue with ndiswrapper, but I do know wpa_supplicant is have some issues at least. When issuing sudo /etc/init.d/networking restart, I would get the following problem (several lines from the entire output):
send_packet: Operation not permitted wpa_supplicant: cannot read contents of managed run-parts: /etc/network/if-post-down.d/wpasupplicant exited with return code 1 wpa_supplicant: cannot read contents of managed run-parts: /etc/network/if-pre-up.d/wpasupplicant exited with return code 1 There is already a pid file /var/run/dhclient.eth1.pid with pid 134993416 I would then be told the hostname is invalid. Bizarre. I don't know what this all means. Either way, I am now using the Internet following a guide on Ubuntu forums, but I still can't connect to WPA2 using my BCM4318 card. One forum user reported having a working connection to a WPA2 access point using only AES, and not TKIP-AES (He has a BCM4318 card). Using only AES won't work for me. -- wpa_supplicant doesn't work with ndiswrapper anymore https://bugs.launchpad.net/bugs/108013 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
