Hello Michael, On 6/18/2006, "Michael Buesch" <[EMAIL PROTECTED]> wrote:
>Ok, I got my Airport to generate Beacons on this BE machine. > >There was a bug hiding in bcm43xx_ram_write(). Current in-tree buggy >ram_write() expects swapped input value. So on a LE system it takes >a BE value and on a BE system it takes a LE value. Aha, this seems to explain why I had to put swab32 in ram_write calls ... >After fixing that so that ram_write() takes input in CPU order >(as it should be) and after fixing some other endianess bugs in the >patch, it generates beacons correctly. Please compare your fixes with the patch I posted earlier for BE fixes (14.06.2006, my mail to Francois) and also compare the dump of your templates with those I posted in previous mails to Francois - it's just that if there are still some endianess problems in the body generation of either beacon or probe response templates, it can result in incorrect behavior, even though there would be no IRQ_XMIT_ERROR messages. >But I can not associate to the bcm43xx-AP. >But it seems like a dscape problem. The authentication packet >arrives at the machine (I can capture it with the new cool virtual >monitor interface), but it is not processed. So the STA does >not receive a response. > >Do you see similiar behaviour? I think the only similar case during my debugging was when hostapd has generated probe responses together with the hardware, thus they were interferring with each other preventing STA from correct operation, but if you use the patched version of hostapd and have "send_probe_response=0" in your config, this should not be the case ... As far as I know, it should be the hostapd who proceeds auth packets - so, I'd suggest examining its debug output (probably also add some debug output close to auth packet handling) to see what the problem could be. Or do you mean that those auth packets are dropped by dscape and do not reach hostapd at all? Good luck! Alexander _______________________________________________ Bcm43xx-dev mailing list [email protected] http://lists.berlios.de/mailman/listinfo/bcm43xx-dev
