Am Samstag, 30. Juli 2011, 22:03:34 schrieb Andreas Hartmann: > Jouni Malinen schrieb: > > On Fri, Jul 29, 2011 at 07:22:17PM +0200, Helmut Schaa wrote: > >> Since EAPOL frames are normal data frames they are treated by the > >> rate control algorithm as such. Thus it can happen that the rate > >> control algorithm chooses an inappropriate rate (minstrel_ht uses > >> MCS rates for example) for the 4-way handshake and under low signal > >> conditions the handshake may time out. > >> > >> To fix this issue always treat EAPOL frames the same as management > >> frames and send them with the lowest available rate. > > > > I don't think that this should be applied for the reasons given (and > > alternative mechanisms proposed) in the discussion. > > I tested it with AP (rt2860) (with STA rt3572sta) under load and > couldn't see any improvement. Because the patch never intended to tackle the problem you've reported :) However, I've got some reports of clients timing out during the 4-way handshake if they are "far" away from the AP while auth and assoc work just fine. Helmut -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
