Hello, I’m trying to set up a consistent test environment for experimentation. One thing that I am trying to implement is a fixed beacon size, regardless of the adapter and driver. My first attempt: I added an additional config option in hostapd.conf which adds N number of bytes to the beacon in `ieee802_11_set_beacon`. But as you all know, that new structure is simply added to whatever the driver builds by calling the driver’s set_ap call. (I use the extended IE tag 0xff and then a reserved secondary identifier to avoid confusing the station.) I use this new config option by opening WireShark to determine the “native” beacon size, and then adjust the config parameter for each new adapter. Tedious? Yes. Especially for each new adaptor. I would like to have N be the size of the final beacon, rather than the number of extra bytes added to the existing beacon. There doesn’t appear to be driver-to-hostapd communication (or query) to determine the driver’s additions to the final beacon, as far as I can tell. What would the group suggest as a way to solve this? Thanks, Peter
Attachment:
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ Hostap mailing list Hostap@xxxxxxxxxxxxxxxxxxx http://lists.infradead.org/mailman/listinfo/hostap
