Date: Tue, 7 May 2013 19:53:22 -0700 From: Adrian Chadd <adrian@freebsd.org> To: lev@freebsd.org Cc: freebsd-wireless@freebsd.org Subject: Re: New hardware, old problem: stuck beacon when here is WiFi traffic Message-ID: <CAJ-Vmok6fFB=Tb%2BJyGfAGJMLUzJ93LN_v==TJsRv--5bWU8YGg@mail.gmail.com> In-Reply-To: <CAJ-VmomOywCicVHP8aLKXhdysad48K7bc-wRudaPYmcuQLcKYA@mail.gmail.com> References: <2810538978.20130423164137@serebryakov.spb.ru> <CAJ-Vmom4UDoz7EgdnVeQ%2BALuFFXkH9t_Uj7=FwL77S5rKfUD1g@mail.gmail.com> <1813905823.20130423184528@serebryakov.spb.ru> <CAJ-VmomhRaKODxis09MjAhUbAUOw%2B6jWBY48JpZR_JgfZZLKcQ@mail.gmail.com> <184105677.20130424002002@serebryakov.spb.ru> <CAJ-VmokVmHDXwE7S5koSqtFjPXQ_VUPhj8gfMruDM2k-DyUMPw@mail.gmail.com> <1936997795.20130424003555@serebryakov.spb.ru> <CAJ-Vmokx2QhcjcsgA-_kqjX63Vu4CLk7HkuyALautbnzp61ywQ@mail.gmail.com> <886711115.20130424004702@serebryakov.spb.ru> <CAJ-VmoksSTBC7jmC-_hvBeJFSD0k28HoZodaWdHm0AF0d1yZJg@mail.gmail.com> <6010292503.20130426001447@serebryakov.spb.ru> <CAJ-VmomUsPgHTVGaKHZ_YE%2Bu1ZOjGqrVfh2uYmvOs6gKmhnxOw@mail.gmail.com> <CAJ-VmokZBbmHbruKJV-8kvTyOTsiq5_XHnfqUYo3vO68872Q=w@mail.gmail.com> <99510815.20130426122508@serebryakov.spb.ru> <CAJ-VmoktRPbnDRbRuwA4i8w50kExs2pwD4yBawL6iOz7F4Bknw@mail.gmail.com> <CAJ-VmonCao99MOrm97tQS_f1xS9tieQfg-nQUB4APWVmdJJUBg@mail.gmail.com> <187241224.20130429113623@serebryakov.spb.ru> <CAJ-Vmo=MzeJsKHfVoipPQqCRmkOHWk6p-iZNaXDwye6oG%2B76xg@mail.gmail.com> <CAJ-Vmo=b-kBDWKz=Y709kYEsYQt3ZRczCN0wG9zDRk=sR60%2Btg@mail.gmail.com> <124956607.20130430122459@serebryakov.spb.ru> <CAJ-VmonQXyB_Aik-ApSmgRqT3yhD5Bqrx3zj%2BKM%2BitVmZhY0TQ@mail.gmail.com> <146903383.20130501000714@serebryakov.spb.ru> <CAJ-Vmo=n27vAzsEPDwaO%2BjxS-n42WBbiNyfpvmnO931q1CKcDA@mail.gmail.com> <94204652.20130501133220@serebryakov.spb.ru> <CAJ-VmonvS_=_vgJufRc-5d4NGfkKtpsUEZh%2BTaE_Th-dEj2W9A@mail.gmail.com> <CAJ-Vmo=fFEkRr4-R3g1%2B%2BMq7QoTGD_OFWpHc5jpgbwEcgrOJYQ@mail.gmail.com> <CAJ-Vmont9febEE9jOX8ZMp7omMdQ_4wDNRr5gyq8gbpm3x18KQ@mail.gmail.com> <CAJ-Vmon0dj%2Bg1ZE28whsvtP%2BshUwoMa-E_XnQu6uFy8cSCUuZg@mail.gmail.com> <94971208.20130503122811@serebryakov.spb.ru> <CAJ-VmonPyg6a5ZidA9vZzozVGFc0XHT2MoX3OfhCBrqMxVn7cw@mail.gmail.com> <CAJ-VmomOywCicVHP8aLKXhdysad48K7bc-wRudaPYmcuQLcKYA@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi Lev (and others); I've fixed the UDP TX + rekey session drop bug. Please re-test your testcase on the latest -HEAD and let me know how it goes. I'd really like to sneak in these power save and reassociate changes of mine, but first I want to make sure that your issue is correctly resolved. Thanks! Adrian On 3 May 2013 22:09, Adrian Chadd <adrian@freebsd.org> wrote: > Hi, > > So doing this testing as a station doing the UDP transmitting (to a > FreeBSD AP) is showing some interesting behaviour. No, i don't think > it's your bug. > > The key re-negotiation seems to be failing somewhere; I bet it's out > of sequence or out of order crypto frames. I've seen this happen > before but I only fixed it for the AP case (by overriding the QOS for > said frames so it appeared in a different TID, thus different sequence > number space.) Since it's reauthing, it's transitioning the node > through disassociate / re-auth / re-associate, but the current code in > -HEAD isn't resetting the local state (aggregation, BAR state, > filtered frames state, etc.) So things can and do go weird. > > I'll do some further digging into this and see if I can resolve it. I > thought I had fixed it but .. well, obviously not. Once I have > resolved this rekey / disconnect issue I'll keep testing things out > and see if I've fixed your issue. > > (And I'll do some testing in parallel in open mode, so I don't bite this bug.) > > > > adrian
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAJ-Vmok6fFB=Tb%2BJyGfAGJMLUzJ93LN_v==TJsRv--5bWU8YGg>