NetworkManager Sucks Very Bad :(

T-u-N-i-X · 2008-02-20 22:05:26

Hey There,

Like I've written here before, I really like the idea of leaving most of the things to GNOME such as networking.. I'm using iwlwifi driver with gnome-networkmanager.. It starts fine but when it's about to connect to the network, suddenly the whole networkmanager daemon dies..! It's really annoying so I started using good old network profiles.. Anyone having such problems like this ?

Allan · 2008-02-20 22:10:29

I have no problems at all using gnome-networkmanager, iwlwifi on Arch64. Sometimes on my laptop, networkmanager dies completely on resume from suspend but I have "alias nmr='sudo /etc/rc.d/networkmanager restart'" in my .bashrc to quickly fix it...

fwojciec · 2008-02-20 22:20:28

http://wiki.archlinux.org/index.php/Autowifi
A pain to configure at first if you're not familiar with the syntax of wpa_supplicant.conf but once configured it is the most elegant laptop wifi solution, IMO.

T-u-N-i-X · 2008-02-21 11:35:13

:S pffff, i'm at the office right now... it doesn't get connected no mather what i do... the first green light comes up and i start to follow the logs (/var/log/daemon.log) dhcp offer times out..... Then I deactivate wireless connections through networkmanager, do the following:

sudo ifconfig wlan0 up
sudo iwconfig wlan0 essid XXXXX key XXXXX
sudo dhclient wlan0

and it quickly gets connected..! I can't believe networkmanager sucks this much..! I recompiled it so that maybe it works better, nothing has changed....

zenlord · 2008-02-21 14:32:42

I can really vouch for netcfg2. Sure, you don't have a menu (yet) to chose networks from, but I have never seen it crash in my 2 months of using it. AND it is being developped in-house

Zl.

T-u-N-i-X · 2008-02-21 14:44:17

Yeah, but the problem is, it tries all wireless networks and then assumes that the cable is plugged in and runs the cable profile despite the cable is not connected..

aport · 2008-02-21 17:08:08

If you want a nice GUI replacement to networkmanager, wicd is pretty nice.

mintcoffee · 2008-02-21 17:54:27

Yep I can vouch for wicd. The latest version is great. I had a bad experience with NetworkManager, but wicd seems to be working flawlessly so far. The good part of wicd is that it's very lightweight. It's not very intrusive, so if all else fails, you can simply remove the daemon and tray applet, and connect manually. NetworkManager had a tendency to reset all my settings.

iphitus · 2008-02-21 21:14:11

NetworkManager always refused to see and connect to one of my available networks. Not hiddent SSID or anything, it just never showed it. Windows and everything else does (including netcfg2).

Further, I didnt like the fact I had to have a GUI up to run network manager (the console SoC project wasnt started then). It's not so friendly when it comes to tiling wm's either, as you've gotta fit a panel in there somewhere. xmonad handles this well though.

And then, if I ever did get connected, it was an unstable connection. It'd drop out, or just be plain weak. On my Uni connection, it never remembered my password or anything, I just got sick of typing it in allthe time.

So I filed a bug with network manager.... and it has _never_ been acknowledged. I refuse to use it until it is.

James

T-u-N-i-X · 2008-02-21 22:14:18

@iphitus: I used to have dhcp timeouts with netcfg and netcfg2.. I'll try it tomorrow if I have the same problem again tomorrow.. (I started using ipw3945 - and it works better: my wifi card sees more networks now than before) I didn't like the idea that it only scans for networks at startup...

If you're using a laptop computer, it's likely that you change location.. And it'd be nice to see a GUI for netcfg2.. (if there's an api or something like that, I can try the GUI) It would be better if the new netcfg2 could work as a daemon..

By the way, I couldn't get used to netcfg2 since it passes all wifi networks and uses the cable profile despite it's not connected.. (the profile was using a static ip address)

zenlord · 2008-02-26 09:48:14

T-u-N-i-X wrote:

By the way, I couldn't get used to netcfg2 since it passes all wifi networks and uses the cable profile despite it's not connected.. (the profile was using a static ip address)

You now have the option to exclusively connect to 1 profile (in v2.0.6) or cycle through the profiles and stop looking after a succesfull connection.

Zl.

T-u-N-i-X · 2008-02-26 11:33:43

zenlord wrote:

T-u-N-i-X wrote:
By the way, I couldn't get used to netcfg2 since it passes all wifi networks and uses the cable profile despite it's not connected.. (the profile was using a static ip address)
You now have the option to exclusively connect to 1 profile (in v2.0.6) or cycle through the profiles and stop looking after a succesfull connection.
Zl.

Sorry but I didn't understand if that's a solution for me ? Right now, I didn't add the cable profile to NETWORKS=() and connect to it manually if needed.. But of course it'd be nice if I could connect to it automatically..

Arch Linux

#1 2008-02-20 22:05:26

NetworkManager Sucks Very Bad :(

#2 2008-02-20 22:10:29

Re: NetworkManager Sucks Very Bad :(

#3 2008-02-20 22:20:28

Re: NetworkManager Sucks Very Bad :(

#4 2008-02-21 11:35:13

Re: NetworkManager Sucks Very Bad :(

#5 2008-02-21 14:32:42

Re: NetworkManager Sucks Very Bad :(

#6 2008-02-21 14:44:17

Re: NetworkManager Sucks Very Bad :(

#7 2008-02-21 17:08:08

Re: NetworkManager Sucks Very Bad :(

#8 2008-02-21 17:54:27

Re: NetworkManager Sucks Very Bad :(

#9 2008-02-21 21:14:11

Re: NetworkManager Sucks Very Bad :(

#10 2008-02-21 22:14:18

Re: NetworkManager Sucks Very Bad :(

#11 2008-02-26 09:48:14

Re: NetworkManager Sucks Very Bad :(

#12 2008-02-26 11:33:43

Re: NetworkManager Sucks Very Bad :(

Board footer