NetworkManager not working (WICD does)
 

Ok, just like the title says, Network Manager is not working for me, It never did (for me, since 13.37), but I wasnt worried becasue WICD did all the job I needed.

But now, I would like to work with both, wired and wireless connection, and of
course, WICD does not support that, you have to choose between wired or wireless.

So, Ive been trying to make Networkmanager work. So far,wihtout any success.

NM did work on my debian (same laptop).

Im running Slackware64 14.1 (multilib). Linux ASUS 3.10.17 x86_64 Intel(R) Core(TM) i5-2430M CPU @ 2.40GHz GenuineIntel GNU/Linux

My laptop specs:

ASUS N53SV
8Gb RAM

Ethernet Adapter:
Realtek Semiconductor Co., Ltd. RTL8111/8168 PCI Express Gigabit Ethernet controller
RTL8111/8168 PCI Express Gigabit Ethernet controller (0x8168)
Device 0a00 (0x0000:0x0A00)

Wireless Adapter:
Atheros Communications Inc. AR9285 Wireless Network Adapter (PCI-Express)
AR9285 Wireless Network Adapter (PCI-Express) (0x002B)
Device 0a00 (0x0000:0x0A00)

I tried to uninstall, reinstall, compile and install again NM, NM-applet, libraries etc...

I DID ENABLE NETWORKING on nm-applet. Ive run out of ideas. Suggestion, or any other network manager that supports both wired and wireless at the same time?

The last I knew wicd did allow for wired connections. You just need to go to properties and tell wicd what your your ethernet is labeled (ie: eth0). To find that open terminal, become root and enter iwconfig. It will also list what your wireless connection is.

below is from here: http://docs.slackware.com/slackware:beginners_guide

You can get a lot of information from here as well.

Graphical Network Configuration Services
Slackware currently has some alternatives to configure and monitor your network connections. These install a daemon (aka a background service) which will allow you to switch between wired and wireless connections easily. That makes them perfectly suited for mobile users. They come with graphical configuration utilities and do not depend on the traditional Slackware configuration files - in fact, those files will cause conflicts if they contain network configuration.

You will find wicd in the extra section of the Slackware release tree (the word extra means that it is not part of the core distribution and will not have been installed as part of a full installation).
After installing the wicd package, you have to make its init script executable so that the network daemon automatically starts at boot:
# chmod +x /etc/rc.d/rc.wicd
You can then configure your network using the graphical tool wicd-client or if you are running Slackware 14 you can use the KDE widget for wicd instead. For console lovers, there is also wicd-curses which offers the same configuration capabilities as the X-based counterparts.

Starting with Slackware 14, there is also Networkmanager. It will be installed as part of a full install, but the network daemon will not be started by default. As with wicd, you have to make its init script executable:
# chmod +x /etc/rc.d/rc.networkmanager
which will make NetworkManager start at boot. You will have to configure NetworkManager using an X-based graphical utility.
Slackware 14 includes a KDE widget for Networkmanager. If you are using another Desktop Environment like XFCE, you can install the Gnome network-manager-applet from SlackBuilds.org.

In addition to three wired servers (well, desk tops), I use a laptop (a Dell 1750) both wired (at home) and wi-fi (not at home) and WICD handles both connections with ease without any configuration on my part other than the log in and password for a wi-fi connection. I can connect at home with a wi-fi connection (wife has a Kindle, it needs wi-fi, I have a second router that provides that); I prefer wired, though, it's faster.

Thing is, WICD sees whatever is available and lets you connect either way. Don't know what network manager does (and don't really wanna, frankly) but if it requires a bunch of set up, why bother? WICD has gotten to be "just works" (at least here).

Hope this helps some.

Just to clarify what n4rf wants - Network Manager is happy to use both the wired and wireless connections in parallel, but AFAIK wicd can't do that.

I won't take sides in the endless NM vs. wicd debate, neither is entirely satisfactory :(

thank you 55020. Sorry If did not express myself clear enough. Yes, I need to use both, wired and wireless connections in parallel, for example: internet over wifi, and control a device over wired, and bridge them both, so the device has internet access: Thats why WICD wont quite fullfil my requirements.

You're correct (AFAIK), one or the other active with WICD (I do have to wonder, though, why anybody would want to connect a machine with parallel network connections on a single network card). I mean, you've got a server, you've got a router/switch/whatever, you've got an Ethernet cable, why screw around with wi-fi? No cable? Wi-fi. Six of one, half dozen of the other... just not both at the same time? I'm not being a smart-ass, I'm actually wondering why.

I don't think Wicd was made to do that, in other words what you want is to make the computer behave like a router, to share the wi-fi connection is receiving from the router, and then send it to the wired one, is that correct?

If that is the case then you need some iptables rules, or if you have a firewall tool, through that would be possible to achieve such setup.

Regards

You can do this with a bridged adapter setup. I've never tried it, but here's a link to a post in the antix forums that highlights a succesful bridging of a wireless adapter to a wired adapter.

http://antix.freeforums.org/post32263.html#p32263

note this is for a debian based system. I assume there would be some differences in a slackware setup.

NetworkManager not working (WICD does)
 

i need both connections because over wifi i get internet. and the ethernet port will be in use for a device i designed myself. i simply need both connecions so i can have internet while debugging programig the device.. i have severeal input/ouput i have to test while connected to the decice. router is out of my reach. other words would be that router is in smallroom full of stuff where i can not access and since network manager allowed me to do it on debian (and also was able to do it with windows) i wanted to make it work on slackware. thats why i want both interfaces working at the same on my slackware

You can setup the wired interface in "/etc/rc.d/rc.inet1.conf" and manage wireless with wicd. I used to do it this way, though now I manage both with "/etc/rc.d/rc.inet1.conf".

Thank you very much! :D


Even tho it did not solve titles description, it has solved the purpouse of the post. Mark as solved?

When you want to run networkmanager make rc.networkmanager executable, _and_ don't forget to remove the executable bit from /etc/rc.wicd. Otherwise networkmanager will not come up.

Sorry if this is too basic, no insult intended. But I tripped over the executable rc.wicd at some time....

fsauer good to know that! I did not know it! don't worry.. no insult taken. Its those little details that someone else has already tripped over, and may prevent you from tripping with them. Thank you very much. I find it very helpful :D

Found a simple solution!
 

To activate Network Manager ... Run this in terminal :-

also add this code to startup ... to run network manager on startup... enjoy