Not logged in
Log in now
Create an account
Subscribe to LWN
LWN.net Weekly Edition for May 23, 2013
An "enum" for Python 3
An unexpected perf feature
LWN.net Weekly Edition for May 16, 2013
A look at the PyPy 2.0 release
For years I managed my wireless on linux using command line tools and wpasupplicant... I am sure as hell happy I don't have to do that anymore!
Helper software for twm/fvwm/etc
Posted Nov 10, 2011 21:15 UTC (Thu) by dskoll (subscriber, #1630)
You must enjoy suffering.
No, if I enjoyed suffering, I'd use GNOME 3.
Posted Nov 11, 2011 0:10 UTC (Fri) by mathstuf (subscriber, #69389)
Unfortunately the machines I have don't have wireless chips that are supported by upstream, so I'm without wireless most times.
TWC cuts out and this is the quickest way to get the modem to allow traffic through again. It's not the switch since the same happens when the machines are connected directly to the modem in which case a modem power cycle is the only way and the local network is unaffected.
Posted Nov 11, 2011 14:35 UTC (Fri) by drag (subscriber, #31333)
Unless you were talking about using a very old version of Network-Manager. If so you should probably re-evaluate as it's massively better then it was when it was new. Matured massively in capabilities and stability.
Why do I say this?
Because Network-Manager depends on wpa_supplicant.
On my Fedora 14 box:
rpm -qR $(rpm -qf $(which NetworkManager)) |grep wpa
wpa_supplicant >= 1:0.6.8-4
Posted Nov 11, 2011 16:22 UTC (Fri) by mathstuf (subscriber, #69389)
I agree that it has gotten better, but this behavior is a showstopper for me. I brought it up on f-d-l and I did not get the impression that marking networks as "flaky" (so that NM would take N seconds before dropping DNS, IP, and related information on the interface instead of 0) was not an important feature.
Copyright © 2013, Eklektix, Inc.
Comments and public postings are copyrighted by their creators.
Linux is a registered trademark of Linus Torvalds