Hi Bas, > don't mean to push you or anything, but I was wondering if you > overlooked my last mail. You asked me to add some printk's to the > rt2500pci driver to debug hostapd authentication failure. I did this, > and these are the results: Sorry. I'm sure I read it but I must have forgotten, thanks for the note. > rt2500pci MAC changed: 00:0c:f6:14:05:19 > rt2500pci filter_flags: 2 > rt2500pci MAC changed: 00:00:00:00:00:00 > rt2500pci MAC changed: 00:0c:f6:14:05:19 > rt2500pci MAC changed: 00:00:00:00:00:00 > rt2500pci MAC changed: 00:0c:f6:14:05:19 > rt2500pci filter_flags: 2 > rt2500pci filter_flags: 0 > rt2500pci MAC changed: 00:00:00:00:00:00 > rt2500pci MAC changed: 00:0c:f6:14:05:19 > rt2500pci filter_flags: 2 > ------------------------------------------------ > this is immediately on startup of hostapd, after that filter and MAC > remain unchanged (at least if my printk catches everything). That looks pretty much expected. > does this look ok to you? Does it explain why I can only receive EOPOL > keys when in promiscuous mode? Unfortunately not, it's a bit weird. I think I'll probably have to run it myself to figure it out and do captures on the various interfaces. johannes
Attachment:
signature.asc
Description: This is a digitally signed message part
