FS#10585 - Netcfg2 fails to associate atheros card with WEP access point (working patch provided)

Attached to Project: Arch Linux
Opened by Scott Cassidy (scottlc) - Wednesday, 04 June 2008, 14:24 GMT
Last edited by James Rayner (iphitus) - Wednesday, 06 August 2008, 12:57 GMT
Task Type Bug Report
Category Packages: Core
Status Closed
Assigned To James Rayner (iphitus)
Architecture i686
Severity Low
Priority Normal
Reported Version 2007.08-2
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:

Netcfg2 fails to associate my atheros card with a WEP access point; though WPA works fine. This happens every single time. The ESSID is correctly set by netcfg2, as reported by iwconfig, but the status stays at "not associated". It should be noted that netcfg2 doesn't complain about not associating, but merely fails silently.

My own research has shown that this atheros (madwifi) card does not seem to like netcfg2 calling iwconfig while the interface is still up. I have patched my copy of netcfg to bring the interface down before calling iwconfig in the WEP part. I have attached this modification as a unified diff to "/usr/lib/network/wireless.subr". After applying this simple modification, netcfg2 successfully associates with the WEP access point.

I would suggest, however, that the correct modification would be to always make sure that the interface is brought down at the start of wireless_up(), and only brought up again after iwconfig has been called for the last time. (i.e. configure first, then association will begin when the interface is brought up)


Additional info:

Output of lspci:
02:00.0 Ethernet controller: Atheros Communications, Inc. AR5212/AR5213 Multiprotocol MAC/baseband processor (rev 01)

Netcfg2 profile:
CONNECTION="wireless"
INTERFACE=ath0
SCAN="yes"
SECURITY="wep"
ESSID="[removed]"
KEY="[removed]"
IP="dhcp"
TIMEOUT=30
This task depends upon

Closed by  James Rayner (iphitus)
Wednesday, 06 August 2008, 12:57 GMT
Reason for closing:  Implemented
Additional comments about closing:  quirk merge. Suggest that this should be followed up upstream
Comment by James Rayner (iphitus) - Thursday, 05 June 2008, 05:06 GMT
That's crap behaviour on Atheros' behalf. Please file a bug with the developers upstream.

Some drivers require the ifconfig up to enable the device, and ifconfig down disables those devices. You can see how that conflicts with this.

The next netcfg2 release has a QUIRKS=() option to opt-in to stupid workarounds for various driver issues. I'll add a quirk option for this one too...
Comment by James Rayner (iphitus) - Wednesday, 25 June 2008, 12:33 GMT
Ok, new netcfg2 is out with quirks array. Is this still an issue or do I still need to add a quirk?
Comment by Scott Cassidy (scottlc) - Monday, 30 June 2008, 12:48 GMT
I believe it is still an issue, so a quirk would be useful. I'm currently using my patched version. I'll do some more investigating and see if I can get it fixed upstream.

Loading...