"Sepherosa Ziehau" <[EMAIL PROTECTED]> 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 -- Dag-Erling Smørgrav - [EMAIL PROTECTED] _______________________________________________ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "[EMAIL PROTECTED]"
