disassociate frames

[Greg M. Hochstrasser]

Jouni:

Thanks for the quick response.  Your answer in reference to firmware 
controlling
a client in HostAP makes sense.   I have been using prism2/2.5 cards 
for a while now.
Maybe it's time I switched over to the Atheros (madwifi) cards.  I did 
a quick
proof of concept with a Proxim a/b/g card and madwifi to work with 
Kismet; but didn't think about
making it the stable card for HostAP, because I have not seen  any 
Atheros cards with external
antenna connectors (R-MMCX).

Appreciate the response and help here.

gmh

On Sep 14, 2004, at 10:49 PM, Jouni Malinen wrote:

On Tue, Sep 14, 2004 at 01:27:15PM -0500, Greg Hochstrasser wrote:

> Can anyone tell me how to set hostap to ignore
> "disassociate frames" being generated by the WIDS to kick
> me off the network?

Are you using Host AP driver as the access point or as the client? In
case of Host AP as the AP, you will just need to modify handle_deauth()
and handle_disassoc() functions to ignore packets. In case of client
mode, you are likely out of luck with Prism2/2.5/3 cards and their
current firmware.. In other words, it is the firmware that takes care of
the client side operations (auth/assoc/deauth/disassoc). You could use
another card with these functions implemented in the driver, e.g.,
Atheros-based cards for this.

> Trying to learn how to overcome the WIDS and the frames it
> is generating to protect the trusted section of the WLAN.

That sounds like useless "protection" to me if WIDS is sending those
frames over air to client or AP.

-- 
Jouni Malinen                                            PGP id EFC895FA
_______________________________________________
HostAP mailing list
HostAP at shmoo.com
http://lists.shmoo.com/mailman/listinfo/hostap