gbur at informatik.uni-rostock.de
Wed Jan 21 05:27:55 EST 2004
> handle_ap_item - addr1(DA)=ff:ff:ff:ff:ff:ff not own MAC
> Whis is sometimes repeated many times in a short period, and other times
> This problem is increasing in frequency and sometimes the mac
> address is different.
This is not a problem. Your AP gut a managment frame with is not for
the AP. Thats all.
> In conjunction with this, there is an occasional
> problem which I think is related where hostap will disassociate all
> clients and not allow any new reassociations, for no obvious reason or
> cause. When this happens, the AP is still running and I can ssh in and
> have a look around, and the second AP in the box is still going (the
> second pcmcia card still has clients and is still working), there just
> areen't any clients associated any more on the first AP. I have to reboot
> the box at that point and then everything is fine again. This happened on
> an AP with 33 clients and all the syslogging I do doesn't reveal anything
> obvious, no flood of kernel messages, no nothing... just all of a sudden, where there
> were 33 clients there are zero.
I have the same problem with the hostapd. It seams that the hostapd got
a SIGKILL. But i don't know why. Not enough memory is not the problem.
Did you use the hostap deamon (hostapd) or only the kernel-module?
More information about the HostAP