2d43d37ff2
Some applications require knowing about probe requests to identify devices. This can be the case in AP mode to see the devices before they connect, or even in P2P mode when operating as a P2P device to identify non-P2P peers (P2P peers are identified via PeerFound signals). As there are typically a lot of probe requests, require that an interested application subscribes to this signal so the bus isn't always flooded with these notifications. The notifications in DBus are then unicast only to that application. A small test script is also included. Signed-hostap: Johannes Berg <johannes.berg@intel.com> |
||
---|---|---|
.. | ||
60_wpa_supplicant | ||
dbus-listen-preq.py | ||
ieee8021x.conf | ||
openCryptoki.conf | ||
p2p-action-udhcp.sh | ||
p2p-action.sh | ||
plaintext.conf | ||
udhcpd-p2p.conf | ||
wep.conf | ||
wpa-psk-tkip.conf | ||
wpa2-eap-ccmp.conf | ||
wpas-dbus-new-getall.py | ||
wpas-dbus-new-signals.py | ||
wpas-dbus-new-wps.py | ||
wpas-dbus-new.py | ||
wpas-test.py | ||
wps-ap-cli |