Thanks for the info, Fred. I'll take a look at this towards the end of today.
On Fri, Oct 12, 2012 at 12:18 PM, fred veldini <[email protected]> wrote: > This issue shows up after 3+ peers. > > We tested up to 6 peers and had the same results but more nodes were in > LISTEN state, might be 3 might be 4 never the same or consistent on which > nodes are ESTAB. > > We have tried booting the systems up in different sequences and times to > narrow down a timing issue. But that didn't make a difference. Once the > routers all talk to each other with AUTHSAE they randomly got to LISTEN > mode. > > > > > > > > On Fri, Oct 12, 2012 at 3:08 PM, Thomas Pedersen <[email protected]> wrote: >> >> > Sorry it's still not really clear: everyone else has LISTEN towards >> > 00:15:6d:65:4f:76, or 00:15:6d:65:4f:76 can't communicate with >> > everyone else? >> > >> > Can you please post a full authsae debug output from on of the routers >> > showing LISTEN towards a peer and the ath5k warning? Please mention >> > which mac address is in LISTEN as well >> >> Also, it would be useful if you could determine the number of peers >> needed to trigger this warning. >> >> Thomas >> >> _______________________________________________ >> Devel mailing list >> [email protected] >> http://lists.open80211s.org/cgi-bin/mailman/listinfo/devel > > > > _______________________________________________ > Devel mailing list > [email protected] > http://lists.open80211s.org/cgi-bin/mailman/listinfo/devel > _______________________________________________ Devel mailing list [email protected] http://lists.open80211s.org/cgi-bin/mailman/listinfo/devel
