Not all symptoms in the bug were resolved, because of this related issue. That said, ok - I'll give NM another shot when I bored enough to break my system a little. Still, though - Any idea what is different between the ifup at boot and the ifup in my rc.local? Why would the one work and not the other?
-Sean
On Sun, Aug 31, 2008 at 11:31 AM, Justin Dugger jldugger@ubuntu.com wrote:
On Sat, Aug 30, 2008 at 11:01 PM, Sean Crago cragos@gmail.com wrote:
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
That post was written a while ago, possibly before NM was made default. And the forums are full of crack monkeys.
And here's an old bug report on the subject: https://bugs.launchpad.net/linux/+bug/33089
That's a report about ndiswrapper and broadcom; you've got different hardware. Plus, that bug is fixed! When Ubuntu 8.10 alpha5 (new kernel!) comes out, grab it and test the wifi with NM. It'll be useful to determine whether your configuration is a problem, and developers are more likely to help and fix bugs filed against the testing version. Alpha 5 is scheduled for September 4th [1], so it won't be a long wait. When you do test and it doesn't work, file a new bug rather than piggy back on an existing one. Launchpad's dupe features are smarter than average, but hardware specific bugs can sound similiar while having different patches to fix.
I don't own a mameo platform, but I imagine it's using NM along with the rest of GNOME. NM does have an annoying keyring misfeature, thats mostly solvable with libpam-keyring, which unlocks the keyring as part of login. But I think storing WEP keys cryptographically is overkill, and probably WPA/WPA2 as well.
Justin Dugger
On Sun, Aug 31, 2008 at 02:28:05PM +0545, Sean Crago wrote:
Not all symptoms in the bug were resolved, because of this related issue. That said, ok - I'll give NM another shot when I bored enough to break my system a little. Still, though - Any idea what is different between the ifup at boot and the ifup in my rc.local? Why would the one work and not the other?
-Sean
Here is one thing that I considered when I was researching this problem some time ago. (I don't recall if I even resolved it or not now.) I wondered if something else e.g. NM was doing an ifdown at somepoint when it took over control of the network device. I wondered if this was true because when I switched to a text console before NM was running and found that the interface was up, but then it was down once I was logged in. Again I remember nothing else about what I did or did not do or even if I resolved it.
Thanks, -- Hal
-
Hal Duston -
Sean Crago