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.
Eh, "made sure rc.wireless is -x"? You removed the executable bit from rc.wireless? That will be the cause then, rc.wireless needs to be executable because that is what starts wpa_supplicant.
Eric
Quote:
Originally Posted by Alien Bob
Never use rc.wireless.conf please, use rc.inet1.conf also for your wireless configuration. In "man rc.inet1.conf" you will find "/etc/rc.d/rc.wireless.conf - configuration parameter file ( deprecated )".
You have me confused, now. I have rc.wireless/rc.wireless.conf up and running, and of course am obeying rule no. 1 "Ïf it works, don fix it!"
For those of us with wpa2 security, what is recommended? Run rc.wireless but leave rc.wireless.conf blank?
You have me confused, now. I have rc.wireless/rc.wireless.conf up and running, and of course am obeying rule no. 1 "Ïf it works, don fix it!"
For those of us with wpa2 security, what is recommended? Run rc.wireless but leave rc.wireless.conf blank?
I put the appropriate information in /etc/wpa_supplicant.conf...
You have me confused, now. I have rc.wireless/rc.wireless.conf up and running, and of course am obeying rule no. 1 "Ïf it works, don fix it!"
For those of us with wpa2 security, what is recommended? Run rc.wireless but leave rc.wireless.conf blank?
Let me point (again) to http://alien.slackbook.org/dokuwiki/...eless_networks where I explain my reasons. You also should not be running rc.wireless yourself. I is the task of rc.inet1 to invoke the wireless script if it detects a wireless network interface.
For WPA wireless connections, you have to configure the WPA part in /etc/wpa_supplicant.conf amd indicate in rc.inet1.conf that you are using WPA and wpa_supplicant for the interface.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.