Posted Nov 10, 2011 21:15 UTC (Thu) by dskoll (subscriber, #1630)
[Link]
You must enjoy suffering.
No, if I enjoyed suffering, I'd use GNOME 3.
Helper software for twm/fvwm/etc
Posted Nov 11, 2011 0:10 UTC (Fri) by mathstuf (subscriber, #69389)
[Link]
When I used wpa_supplicant[1], it had better behavior than NM. If I disconnected, the network didn't immediately disconnect and force me to do everything again. I could walk from my room, out to the staircase and to the room above or below me in the dorm on my wireless without reconnecting (manual or otherwise) to my router even though the stairwell was well out of range. NM drops at the hint of a disruption (e.g., power cycle the connected switch[2]) and NM would disconnect wired lines while manual ifup just waits and buffers traffic instead of confusing all NM-aware applications.
[1]Unfortunately the machines I have don't have wireless chips that are supported by upstream, so I'm without wireless most times.
[2]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.
Helper software for twm/fvwm/etc
Posted Nov 11, 2011 14:35 UTC (Fri) by drag (subscriber, #31333)
[Link]
I do not think the behavior you describe can be attributed to solely Network-Manager. I suspect it's more of a function of the wireless drivers you are using and/or the hardware.
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.
Posted Nov 11, 2011 16:22 UTC (Fri) by mathstuf (subscriber, #69389)
[Link]
Possibly, but I doubt it. That was back around NM 0.8. I moved my work laptop to NM in the past few months for 0.9, but the same "drop as soon as the cable is disconnected" behavior happens with wired which did not happen when I was using just wpa_supplicant.
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.