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.
I have Slackware 12 installed on my laptop (Tecra M2) and am trying to set up wireless.
The intel 2200bg wireless chip works fine.
My access point uses WPA so I understand that I have to use wpa_supplicant.
I got all that working from command line.
I start wpa_supplicant first with
wpa_supplicant -B -ieth1 -c/etc/wpa_supplicant.conf
I have the configuration for my AP entered in wpa_supplicant.conf and that part works fine now.
Next I just obtain an IP address with
dpcpcd eth1
That's it. I'm connected and networked.
Now, what I don't know is how do I automate it all?
I use rc.local to start wpa_supplicant for now
and then run dhcpcd from cli manualy.
KDE's wifi manager is useless as it doesn't work with wpa.
Any suggestions?
In particular, at point during boot and from where do I start the wpa_supplicant?
might want to put all those commands together in a script, and run it from rc.local from background, that way the commands will work one after the other and won't slow down the bootup process.
I think rc.local is a fine place for placing those.
Edit the file /etc/rc.d/rc.wireless.conf
You have to put here the configuration of your wireless card.
I have something like this :
Code:
*)
INFO="My Network"
ESSID="MyESSID"
;;
The important thing here is the ESSID. If you need more option, the file is well documented.
Edit the file /etc/rc.d/rc.inet1.conf
You set here the configuration for each of your network interface. If you use eth1 you should have something like this :
USE_DHCP="yes" says that you get your IP address by DHCP.
WLAN_WPA="wpa_supplicant" says that you use wpa_supplicant for authentification.
WLAN_WPADRIVER="wext" is the WPA driver for Intel 2200BG.
There are others configuration attributes but I don't use any of them (see the file itself for all possibilities).
Be sure that /etc/rc.d/rc.inet1 and /etc/rc.d/rc.wireless are "executables" and at the next boot your connexion will be automatically up
Thanks to all for your replies and help.
The rc.local solution is certainly an option but the downside is that any services that depend on a network interface being up and running will not function correctly.
So I like etienne's solution best and I think it's how Slackware meant for the network to be configured.
I will test it later today and see if it'll work for me.
Maybe suitable for a new thread, and if so let me know, but I'll ask anyway.
I've used wpa_gui for the first time and see that it has the ability to update wpa_supplicant.conf if run as root.
Is it something that would be useful when connecting to public wifi AP, or any AP outside of my regular network?
How do people with Slackware scan for wifi AP's? And subsequently connect to them?
Well, it's working great.
I followed etienne's advice and entered the settings there.
I did have wpa_supplicant.conf configured beforehand though.
The only thing I had to do is download and install the firmware.
Now when I boot, I'm automaticaly connected to my wireless AP.
However, dmesg doesn't show any info, ip, mac etc, like it used to for regular wired connection, but I can live with that.
Thanks all for your help.
I'd like to share my solution here which is to edit rc.wireless.conf. The original rc.wireless.conf after a clean installation is a case driven script. I think it too complicated for my need. So I just replace it with my own one:
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.