On Mon, Jan 28, 2013 at 04:44:39PM +0100, Mark Kettenis wrote: > When working on the WPA-Enterprise stuff, I actually ran into an issue > with the rsu(4) I was using. It seems there is a problem with > submitting the "join BSS" command when an RSN information element is > included, which makes the command never complete. The crucial bit > seems to be that this changes the length of the command to something > the firmware doesn't like. The code rounds the length up to the next > multiple of 8, but it seems the firmware wants it to be at least a > multiple of 16. The easiest fix seems to be to just send the entire > buffer that we allocate for the command. This will transfer more > bytes than strictly necessary, but this command isn't sent invoked > very often so I don't think this will be a problem. This diff might > fix issues with WPA-PSK as well. > > ok?
To a certain extent this seems to make rsu(3) work a little better, but now I am seeing ``rsu0: could not send join command'' messages which never happened before. The other issue I'm experiencing is when the driver does a scan either from the kernel doing so or from me issuing ifconfig scan will result in rsu_site_survey() failing (rsu0: could not send site survey command) after a few invocations of the function to issue the fw command. Over all though rsu(3) is still mainly unusable at least for the chipset in the adapter I am using; it is way too unreliable. I am using.. rsu0 at uhub0 port 2 "Manufacturer Realtek 11n USB Adapter" rev 2.00/2.00 addr 2 rsu0: MAC/BB RTL8712 cut 3, address 00:14:d1:6e:ac:6c -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean.
