On Wed, 2011-09-28 at 10:58 -0400, Andy Pintar wrote: > On Tue, 27 Sep 2011, Nick Nobody wrote: > > I took your suggestion and stopped my network-manager daemon and > > manually set up my wireless connection with wpa_supplicant and dhclient. > > Amazingly the connection was rock-solid all day! > > > > Now I have to figure out what network manager is doing that messes up > > the connection :S > > Hi Nick; > > Glad you had success. I'm not sure what it is exactly NetworkManager (NM) > does that messes up the connection. There is a network monitor menubar > widget that I use to keep an eye on connectivity, and normally if I > suspend my laptop and open it up elsewhere I have to ifdown/ifup it, > possibly having to run dhclient again. The *idea* was for NM to avoid > this hassle. I think instead of making a nice wrapper for WPASupp they > went their own route entirely, different drivers, etc. > > I have in the past looked for other gui replacements, just querying google > now pulls up wicd. That might work for you. I know that years ago, > around Ubuntu 5, they switched from whatever they used to NM, and having > only ever really used Thinkpads with intel wireless I've always had issues > with NM. I'm one of the few who doesn't mind 'iwlist scan | grep <blah>', > then adding a new entry to wpa_supplicant.conf for that AP. I find the > flexibility is unparalleled by any gui app (eg, windows, WHAT ARE YOU > DOING!!!! DON'T CONNECT TO THAT ONE! UGH!!!!). > > I hope you find a solution that works well for you, but remember you can > always fall back on wpa_supplicant. If you're having keyboard-smashing > moments trying to connect to a new AP (especially coming out of suspend), > the following might help: > ifdown/up, make sure wpa_supplicant is set up to work with those scripts, > killall dhclient, then dhclient <wificard>, > make sure there aren't any other wpa_supplicant processes running that you > forgot about... > > I guess that's about it. > It might be worth sending an email to the Ubuntu people reminding them > what tripe NM really is (although I got zero response when I gave feedback > back in the Ubuntu5 era). Not sure why they're so tied to it when it's > such crap, but that's life.
Grrr, I spoke too soon. I'm able to replicate the problem using just wpa_supplicant. After the connection drops (due to bad reception) wpa_supplicant gets stuck trying to re-authenticate. I have to kill wpa_supplicant and start it again to get my connection back. That being said, yesterday my connection was more stable than it's ever been when just using wpa_supplicant but I was in an area with really good reception. So network-manager is responsible for doing something to make the connection drop in the first place and wpa_supplicant is what causes the large delay before I get my connection back again. This isn't going to be fun to debug :( nick _______________________________________________ mlug mailing list [email protected] https://listes.koumbit.net/cgi-bin/mailman/listinfo/mlug-listserv.mlug.ca
