On 2011-03-30 5:26 PM, Paweł Foremski wrote:
W dniu 30 marca 2011 15:05 użytkownik Felix Fietkau<n...@openwrt.org> napisał:
On 2011-03-30 9:10 AM, Paweł Foremski wrote:
2011/3/28 Felix Fietkau<n...@openwrt.org>:
On 2011-03-28 1:40 PM, Paweł Foremski wrote:
Last week ath9k updates broke adhoc. I'm running todays trunk on
RB433AH + RB52n. From
what I can see, beacons don't fly in adhoc. AP looks OK and
association is possible.
You're running AP and Ad-Hoc on one interface?
No, either adhoc or ap/sta as 1st vap and monitor as 2nd.
What kind of hardware? Does reproducing this require a second node or a
network of nodes? Or can this be reproduced by setting up a new unused
ad-hoc cell on one device?
Routerboard RB433AH with 3 x RB52n minipci cards.
I think the issue can be reproduced on 1 node, but second one is
needed to observe it. Exemplary two symptoms: 1) BSSIDs don't converge
2) tcpdump on monitor vap shows no beacons from other nodes. dmesg
doesn't show anything suspicious.
Should be fixed in r26395 (trunk), r26396 (backfire)
- Felix
_______________________________________________
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
