Sure - Here's one on the subject - May not be the official way to do it, but it worked for me: http://ubuntuforums.org/showthread.php?t=202834
And here's an old bug report on the subject: https://bugs.launchpad.net/linux/+bug/33089
There are multiple forum entries on the subject as well, but they mostly end with lazy half-fixes like the one I put in place (ifdown wlan0;ifup wlan0 in the /etc/rc.local file). One way or another though, it still doesn't make a lick of sense that the ifup script can succesfully work with iwconfig when the system's fully loaded, but can't halfway through. It should have no significant dependencies.
By the way, I've had the same problem on two completely different sets of hardware, too. Full lspci output's in the bug report. Me thinks NetworkManager is just too immature to properly handle WPA2. it's a shame - incredibly simple and clean interfaces are out there and just waiting to be ripped off from myriad embedded Linux projects.
Sean Crago Kathmandu
On Sun, Aug 31, 2008 at 2:04 AM, Justin Dugger [email protected] wrote:
On Sat, Aug 30, 2008 at 12:38 PM, Sean Crago [email protected] wrote:
Unfortunately it works so poorly in my specific configuration, works so poorly with secured access points, that the primary tutorials for Ubuntu push users in the direction that I took. It's a damned shame that it doesn't work as seemlessly and easily as it does in the OSS embedded GTK Maemo, but NetworkManager really didn't work for me.
-Sean
If you've tested with the latest Intrepid LiveCD, maybe report a bug in Launchpad. As you probably know, some hardware has less vendor support for Linux, but we do what we can ;)
Can you cite the "primary tutorials" you read that moved away from NM? I'd like to read it as well, since I've been spoiled by NM working on my hardwares.
Justin Dugger Ubuntu Member