the madwifi-driver cant scan/wont get any results, unless the interface is brought up before scanning (ifconfig ath0 up). the rc-script doesnt consider this, and thus it cant bring the interface up. additionally, the madwifi card is very unstable when it comes to scan results. you get results with "iwlist ath0 scan" most of the time, but it never connects using the rc-scripts even though you bring the interface up Reproducible: Always Steps to Reproduce: /etc/init.d/net.ath0 restart Actual Results: /etc/init.d/net.ath0 restart * Starting ath0 * Configuring wireless network for ath0 * Failed to configure wireless for ath0 [ !! ] Expected Results: /etc/init.d/net.eth1 restart * Stopping eth1 * Bringing down eth1 * Stopping dhcpcd on eth1 ... [ ok ] * Shutting down eth1 ... [ ok ] * Starting eth1 * Configuring wireless network for eth1 * eth1 connected to "homenet" at 00:xx:xx:xx:xx:xx * in managed mode (WEP enabled - open) * Bringing up eth1 * Configuration not set for eth1 - assuming dhcp * dhcp * Running dhcpcd ... [ ok ] * eth1 received address x.x.x.x either apply a patch to the madwifi-driver to allow scanning regardless of int status, or create a /etc/conf.d/net configuration workaround for it? workaround is to set a static assosciation
The interface is brought up before scanning. Try setting sleep_scan_ath0="60" which will force a wait of 60 seconds after ath0 has been brough up and before it attempts a scan. If this works, reduce the number until you find a happy medium.
Then there must be another issue as I had previously tried with sleep_scan_ath0 vlue of 5, but now with 60 as you suggested, even 100 without any results.
Could you set RC_VERBOSE=yes in /etc/conf.d/rc and restart the script please? I use the madwifi driver myself and it works just fine.
Also, I just noticed that you're using WEP - can you connect without WEP? You'll need to turn WEP off at the AP as well to test.
Created attachment 52128 [details] verbose output of the network rc-script for both my 3crpag175 and ipw2100 As I booted up my laptop to test without WEP, my madwifi card actually managed to assosciate for the first time, without me touching any settings. I tried to reboot 3-4 times to test if it could assosciate a second time, but no.
Created attachment 52301 [details, diff] allows iwconfig and iwpriv setup before configure You'll need the above patch to try the following iwpriv_ath0="mode 3" This forces the card into g mode which is apparently sometimes required. Also, it looks like you have the essid hardcoded - the madwifi driver supports scanning, so you can remove the option essid_ath0= Lastly, if this still fails you can use wpa_supplicant instead as it supports madwifi cards and can connect to WEP secured AP's
Is your AP broadcasting its ESSID? If not, then try the patch in the forum linked below http://forums.gentoo.org/viewtopic-p-2351030.html#2351030
Re-open the bug if any of the above fails to fix it for you
