Date: Sat, 05 Jan 2008 15:19:43 +0100 From: =?utf-8?Q?Dag-Erling_Sm=C3=B8rgrav?= <des@des.no> To: "Sepherosa Ziehau" <sepherosa@gmail.com> Cc: kevlo@freebsd.org, sam@freebsd.org, current@freebsd.org, net@freebsd.org Subject: Re: if_ral regression Message-ID: <864pds8idc.fsf@ds4.des.no> In-Reply-To: <ea7b9c170801040620l1e1c27a1t30a875b32dc0f01c@mail.gmail.com> (Sepherosa Ziehau's message of "Fri\, 4 Jan 2008 22\:20\:48 %2B0800") References: <86ir2hznnd.fsf@ds4.des.no> <ea7b9c170712312227m7a961c95kc2bed20f94d09593@mail.gmail.com> <86abnpu0wv.fsf@ds4.des.no> <ea7b9c170801020518m6d5f8fdejd01947166669e9e4@mail.gmail.com> <86abnovy4k.fsf@ds4.des.no> <86odc3dlgi.fsf@ds4.des.no> <ea7b9c170801031824n2205c1e8i2f010df67a07dfff@mail.gmail.com> <86lk76c6t5.fsf@ds4.des.no> <ea7b9c170801040620l1e1c27a1t30a875b32dc0f01c@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
"Sepherosa Ziehau" <sepherosa@gmail.com> writes: > This actually brings up two things: > 1) I think we should ignore seq in multicast frames; this is permitted in > 802.11 standard. In dfly I did that, since one of our users > encountered a broken commercial AP which is not 802.11e but uses > different seq for data and beacon. > 2) TX sequence. I think standards only mention QSTA/nQSTA, but not > AP. Currently our AP uses per node TX seq, which means beacon's seq > is difficult to choose, at least for 2560 based ral(4), whose beacons' > seq need to be set by software. I saw Linksys AP uses one seq for all > of the frames it sends. Sam, what's you opinion on this? > > I think if STA counts ral(4)'s beacon seq, as what we do currently, > beacon missing will quickly happen since beacons will be discarded > after first several data frames. OK, I *think* I understood most of that. Does this suggest a solution to you? I will try to get the wlandebug output tonight. DES --=20 Dag-Erling Sm=C3=B8rgrav - des@des.no
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?864pds8idc.fsf>