LinuxQuestions.org
Help answer threads with 0 replies.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices


Reply
  Search this Thread
Old 10-18-2014, 09:15 AM   #1
statguy
Member
 
Registered: Sep 2004
Location: Ontario, Canada
Distribution: Slackware 14.2, current
Posts: 416

Rep: Reputation: 36
Connecting to wireless network at boot


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.

Can anyone offer advice?

Thanks
 
Old 10-18-2014, 09:48 AM   #2
ProbablyAndy
LQ Newbie
 
Registered: Oct 2014
Posts: 2

Rep: Reputation: Disabled
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.
 
Old 10-18-2014, 09:51 AM   #3
statguy
Member
 
Registered: Sep 2004
Location: Ontario, Canada
Distribution: Slackware 14.2, current
Posts: 416

Original Poster
Rep: Reputation: 36
Quote:
Originally Posted by ProbablyAndy View Post
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.
 
Old 10-18-2014, 10:02 AM   #4
ProbablyAndy
LQ Newbie
 
Registered: Oct 2014
Posts: 2

Rep: Reputation: Disabled
Quote:
Originally Posted by statguy View Post
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...
 
Old 10-18-2014, 10:14 AM   #5
statguy
Member
 
Registered: Sep 2004
Location: Ontario, Canada
Distribution: Slackware 14.2, current
Posts: 416

Original Poster
Rep: Reputation: 36
Quote:
Originally Posted by ProbablyAndy View Post
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.
 
Old 10-18-2014, 01:10 PM   #6
dr.s
Member
 
Registered: Feb 2010
Distribution: Slackware64-current
Posts: 338

Rep: Reputation: 156Reputation: 156
Quote:
Originally Posted by statguy View Post
...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
 
1 members found this post helpful.
Old 10-18-2014, 01:16 PM   #7
statguy
Member
 
Registered: Sep 2004
Location: Ontario, Canada
Distribution: Slackware 14.2, current
Posts: 416

Original Poster
Rep: Reputation: 36
Quote:
Originally Posted by dr.s View Post
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.
 
Old 10-19-2014, 08:17 PM   #8
statguy
Member
 
Registered: Sep 2004
Location: Ontario, Canada
Distribution: Slackware 14.2, current
Posts: 416

Original Poster
Rep: Reputation: 36
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.
 
Old 10-19-2014, 10:24 PM   #9
frankiej
LQ Newbie
 
Registered: Feb 2013
Distribution: Fedora
Posts: 29

Rep: Reputation: 24
Quote:
Originally Posted by statguy View Post
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.
 
2 members found this post helpful.
Old 10-20-2014, 08:13 AM   #10
bassmadrigal
LQ Guru
 
Registered: Nov 2003
Location: West Jordan, UT, USA
Distribution: Slackware
Posts: 8,792

Rep: Reputation: 6656Reputation: 6656Reputation: 6656Reputation: 6656Reputation: 6656Reputation: 6656Reputation: 6656Reputation: 6656Reputation: 6656Reputation: 6656Reputation: 6656
Quote:
Originally Posted by statguy View Post
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.
 
1 members found this post helpful.
Old 10-20-2014, 08:19 AM   #11
statguy
Member
 
Registered: Sep 2004
Location: Ontario, Canada
Distribution: Slackware 14.2, current
Posts: 416

Original Poster
Rep: Reputation: 36
Quote:
Originally Posted by bassmadrigal View Post
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.
 
Old 10-20-2014, 01:40 PM   #12
bassmadrigal
LQ Guru
 
Registered: Nov 2003
Location: West Jordan, UT, USA
Distribution: Slackware
Posts: 8,792

Rep: Reputation: 6656Reputation: 6656Reputation: 6656Reputation: 6656Reputation: 6656Reputation: 6656Reputation: 6656Reputation: 6656Reputation: 6656Reputation: 6656Reputation: 6656
Quote:
Originally Posted by statguy View Post
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.
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
Ubuntu 11.10 Network Manager issues connecting to wireless network after restart depam Linux - Software 2 01-22-2012 08:39 PM
Wireless network available but not connecting nicdaug Linux - Wireless Networking 4 02-09-2011 08:00 PM
Connecting to my wireless network Iyeck Linux - Newbie 6 06-29-2007 04:17 AM
connecting to a wireless network newbiesforever MEPIS 3 04-11-2007 04:36 PM
wireless network not connecting jburford Linux - Wireless Networking 11 07-08-2005 08:14 AM

LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware

All times are GMT -5. The time now is 06:14 AM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Open Source Consulting | Domain Registration