On Mon, Dec 05, 2022 at 04:43:36PM +0200, Andrei Otcheretianski wrote: > When configuring FTM responder, wpa_supplicant/hostapd configures the > driver to operate as a responder. However, it is possible that it is > only needed to advertise the FTM responder capabilties, but not > configure the driver to operate as a responder (e.g. when a usespace > daemon operates as a responder). Add an option to only advertise the > FTM responder capabilities without configuring the driver. How would a user know when to use the new ftm_responder_capab_only vs. the old ftm_responder_capab configuration parameter? What happens if ftp_responder_capab_only=1 is used and there is no userspace daemon to process the operations? Is this something that could be handled automatically? It would seem to be much more convenient to not add this new configuration parameter at all and instead determine the FTM responder location between the driver and that separate userspace daemon automatically so that it does not matter whether hostapd/wpa_supplicant requests the driver to process the requests. -- Jouni Malinen PGP id EFC895FA _______________________________________________ Hostap mailing list Hostap@xxxxxxxxxxxxxxxxxxx http://lists.infradead.org/mailman/listinfo/hostap
