wicd does that (connect automatically after hibernation) for me now. Oh, it can be futzy, but it's running much better since the upgrade.

I set up NM as directed in the changelog, but I can't run KDE on this tiny eeepc 2G surf, and I haven't found any need to try it any other way.

I switched back to wicd for a few days after the big kde update in -current because it broke my NetworkManager applet (I use xfce). I've since recompiled it and everything is okay. But during those few days I noticed this with wicd, and remembered this "problem" from before when I used wicd. Perhaps I was just impatient and did not give it long enough to connect, but NM reconnects almost instantly.

Brian

@cwizardone
thanks for your reply!
well yeah,, that's exactly the problem is.. i was using Xfce, switched from KDE coz it's too heavy for my laptop and now i've been using fluxbox for months and i absolutely love it

so that time i went using SlackBuild from slackbuilds.org which didn't work, then i tried using the one that came with GNOME SlackBuild without installing GSB itself -> this caused more problems. that's why i ended up using wicd again,
and had to use Vista whenever i needed to use my iPad. doesn't matter, i've got a router at home now
i'll try using NetworkManager when i get a better pc. i'm quite confident if it's already included in the mainstream.

still, i'm quite curious.. has anybody actually tried using NetworkManager to create an adhoc wireless network that shares internet connection coming from the lan card?

Yeah, I've done it once or twice, but in my experience, you can only connect to ONE(1) machine.

Is there a way to get networkmanager to connect without having to boot into X or start KDE ?
Wicd connects as soon as Linux boots to the console, without having to startx.

Yeah, if you have NetworkManager installed(by whatever means you choose to do so, I used SBo):

I've been asking myself the same thing.... however didn't had the time to try networkmanager until now.
I see no real advantage of network manger over wicd to be honest... in fact, i'm very used to wicd

i'll keep on using networkmanager for the time been and see if i can work with it

NetworkManager is a more modularized system for all types of connections ranging from specialized things like VPNs to everyday connections while Wicd is a more traditional utility just for everyday usage.

NM however is a more featured connection manager though.

The ModemManager module of NM freezes my PC for many seconds when I plug in my USB modem key. Apparently it is recognized as four different serial ports and instead of using the first one, MM cycles over the four ports trying to connect; in the meantime everything is frozen. Disabling ModemManager and connecting manually with pppd is the only solution I found. Is anyone having similar issues?

I had been using wicd for a long time and was very happy with it till it was upgrades to a new version.
Then, wicd would refuse to take a password on a new install of Slack. (WPA2) Or if anything changed forcing me to re-enter the password. I messed around with it for a week or two and then found there was a WPA2 bug that hadn't been resolved. Switched back to an older version and everything was fine.
Decided to try Networkmanager and it just plain worked right out of the box with -Current after issuing chmod +x /etc/rc.d/rc.networkmanager..

Of my 13.37 system I had to use the SlackBuilds and modify rc.M but that worked out also.

The main advantage Wicd has over Network Manager is that Wicd allows you to configure in the DNS servers where as Network Manager will not.

I prefer wicd because I find it simpler. However, Network Manager is not too bad either. I am ok with both.

Sorry, I don't believe that is correct.

I'll take this remark to indicate that Network Manager now handles custom DNS setups, because the version of Network Manager that I used under Linux Mint last year definitely did not support this. That was the reason I abandoned it for Wicd.