Please note: This project is no longer active. The website is kept online for historic purposes only.
If you´re looking for a Linux driver for your Atheros WLAN device, you should continue here .

Ticket #1293 (new defect)

Opened 15 years ago

Last modified 13 years ago

Ubiquiti SRC will not associate to access points using WEP.

Reported by: nahuatl@member.fsf.org Assigned to:
Priority: major Milestone:
Component: madwifi: driver Version: trunk
Keywords: ubiquiti Cc:
Patch is attached: 0 Pending:

Description (Last modified by mrenzmann)

At first I had not thought it was able to connect to any AP at all, it was jumping around all channels, from 2.4X to 5.2X etc., however I figured out that setting the channel and the bitrate manually normalized connectivity, but when I tested it out on a WEP encrypted AP the channel would not manually set, here's my output from dmesg:

[   21.388000] ath_hal: module license 'Proprietary' taints kernel.
[   21.392000] ath_hal: 0.9.18.0 (AR5210, AR5211, AR5212, RF5111, RF5112, RF2413, RF5413)
[   21.540000] wlan: 0.8.4.2 (svn r2303)
[   21.584000] ath_pci: 0.9.4.5 (svn r2303)
[   21.584000] PCI: Enabling device 0000:03:00.0 (0000 -> 0002)
[   21.584000] ACPI: PCI Interrupt 0000:03:00.0[A] -> Link [LNKE] -> GSI 11 (level, low) -> IRQ 11
[   22.096000] ath_rate_sample: 1.2 (svn r2303)
[   22.096000] wifi0: 11a rates: 6Mbps 9Mbps 12Mbps 18Mbps 24Mbps 36Mbps 48Mbps 54Mbps
[   22.096000] wifi0: 11b rates: 1Mbps 2Mbps 5.5Mbps 11Mbps
[   22.096000] wifi0: 11g rates: 1Mbps 2Mbps 5.5Mbps 11Mbps 6Mbps 9Mbps 12Mbps 18Mbps 24Mbps 36Mbps 48Mbps 54Mbps
[   22.096000] wifi0: turboA rates: 6Mbps 9Mbps 12Mbps 18Mbps 24Mbps 36Mbps 48Mbps 54Mbps
[   22.096000] wifi0: turboG rates: 6Mbps 12Mbps 18Mbps 24Mbps 36Mbps 48Mbps 54Mbps
[   22.096000] wifi0: H/W encryption support: WEP AES AES_CCM TKIP
[   22.096000] wifi0: mac 5.9 phy 4.3 radio 3.6
[   22.096000] wifi0: Use hw queue 1 for WME_AC_BE traffic
[   22.096000] wifi0: Use hw queue 0 for WME_AC_BK traffic
[   22.096000] wifi0: Use hw queue 2 for WME_AC_VI traffic
[   22.096000] wifi0: Use hw queue 3 for WME_AC_VO traffic
[   22.096000] wifi0: Use hw queue 8 for CAB traffic
[   22.096000] wifi0: Use hw queue 9 for beacons
[   22.132000] wifi0: Atheros 5212: mem=0x58000000, irq=11

and when I try to set the channel to 11 on the wep encrypted AP:

[ 1322.852000] wifi0: ath_chan_set: unable to reset channel 11 (2462 MHz) flags 0xc0 '' (HAL status 3222406918)
[ 1323.764000] ACPI: PCI interrupt for device 0000:03:00.0 disabled
[ 1371.352000] pccard: CardBus card inserted into slot 0
[ 1371.352000] PCI: Enabling device 0000:03:00.0 (0000 -> 0002)
[ 1371.352000] ACPI: PCI Interrupt 0000:03:00.0[A] -> Link [LNKE] -> GSI 11 (level, low) -> IRQ 11
[ 1371.932000] wifi0: 11b rates: 1Mbps 2Mbps 5.5Mbps 11Mbps
[ 1371.932000] wifi0: 11g rates: 1Mbps 2Mbps 5.5Mbps 11Mbps 6Mbps 9Mbps 12Mbps 18Mbps 24Mbps 36Mbps 48Mbps 54Mbps
[ 1371.932000] wifi0: turboG rates: 6Mbps 12Mbps 18Mbps 24Mbps 36Mbps 48Mbps 54Mbps
[ 1371.932000] wifi0: H/W encryption support: WEP AES AES_CCM TKIP
[ 1371.932000] wifi0: mac 7.9 phy 4.5 radio 5.6
[ 1371.932000] wifi0: Use hw queue 1 for WME_AC_BE traffic
[ 1371.932000] wifi0: Use hw queue 0 for WME_AC_BK traffic
[ 1371.932000] wifi0: Use hw queue 2 for WME_AC_VI traffic
[ 1371.932000] wifi0: Use hw queue 3 for WME_AC_VO traffic
[ 1371.932000] wifi0: Use hw queue 8 for CAB traffic
[ 1371.932000] wifi0: Use hw queue 9 for beacons
[ 1371.932000] wifi0: Atheros 5212: mem=0x58000000, irq=11
[ 1382.504000] ath0: no IPv6 routers present

Change History

05/04/07 00:27:34 changed by nahuatl@member.fsf.org

oh, and because I forgot to mention it, I'm using Ubuntu Feisty Fawn, and the SVN drivers from a few days ago (I wasn't able to connect on the most recent stable release or the release in Feisty Fawn either)...also my Dlink WNA 223 works just fine, and it uses the madwifi drivers too.

(follow-up: ↓ 3 ) 05/07/07 16:34:30 changed by mrenzmann

  • description changed.

Is this issue fully reproducible on the Ubiquity card?

(in reply to: ↑ 2 ) 11/01/07 16:12:45 changed by anonymous

Replying to mrenzmann:

Is this issue fully reproducible on the Ubiquity card?

Yes it is, I have the same problem. The card kicks ass in windows using the Ubiquiti supplied driver, but in linux using the Madwifi driver, it is fine for use with kismet and the like, but for acturally trying to make a connection to a wireless point I find it almost impossible and only on the rarest of occassions can I connect to my own point which I have no problems connecting to from windows.