Linux - Wireless NetworkingThis forum is for the discussion of wireless networking in 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.
So I compiled the madwifi-ng drivers and got it all working. But on the next reboot, it complains about something like the device does not exist and the wireless doesn't start.
I jump to a terminal and type, "wlanconfig ath0 create wlandev wifi0 wlanmode sta" and it starts working and is fine... until next reboot. Then I have to do the same thing again to make it work.
So there must be a startup script somewhere that I should plug the wlanconfig line into???
i had this same problem, i tried creating the device in /etc/rc.local but it gave me an error, but once i logged in and executed the command it works. It is like wlanconfig doesn't exist until after the system is logged in.
Nope. Lost interest for a while. Other things to tinker with. I have a couple extra LAN wires at that station, so I just plugged one in and used that instead for now.
I can't remember how Fedora run level dirs are structured BUT you can make a script(make it executable chmod +x scriptname) in /etc/init.d/ (I think) with the commands to creaate the device and symbolic link it to your appropriate run level.
Ok I guess you can be extremely lazy and use ksysv editor. (I never used it)
I had the same sort of problem (I think). I got around it by using the full pathname for wlanconfig when calling wlanconfig from rc.local (or a script that is called by rc.local).
I currently have a separate shell script that is called by rc.local, and this script sets up the wireless-related stuff. Initially, I had calls to wlanconfig (which were causing problems), but I replaced those with the actual location of where the wlanconfig file is (i.e. using "//usr/local/bin/wlanconfig" instead of just "wlanconfig").
Here's the line I have in rc.local:
//etc/rc.d/startup_wireless.sh
And here's the contents of startup_wireless.sh:
#!/bin/bash
ifconfig eth0 down
//usr/local/bin/wlanconfig ath0 create wlandev wifi0 wlanmode sta
modprobe wlan_scan_sta
ifconfig ath0 xxx.xxx.xxx.xxx netmask 255.255.255.0 up
//usr/local/bin/wlanconfig ath0 list scan
iwconfig ath0 key "xxxx:xxxx:xxxx:etc"
iwpriv ath0 authmode 2
iwconfig ath0 essid "xxxxxxxxxx"
route add default gw xxx.xxx.xxx.xxx
If you decide to do something like this, you'll have to modify the contents of setup_wireless.sh to include whatever commands you would normally call after you boot up in order to get wireless working.
And make sure to do a chmod on startup_wireless.sh to make it executable.
I can't remember how Fedora run level dirs are structured BUT you can make a script(make it executable chmod +x scriptname) in /etc/init.d/ (I think) with the commands to creaate the device and symbolic link it to your appropriate run level.
Ok I guess you can be extremely lazy and use ksysv editor. (I never used it)
The proper way is to use the special markups inside the comments of the init script.
Use the chkconfig program to manage the symbolic links for you. People should not finick around with anything in rc3.d/...
Put the script in rc.d/... and do 'chkconfig servicename on'.
system-config-services (I think) can use the chkconfig syntaxed files as well.
I'm stuck with the same problem.
I think what needs to be done is the ath0 device should be loaded and the optional wpa_configurator (or whatever the name of that wpa extension thing is), just before the ath0 interface comes up.
/etc/sysconfig/network-scripts/ifup-ath
could be used. However, it'll then bypass all the normal initialization stuff, including any dhcp stuff.
Another possibility is to the wlanconfig...sta command and the wpa_config... command at the bottom of the rc.local file.
Then, not have the ifup-ath file, and keep the normal TYPE=Wireless setting in ifcfg-ath0.
A simple 'ifup ath0' should bring up the interface. If ONBOOT=YES then a 'service network restart' as well as a reboot should bring it up also.
I read through the ifup and network-functions scripts, and I can't come up with anything better than putting the ath0 pre-init stuff in rc.local.
Ok, I'm back. Here's what I did that works. I did go with the /etc/rc.d/init.d thing and not rc.local. That way seems cleaner and I can start and stop the ath0 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.