SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
My Slackware 14.1 box is on my wireless network (I have no other option at the moment). I am currently using wicd to manage the connection but I think that is causing some problems.
Specifically, it appears the with wicd the wireless connection is not established until much later in the start up than the standard network start up happens. This appears to be causing problems for certain services (I've noticed ddclient and sendmail seem offended by this).
So, I want to connect to my wireless network right from the beginning but I have no idea how to do wireless stuff manually.
Well, I'm not using Wicd, but I am using NetworkManager (which I have mixed feelings about...), but in NetworkManager if you check the box that says "Automatically connect to this network when it is available" and "All users make connect to this network" in the Connection properties of your wireless, it'll connect on boot. I'd think there would be a similar option in Wicd.
Well, I'm not using Wicd, but I am using NetworkManager (which I have mixed feelings about...), but in NetworkManager if you check the box that says "Automatically connect to this network when it is available" and "All users make connect to this network" in the Connection properties of your wireless, it'll connect on boot. I'd think there would be a similar option in Wicd.
It connects automatically in wicd, just (I think) later in the boot process than it needs to for some things to work right.
It connects automatically in wicd, just (I think) later in the boot process than it needs to for some things to work right.
Ooooh. I need more coffee, or better reading skills.
Well, the time at which wicd and networkmanager are started, and thus connecting to the network, is dictated by /etc/rc.d/rc.M (on line 193 is the call for wicd on my machine), which is called after the call to rc.inet1, which is at line 98. I suppose you could try moving the wicd call up higher to around line 98, but that may have unintentional side effects...
Ooooh. I need more coffee, or better reading skills.
Well, the time at which wicd and networkmanager are started, and thus connecting to the network, is dictated by /etc/rc.d/rc.M (on line 193 is the call for wicd on my machine), which is called after the call to rc.inet1, which is at line 98. I suppose you could try moving the wicd call up higher to around line 98, but that may have unintentional side effects...
Hmmm. Interesting. The offended services are starting after the line that starts wicd, so I'm not sure that's the full story.
On my laptop which uses wicd for all connections, I typically do not have a connection finalized until I log in. It appears that, although wicd starts, it doesn't re-establish connections immediately. I don't know how to test that though.
I know that you can put stuff in rc.wireless (or something like that) that establishes a connection. My setup currently tries to DHCP but uses eth0 instead of wlan0. Maybe I could try re-running the netconfig program, which has an option for NetworkManager and see if that does it.
...I know that you can put stuff in rc.wireless (or something like that) that establishes a connection. My setup currently tries to DHCP but uses eth0 instead of wlan0. Maybe I could try re-running the netconfig program, which has an option for NetworkManager and see if that does it.
Configuring via rc.wireless.conf is deprecated. Try configuring your wireless via rc.inet1.conf,
here's a nice doc that describes the process, not hard but it takes a few short steps. http://alien.slackbook.org/dokuwiki/...ckware:network
Configuring via rc.wireless.conf is deprecated. Try configuring your wireless via rc.inet1.conf,
here's a nice doc that describes the process, not hard but it takes a few short steps. http://alien.slackbook.org/dokuwiki/...ckware:network
Thanks for that link. It looks like there is a ton of great information there. I'll dig in a bit later and see what to do for my system.
All right. I've got my computer configured to connect to wlan0 via rc.inet1.conf as described in the page of Alien Bob's. However, that did not seem to fix at least one of the issues I was having.
Specifically, until I restart sendmail it rejects everything from outside claiming that the domain of the sender address does not resolve. If I restart sendmail (/etc/rc.d/rc.sendmail restart) things work. It may make sense for me to start a new thread on this issue since it is not directly the issue in the OP.
Other curiosities. Now when I log in the NetworkManager applet starts but claims I have no network connection. I clearly do as I am typing this from that machine.
Second thing, the wicd applet still started even though I removed the execute bit from /etc/rc.d/rc.wicd to prevent the daemon from starting.
Second thing, the wicd applet still started even though I removed the execute bit from /etc/rc.d/rc.wicd to prevent the daemon from starting.
The applet will start regardless of the daemon due to /etc/xdg/autostart/wicd-tray.desktop existing. If you remove that you should see the behavior cease.
Other curiosities. Now when I log in the NetworkManager applet starts but claims I have no network connection. I clearly do as I am typing this from that machine.
Second thing, the wicd applet still started even though I removed the execute bit from /etc/rc.d/rc.wicd to prevent the daemon from starting.
AFAIK, NetworkManager doesn't know about connections it didn't set up. So, unless you set up the connection in NetworkManager (like you did with wicd -- and likely having the same issues wicd did), it would likely register that no network is available.
To remove it from your tray, it'd likely be something similar to what frankiej mentioned, but with a NetworkManager (or possible nm-applet) file in the same directory.
AFAIK, NetworkManager doesn't know about connections it didn't set up. So, unless you set up the connection in NetworkManager (like you did with wicd -- and likely having the same issues wicd did), it would likely register that no network is available.
To remove it from your tray, it'd likely be something similar to what frankiej mentioned, but with a NetworkManager (or possible nm-applet) file in the same directory.
That's helpful to know that "NetworkManager doesn't know about connections it didn't set up." I have seen that in one of the rc files there is processing that if it finds an executable rc.wicd it runs that, otherwise it starts NetworkManager if it has an executable rc file. So I bet if I "chmod -x rc.networkmanager" that will take care of it.
That's helpful to know that "NetworkManager doesn't know about connections it didn't set up." I have seen that in one of the rc files there is processing that if it finds an executable rc.wicd it runs that, otherwise it starts NetworkManager if it has an executable rc file. So I bet if I "chmod -x rc.networkmanager" that will take care of it.
I'm pretty sure I don't have rc.networkmanager executable on my system (but I'll have to check -- I'm pretty sure I didn't enable it during install, and I know I wouldn't have enabled it any other time), but I still have the nm-applet in the tray. I've just been too lazy to actually remove it, but I may try the suggestion that frankiej gave for removing the wicd tray applet and see if that works.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.