On 2013-09-10 5:48 PM, Ben Greear wrote: > On 09/10/2013 01:10 AM, Sujith Manoharan wrote: >> Ben Greear wrote: >>> I had a user request that we support always sending management frames >>> (such as EAPOL) at the lowest rate. Evidently, other equipment does this, >>> where as normal-ish supplicant/linux tends to send them at much higher >>> rates. >>> >>> Any suggestions on how to go about doing this properly? >> >> If this is with ath9k_rate_control, then it is a known bug: >> https://bugzilla.redhat.com/show_bug.cgi?id=927191 > > I'm not using ath9k rate control in this case, and at least most messages > get through fine. We didn't actually see any obvious improvement when forcing > everything to 6Mbps, but since my user was asking, I wanted to run the > idea past the list. > > Rate control is not perfect, and on initial bringup it doesn't have > many packets to work with so I thought it might still be useful to allow > users to specify a particular rate for EAPOL packets. Maybe using > a socket ioctl so user-space (ie, supplicant/hostapd) can control it, > for example. minstrel and minstrel_ht always keep low rates in the rate retry chain until enough higher rates have been proven to work. I think adding an interface that allows user space to mess with the rate selection of EAPOL packets is a bad idea - users will pretty much always make worse rate decisions than the rate control module. - Felix -- 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
