Search Linux Wireless

Re: Mesh now completely broken on ath5k, latest git

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hu Andrey,

I'm using Netgear WG311TGE PCI cards, lspci says:

Atheros Communications Inc. AR5212/AR5213 Multiprotocol MAC/baseband
processor (rev 01)

There is only one bit to plug in an antenna, so I've only had one
plugged in, there isnt a place to plug in a second.  After the commit
in question I get no beaconing, before I get beaconing, but the PLINK
state keeps flipping between OPEN_SNT and LISTEN, implying that for
some reason it isnt receiving any PLINK packets.

That said, I havent tried directly after the PCU commit, so I will try
that now... but as I dont have an aux connector surely it shouldnt
effect me?

Cheers

Keir

2008/12/16 Andrey Yurovsky <andrey@xxxxxxxxxxx>:
> Hi Keir.  What type of Atheros-based card are you using?  How many
> antennas do you have connected?  If I understand things correctly, the
> PCU code regression (with respect to mesh and maybe AP and IBSS) has
> to do with having one antenna hooked up when your hardware also has an
> AUX antenna connector.  If you have only one antenna, can you please
> plug in a second one and try again (before and after the commit in
> question)?  I will try to do the same test here.  More details from
> Nick were posted here:
> http://marc.info/?l=linux-wireless&m=122771338021489&w=2
>
> On Tue, Dec 16, 2008 at 8:07 AM, Keir <keirlawson@xxxxxxxxx> wrote:
>> I've been working on the commit previous to the PCU code breakage
>> (8485b7f773a8e9883e0165273940f16a086eba2b), but I'm still having
>> problems (beaconing is working, but links are rarely established, most
>> of the time to packets get through).
>>
>> Cheers
>>
>> Keir
>>
>> 2008/12/16 Steve Brown <sbrown@xxxxxxxxxxxx>:
>>> Keir wrote:
>>>>
>>>> Having has no luck with an old rc6 version (basically all plink
>>>> packets were getting lost), I upgraded to the newest git (rc8) however
>>>> now when I run iw dev mesh0 station sump I don't see a single other
>>>> mesh point.  This would imply that presumably beaconing is broken?
>>>>
>>>> Does anyone know a revision for which ath5k is properly working? I am
>>>> yet to find one that works on my system.
>>>>
>>>> Cheers
>>>>
>>>> Keir
>>>> --
>>>> To unsubscribe from this list: send the line "unsubscribe linux-wireless"
>>>> in
>>>> the body of a message to majordomo@xxxxxxxxxxxxxxx
>>>> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>>>>
>>>
>>> Beaconing seems broken by Update PCU code
>>> dd1c9abd167de9bb9457a57694a1ab5e5801a0c1. After this patch, beacon debug
>>> says beacons sent, but sniffer sees none.
>>>
>>> A snapshot of ath5k prior to this and git 12/10
>>> (b6d06c9669f27db31a0317fc98fedc8ff1ba4822) works for me with hostapd/wpa.
>>> It's been running for the past few days.
>>>
>>> Mesh beaconing also works. I didn't test two nodes; I only sniffed the
>>> beacons.
>>>
>>> I had to comment out 5GHz in caps.c because of too many channels. It's a
>>> nl80211 buffer size problem that's been discussed.
>>>
>>> Steve
>>>
>>>
>>>
>>
>
>
>
> --
> Andrey Yurovsky
> cozybit Inc.
>
--
To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [Linux Host AP]     [ATH6KL]     [Linux Bluetooth]     [Linux Netdev]     [Kernel Newbies]     [Linux Kernel]     [IDE]     [Security]     [Git]     [Netfilter]     [Bugtraq]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux ATA RAID]     [Samba]     [Device Mapper]
  Powered by Linux