that blob looks the same to me.

Hi,

Why so? I guess my laptop still connects with the proper script usage.

Maybe you need a hold your hand means to connect. I do not!

I can do the same with my wired and wireless Desktops. No need to have someone between my needs to get things done. Each to his/her own. I'll keep doing it my way and you can keep doing it your way.
That's whats nice about Slackware, you can get things done without someone between you and the required task(s).
Hope this helps.
Have fun & enjoy!

I use Network Manager on my netbook, since 14.1. Before that, I used WICD. My desktop systems are all wired, so rc.inet1 on them.

Hi,
I don't use either Networkmanager or wicd. I have a collection of rc.d/rc.inet1.conf.<something> files, of which one (for the network I wish to be associated with) is symlinked to rc.d/rc.inet1.conf.

I have a simple script which will do this for me and restart the network.

cheers
pete

pete hilton
saruman@ruvolo-hilton.org

Nope.

It's really convenient to use NetworkManager or wicd for laptops.

I've used rc.wireless.conf to connect to wireless networks; it wasn't convenient but it was doable.

I'm not going to throw rocks at people using a tool to make something much easier (especially since I use the tool myself!), but I'm not going to claim that the job can't be done otherwise.

4 members found this post helpful.

I had trouble with wicd ages ago, not getting connections or losing them, so I switched to NetworkManager.

3 members found this post helpful.

I switched to NetworkManager a long time ago. I think since when it was first introduced in Eric's ktown before it hit Slackware.

2 members found this post helpful.

I have my own network discovery/setup scripts, mostly for wireless, which I have shared here on a couple of occasions.

About a year ago I combined most of them into a single script which I've been trying to build up into an automated solution (similar to networkmanager/wicd, but cli only).

A genuinely generalized solution is hard, though, and I'm not entirely happy with it yet, but I do use it daily.

I decided to keep using KDE 4 so I'm using NetworkManager because it's integrated out-of-the-box.

1 members found this post helpful.

Touche.

I don't see why it has to be fully generalized. Just good enough to be a starting point. NM and wicd are too generalized and hide details to cause them to be more of an annoyance. The nice thing about a scripted approach is that you can fully customize it.

I use inet1.conf to bring the interfaces to a sane state, including laptops, and just use the right tools (customized wpa_supplicant, scripts) for mobility. Then not having a fancy applet completely goes unmissed. Casual users do not notice at all.

1 members found this post helpful.

I ran WICD for a time and it worked well for me. I use Networkmanager now on all of my desktops and laptops; it is stable, and works well for me.

1 members found this post helpful.

I always seem to have a problem with network manager especially after switching users so my daughter can use the laptop, always seems to prompt for a WPA key. Anyway easiest thing for me to do was use rc.inet1, works perfect and all connected before she even types startx. It also means my daughter wont wake me at 7.00am asking for the WPA key.

I've just come back from 1.5 weeks in Turkey and my netbook had a bit of a marathon with wifi since I was in three cities [four if you count the airport].

Networkmanager was able to connect to wifi in some guy's taxi in Antalya and to the wifi in our residence further South in Turkey. However, the hotel we stayed in in another city had wifi which I couldn't connect to: I went to the front desk and they said it was because of a technical issue with our room. The tech guy knew what he was doing though - he whitelisted my mac address ["ah, Linux!"] and after that it was fine.

The biggest issue was Istanbul airport where I failed to get online at all. The Starbucks wifi was configured for smartphones and I don't use a smartphone. The plan is when you tap on the network a box automatically comes up and asks you for your phone number, then they text you a code which you use as a password. Of course this didn't work with my Slackware netbook and I gave up. My wife also tried to connect on her Windows 8 laptop and failed. I find this rather worrying that some places will force users to use smartphones to connect to wifi [other restaurants and bars in the airport were also using Starbucks wifi so Starbucks had their customers' data too].

I've had to fiddle around a bit in the Networkmanager settings for wifi at my university, and I think getting that to work was pot luck. Overall though, Networkmanager has worked for me so I don't plan on changing it.

I haven't had many problems with NetworkManager.

One recent problem that just surface was with my new laptop. I'm using Slackware64-current Ktown Plasma testing.

I could not connect at the office to the providers box, it would go through the motions but never establish a connection. This was true for both the wifi and ethernet. At home no problem connecting via ethernet or Wifi. Same provider, different boxes. Home box has one LAN port, which I connect to my router. Office has wifi and two LAN ports.

Weird part was until a few days ago the laptop connected find at the office. Not sure what changed. I don't think is was the recent updates in Slackware64-current, could be I suppose but can't pin point it down.

I solved the problem by switching the laptop to use dhclient instead of dhcpcd. Works at home too.

Anyway been quite happy with NetworkManager. I've been using it since Eric introduced it in ktown back 2011.

1 members found this post helpful.