FS#11273 - [initscripts] New network daemon fails to associate with a significant number of cards.
Attached to Project:
Arch Linux
Opened by Connor Behan (connorbehan) - Wednesday, 20 August 2008, 23:11 GMT
Last edited by Paul Mattal (paul) - Saturday, 06 February 2010, 13:56 GMT
Opened by Connor Behan (connorbehan) - Wednesday, 20 August 2008, 23:11 GMT
Last edited by Paul Mattal (paul) - Saturday, 06 February 2010, 13:56 GMT
|
Details
Description:
Since the 18/08/08 initscripts update, running /etc/rc.d/network start fails on unsecured networks with "Could not associate ath0 - try increasing WIRELESS_TIMEOUT and check networkis WEP or has no security" regardless of WIRELESS_TIMEOUT value for ath0 drivers and possibly others. Workarounds exist. Additional info: * initscripts 2008.08-1 * relevant /etc/rc.conf areas: MODULES=(ath0) INTEFACES=(ath0) ath0="dhcp" DAEMONS=(network) * /etc/conf.d/wireless: wlan_ath0="ath0 mode managed essid default" WLAN_INTERFACES=(ath0) Steps to reproduce: Setup your files as shown above, turn on an unsecured wireless router, insert an affected card such as an Atheros one and startup your system. |
This task depends upon
Closed by Paul Mattal (paul)
Saturday, 06 February 2010, 13:56 GMT
Reason for closing: Fixed
Additional comments about closing: We believe this is fixed in newer versions of initscripts, but requests for confirmation have not been answered. Please request reopen if you have evidence this is still a bug.
Saturday, 06 February 2010, 13:56 GMT
Reason for closing: Fixed
Additional comments about closing: We believe this is fixed in newer versions of initscripts, but requests for confirmation have not been answered. Please request reopen if you have evidence this is still a bug.
Extra tip: the network script *does* apply the "mode", "essid" (things you set with iwconfig), etc, but nothing regarding ip/netmask (things you set with ifconfig) so the network remains down.(at least for me)
Extra tip2: if you manually set ip/netmask using ifconfig and the bring up the wireless interface, and then run again the network script , it reports no errors and seems to "complete" its tasks, but your connectivity is poor (at least for ad-hoc that i tested) *and* dmesg brings a lot of messages like :
..............
wlan0: beacon TSF higher than local TSF - IBSS merge with BSSID 26:00:9d:76:70:bb
wlan0: Configured IBSS beacon template
phy2: Adding new IBSS station 00:16:b6:a1:0e:6e (dev=wlan0)
wlan0: Configured IBSS beacon template
phy2: Adding new IBSS station 00:16:b6:a1:0e:6e (dev=wlan0)
wlan0: Configured IBSS beacon template
..............
After commenting out this lines in /etc/rc.d/network
#bssid=`iwgetid $1 -ra`
#if [[ "$bssid" = "00:00:00:00:00:00" ]]; then
# printhl "Could not associate $1 - try increasing WIRELESS_TIMEOUT and check network is WEP or has no security"
# return 1
#fi
it start working again.
The same behaviour described in http://bbs.archlinux.org/viewtopic.php?pid=408692#p408692
/usr/sbin/iwconfig $iwcfg
[[ -z "$WIRELESS_TIMEOUT" ]] && WIRELESS_TIMEOUT=2
sleep $WIRELESS_TIMEOUT
bssid=`iwgetid $1 -ra`
if [[ "$bssid" = "00:00:00:00:00:00" ]]; then
printhl "Could not associate $1 - try increasing WIRELESS_TIMEOUT and check network is WEP or has no security"
return 1
fi
It appears that these lines configure the device, but don't bring it up. They then test to see if it has associated with an access point, which by my understanding cannot happen unless the device has been brought up. I inserted a line that says "/sbin/ifconfig ${1} up" after the "/usr/sbin/iwconfig" line, and now the script works for me.
So i worked around in this way:
bssid=`iwgetid $1 -ra`
bssid="00:1B:11:3F:66:6A" # force the NWID
if [[ "$bssid" = "00:00:00:00:00:00" ]]; then
printhl "Could not associate $1 - try increasing WIRELESS_TIMEOUT and check network is WEP or has no security"
return 1
fi
http://bugs.archlinux.org/task/13299
for a patch to fix this issue.
Thanks.