README-P2P 33 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235236237238239240241242243244245246247248249250251252253254255256257258259260261262263264265266267268269270271272273274275276277278279280281282283284285286287288289290291292293294295296297298299300301302303304305306307308309310311312313314315316317318319320321322323324325326327328329330331332333334335336337338339340341342343344345346347348349350351352353354355356357358359360361362363364365366367368369370371372373374375376377378379380381382383384385386387388389390391392393394395396397398399400401402403404405406407408409410411412413414415416417418419420421422423424425426427428429430431432433434435436437438439440441442443444445446447448449450451452453454455456457458459460461462463464465466467468469470471472473474475476477478479480481482483484485486487488489490491492493494495496497498499500501502503504505506507508509510511512513514515516517518519520521522523524525526527528529530531532533534535536537538539540541542543544545546547548549550551552553554555556557558559560561562563564565566567568569570571572573574575576577578579580581582583584585586587588589590591592593594595596597598599600601602603604605606607608609610611612613614615616617618619620621622623624625626627628629630631632633634635636637638639640641642643644645646647648649650651652653654655656657658659660661662663664665666667668669670671672673674675676677678679680681682683684685686687688689690691692693694695696697698699700701702703704705706707708709710711712713714715716717718719720721722723724725726727728729730731732733734735736737738739740741742743744745746747748749750751752753754755756757758759760761762763764765766767768769770771772773774775776777778779780781782783784785786787788789790791792793794795796797798799800801802803804805806807808809810811812813814815816817818819820821822823824825826827828829830831832833834835836837838839840841842843844845846847848849850851852853854855856
  1. wpa_supplicant and Wi-Fi P2P
  2. ============================
  3. This document describes how the Wi-Fi P2P implementation in
  4. wpa_supplicant can be configured and how an external component on the
  5. client (e.g., management GUI) is used to enable WPS enrollment and
  6. registrar registration.
  7. Introduction to Wi-Fi P2P
  8. -------------------------
  9. TODO
  10. More information about Wi-Fi P2P is available from Wi-Fi Alliance:
  11. http://www.wi-fi.org/Wi-Fi_Direct.php
  12. wpa_supplicant implementation
  13. -----------------------------
  14. TODO
  15. wpa_supplicant configuration
  16. ----------------------------
  17. Wi-Fi P2P is an optional component that needs to be enabled in the
  18. wpa_supplicant build configuration (.config). Here is an example
  19. configuration that includes Wi-Fi P2P support and Linux nl80211
  20. -based driver interface:
  21. CONFIG_DRIVER_NL80211=y
  22. CONFIG_CTRL_IFACE=y
  23. CONFIG_P2P=y
  24. CONFIG_AP=y
  25. CONFIG_WPS=y
  26. In run-time configuration file (wpa_supplicant.conf), some parameters
  27. for P2P may be set. In order to make the devices easier to recognize,
  28. device_name and device_type should be specified. For example,
  29. something like this should be included:
  30. ctrl_interface=/var/run/wpa_supplicant
  31. device_name=My P2P Device
  32. device_type=1-0050F204-1
  33. wpa_cli
  34. -------
  35. Actual Wi-Fi P2P operations are requested during runtime. These can be
  36. done for example using wpa_cli (which is described below) or a GUI
  37. like wpa_gui-qt4.
  38. wpa_cli starts in interactive mode if no command string is included on
  39. the command line. By default, it will select the first network interface
  40. that it can find (and that wpa_supplicant controls). If more than one
  41. interface is in use, it may be necessary to select one of the explicitly
  42. by adding -i argument on the command line (e.g., 'wpa_cli -i wlan1').
  43. Most of the P2P operations are done on the main interface (e.g., the
  44. interface that is automatically added when the driver is loaded, e.g.,
  45. wlan0). When using a separate virtual interface for group operations
  46. (e.g., wlan1), the control interface for that group interface may need
  47. to be used for some operations (mainly WPS activation in GO). This may
  48. change in the future so that all the needed operations could be done
  49. over the main control interface.
  50. Device Discovery
  51. p2p_find [timeout in seconds] [type=<social|progressive>] \
  52. [dev_id=<addr>] [dev_type=<device type>] \
  53. [delay=<search delay in ms>] [seek=<service name>] [freq=<MHz>]
  54. The default behavior is to run a single full scan in the beginning and
  55. then scan only social channels. type=social will scan only social
  56. channels, i.e., it skips the initial full scan. type=progressive is
  57. like the default behavior, but it will scan through all the channels
  58. progressively one channel at the time in the Search state rounds. This
  59. will help in finding new groups or groups missed during the initial
  60. full scan. When the type parameter is not included (i.e., full scan), the
  61. optional freq parameter can be used to override the first scan to use only
  62. the specified channel after which only social channels are scanned.
  63. The optional dev_id option can be used to specify a single P2P peer to
  64. search for. The optional delay parameter can be used to request an extra
  65. delay to be used between search iterations (e.g., to free up radio
  66. resources for concurrent operations).
  67. The optional dev_type option can be used to specify a single device type
  68. (primary or secondary) to search for, e.g.,
  69. "p2p_find dev_type=1-0050F204-1".
  70. With one or more seek arguments, the command sends Probe Request frames
  71. for a P2PS service. For example,
  72. p2p_find 5 dev_id=11:22:33:44:55:66 seek=alt.example.chat seek=alt.example.video
  73. Parameters description:
  74. Timeout - Optional ASCII base-10-encoded u16. If missing, request will not
  75. time out and must be canceled manually
  76. dev_id - Optional to request responses from a single known remote device
  77. Service Name - Mandatory UTF-8 string for ASP seeks
  78. Service name must match the remote service being advertised exactly
  79. (no prefix matching).
  80. Service name may be empty, in which case all ASP services will be
  81. returned, and may be filtered with p2p_serv_disc_req settings, and
  82. p2p_serv_asp_resp results.
  83. Multiple service names may be requested, but if it exceeds internal
  84. limit, it will automatically revert to requesting all ASP services.
  85. p2p_listen [timeout in seconds]
  86. Start Listen-only state (become discoverable without searching for
  87. other devices). Optional parameter can be used to specify the duration
  88. for the Listen operation in seconds. This command may not be of that
  89. much use during normal operations and is mainly designed for
  90. testing. It can also be used to keep the device discoverable without
  91. having to maintain a group.
  92. p2p_stop_find
  93. Stop ongoing P2P device discovery or other operation (connect, listen
  94. mode).
  95. p2p_flush
  96. Flush P2P peer table and state.
  97. Group Formation
  98. p2p_prov_disc <peer device address> <display|keypad|pbc> [join|auto]
  99. Send P2P provision discovery request to the specified peer. The
  100. parameters for this command are the P2P device address of the peer and
  101. the desired configuration method. For example, "p2p_prov_disc
  102. 02:01:02:03:04:05 display" would request the peer to display a PIN for
  103. us and "p2p_prov_disc 02:01:02:03:04:05 keypad" would request the peer
  104. to enter a PIN that we display.
  105. The optional "join" parameter can be used to indicate that this command
  106. is requesting an already running GO to prepare for a new client. This is
  107. mainly used with "display" to request it to display a PIN. The "auto"
  108. parameter can be used to request wpa_supplicant to automatically figure
  109. out whether the peer device is operating as a GO and if so, use
  110. join-a-group style PD instead of GO Negotiation style PD.
  111. p2p_connect <peer device address> <pbc|pin|PIN#|p2ps> [display|keypad|p2ps]
  112. [persistent|persistent=<network id>] [join|auth]
  113. [go_intent=<0..15>] [freq=<in MHz>] [ht40] [vht] [provdisc] [auto]
  114. [ssid=<hexdump>]
  115. Start P2P group formation with a discovered P2P peer. This includes
  116. optional group owner negotiation, group interface setup, provisioning,
  117. and establishing data connection.
  118. The <pbc|pin|PIN#> parameter specifies the WPS provisioning
  119. method. "pbc" string starts pushbutton method, "pin" string start PIN
  120. method using an automatically generated PIN (which will be returned as
  121. the command return code), PIN# means that a pre-selected PIN can be
  122. used (e.g., 12345670). [display|keypad] is used with PIN method
  123. to specify which PIN is used (display=dynamically generated random PIN
  124. from local display, keypad=PIN entered from peer display). "persistent"
  125. parameter can be used to request a persistent group to be formed. The
  126. "persistent=<network id>" alternative can be used to pre-populate
  127. SSID/passphrase configuration based on a previously used persistent
  128. group where this device was the GO. The previously used parameters will
  129. then be used if the local end becomes the GO in GO Negotiation (which
  130. can be forced with go_intent=15).
  131. "join" indicates that this is a command to join an existing group as a
  132. client. It skips the GO Negotiation part. This will send a Provision
  133. Discovery Request message to the target GO before associating for WPS
  134. provisioning.
  135. "auth" indicates that the WPS parameters are authorized for the peer
  136. device without actually starting GO Negotiation (i.e., the peer is
  137. expected to initiate GO Negotiation). This is mainly for testing
  138. purposes.
  139. "go_intent" can be used to override the default GO Intent for this GO
  140. Negotiation.
  141. "freq" can be used to set a forced operating channel (e.g., freq=2412
  142. to select 2.4 GHz channel 1).
  143. "provdisc" can be used to request a Provision Discovery exchange to be
  144. used prior to starting GO Negotiation as a workaround with some deployed
  145. P2P implementations that require this to allow the user to accept the
  146. connection.
  147. "auto" can be used to request wpa_supplicant to automatically figure
  148. out whether the peer device is operating as a GO and if so, use
  149. join-a-group operation rather than GO Negotiation.
  150. "ssid=<hexdump>" can be used to specify the Group SSID for join
  151. operations. This allows the P2P Client interface to filter scan results
  152. based on SSID to avoid selecting an incorrect BSS entry in case the same
  153. P2P Device or Interface address have been used in multiple groups
  154. recently.
  155. P2PS attribute changes to p2p_connect command:
  156. P2PS supports two WPS provisioning methods namely PIN method and P2PS default.
  157. The remaining parameters hold same role as in legacy P2P. In case of P2PS
  158. default config method "p2ps" keyword is added in p2p_connect command.
  159. For example:
  160. p2p_connect 02:0a:f5:85:11:00 12345670 p2ps persistent join
  161. (WPS Method = P2PS default)
  162. p2p_connect 02:0a:f5:85:11:00 45629034 keypad persistent
  163. (WPS Method = PIN)
  164. p2p_asp_provision <peer MAC address> <adv_id=peer adv id>
  165. <adv_mac=peer MAC address> [role=2|4|1] <session=session id>
  166. <session_mac=initiator mac address>
  167. [info='service info'] <method=Default|keypad|Display>
  168. This command starts provision discovery with the P2PS enabled peer device.
  169. For example,
  170. p2p_asp_provision 00:11:22:33:44:55 adv_id=4d6fc7 adv_mac=00:55:44:33:22:11 role=1 session=12ab34 session_mac=00:11:22:33:44:55 info='name=john' method=1000
  171. Parameter description:
  172. MAC address - Mandatory
  173. adv_id - Mandatory remote Advertising ID of service connection is being
  174. established for
  175. adv_mac - Mandatory MAC address that owns/registered the service
  176. role - Optional
  177. 2 (group client only) or 4 (group owner only)
  178. if not present (or 1) role is negotiated by the two peers.
  179. session - Mandatory Session ID of the first session to be established
  180. session_mac - Mandatory MAC address that owns/initiated the session
  181. method - Optional method to request for provisioning (1000 - P2PS Default,
  182. 100 - Keypad(PIN), 8 - Display(PIN))
  183. info - Optional UTF-8 string. Hint for service to indicate possible usage
  184. parameters - Escape single quote & backslash:
  185. with a backslash 0x27 == ' == \', and 0x5c == \ == \\
  186. p2p_asp_provision_resp <peer mac address> <adv_id= local adv id>
  187. <adv_mac=local MAC address> <role=1|2|4> <status=0>
  188. <session=session id> <session_mac=peer MAC address>
  189. This command sends a provision discovery response from responder side.
  190. For example,
  191. p2p_asp_provision_resp 00:55:44:33:22:11 adv_id=4d6fc7 adv_mac=00:55:44:33:22:11 role=1 status=0 session=12ab34 session_mac=00:11:22:33:44:55
  192. Parameters definition:
  193. MAC address - Mandatory
  194. adv_id - Mandatory local Advertising ID of service connection is being
  195. established for
  196. adv_mac - Mandatory MAC address that owns/registered the service
  197. role - Optional 2 (group client only) or 4 (group owner only)
  198. if not present (or 1) role is negotiated by the two peers.
  199. status - Mandatory Acceptance/Rejection code of Provisioning
  200. session - Mandatory Session ID of the first session to be established
  201. session_mac - Mandatory MAC address that owns/initiated the session
  202. p2p_group_add [persistent|persistent=<network id>] [freq=<freq in MHz>]
  203. [ht40] [vht]
  204. Set up a P2P group owner manually (i.e., without group owner
  205. negotiation with a specific peer). This is also known as autonomous
  206. GO. Optional persistent=<network id> can be used to specify restart of
  207. a persistent group. Optional freq=<freq in MHz> can be used to force
  208. the GO to be started on a specific frequency. Special freq=2 or freq=5
  209. options can be used to request the best 2.4 GHz or 5 GHz band channel
  210. to be selected automatically.
  211. p2p_reject <peer device address>
  212. Reject connection attempt from a peer (specified with a device
  213. address). This is a mechanism to reject a pending GO Negotiation with
  214. a peer and request to automatically block any further connection or
  215. discovery of the peer.
  216. p2p_group_remove <group interface>
  217. Terminate a P2P group. If a new virtual network interface was used for
  218. the group, it will also be removed. The network interface name of the
  219. group interface is used as a parameter for this command.
  220. p2p_cancel
  221. Cancel an ongoing P2P group formation and joining-a-group related
  222. operation. This operation unauthorizes the specific peer device (if any
  223. had been authorized to start group formation), stops P2P find (if in
  224. progress), stops pending operations for join-a-group, and removes the
  225. P2P group interface (if one was used) that is in the WPS provisioning
  226. step. If the WPS provisioning step has been completed, the group is not
  227. terminated.
  228. p2p_remove_client <peer's P2P Device Address|iface=<interface address>>
  229. This command can be used to remove the specified client from all groups
  230. (operating and persistent) from the local GO. Note that the peer device
  231. can rejoin the group if it is in possession of a valid key. See p2p_set
  232. per_sta_psk command below for more details on how the peer can be
  233. removed securely.
  234. Service Discovery
  235. p2p_service_add asp <auto accept> <adv id> <status 0/1> <Config Methods>
  236. <Service name> [Service Information] [Response Info]
  237. This command can be used to search for a P2PS service which includes
  238. Play, Send, Display, and Print service. The parameters for this command
  239. are "asp" to identify the command as P2PS one, auto accept value,
  240. advertisement id which uniquely identifies the service requests, state
  241. of the service whether the service is available or not, config methods
  242. which can be either P2PS method or PIN method, service name followed by
  243. two optional parameters service information, and response info.
  244. For example,
  245. p2p_service_add asp 1 4d6fc7 0 1108 alt.example.chat svc_info='name=john' rsp_info='enter PIN 1234'
  246. Parameters definition:
  247. asp - Mandatory for ASP service registration
  248. auto accept - Mandatory ASCII hex-encoded boolean (0 == no auto-accept,
  249. 1 == auto-accept ANY role, 2 == auto-accept CLIENT role,
  250. 4 == auto-accept GO role)
  251. Advertisement ID - Mandatory non-zero ASCII hex-encoded u32
  252. (Must be unique/not yet exist in svc db)
  253. State - Mandatory ASCII hex-encoded u8 (0 -- Svc not available,
  254. 1 -- Svc available, 2-0xff Application defined)
  255. Config Methods - Mandatory ASCII hex-encoded u16 (bitmask of WSC config
  256. methods)
  257. Service Name - Mandatory UTF-8 string
  258. Service Information - Optional UTF-8 string
  259. Escape single quote & backslash with a backslash:
  260. 0x27 == ' == \', and 0x5c == \ == \\
  261. Session response information - Optional (used only if auto accept is TRUE)
  262. UTF-8 string
  263. Escape single quote & backslash with a backslash:
  264. 0x27 == ' == \', and 0x5c == \ == \\
  265. p2p_service_rep asp <auto accept> <adv id> <status 0/1> <Config Methods>
  266. <Service name> [Service Information] [Response Info]
  267. This command can be used to replace the existing service request
  268. attributes from the initiator side. The replacement is only allowed if
  269. the advertisement id issued in the command matches with any one entry in
  270. the list of existing SD queries. If advertisement id doesn't match the
  271. command returns a failure.
  272. For example,
  273. p2p_service_rep asp 1 4d6fc7 1 1108 alt.example.chat svc_info='name=john' rsp_info='enter PIN 1234'
  274. Parameters definition:
  275. asp - Mandatory for ASP service registration
  276. auto accept - Mandatory ASCII hex-encoded boolean (1 == true, 0 == false)
  277. Advertisement ID - Mandatory non-zero ASCII hex-encoded u32
  278. (Must already exist in svc db)
  279. State - Mandatory ASCII hex-encoded u8 (can be used to indicate svc
  280. available or not available for instance)
  281. Config Methods - Mandatory ASCII hex-encoded u16 (bitmask of WSC config
  282. methods)
  283. Service Name - Mandatory UTF-8 string (Must match existing string in svc db)
  284. Service Information - Optional UTF-8 string
  285. Escape single quote & backslash with a backslash:
  286. 0x27 == ' == \', and 0x5c == \ == \\
  287. Session response information - Optional (used only if auto accept is TRUE)
  288. UTF-8 string
  289. Escape single quote & backslash with a backslash:
  290. 0x27 == ' == \', and 0x5c == \ == \\
  291. p2p_serv_disc_req
  292. Schedule a P2P service discovery request. The parameters for this
  293. command are the device address of the peer device (or 00:00:00:00:00:00
  294. for wildcard query that is sent to every discovered P2P peer that
  295. supports service discovery) and P2P Service Query TLV(s) as hexdump. For
  296. example,
  297. p2p_serv_disc_req 00:00:00:00:00:00 02000001
  298. schedules a request for listing all available services of all service
  299. discovery protocols and requests this to be sent to all discovered
  300. peers (note: this can result in long response frames). The pending
  301. requests are sent during device discovery (see p2p_find).
  302. There can be multiple pending peer device specific queries (each will be
  303. sent in sequence whenever the peer is found).
  304. This command returns an identifier for the pending query (e.g.,
  305. "1f77628") that can be used to cancel the request. Directed requests
  306. will be automatically removed when the specified peer has replied to
  307. it.
  308. Service Query TLV has following format:
  309. Length (2 octets, little endian) - length of following data
  310. Service Protocol Type (1 octet) - see the table below
  311. Service Transaction ID (1 octet) - nonzero identifier for the TLV
  312. Query Data (Length - 2 octets of data) - service protocol specific data
  313. Service Protocol Types:
  314. 0 = All service protocols
  315. 1 = Bonjour
  316. 2 = UPnP
  317. 3 = WS-Discovery
  318. 4 = Wi-Fi Display
  319. For UPnP, an alternative command format can be used to specify a
  320. single query TLV (i.e., a service discovery for a specific UPnP
  321. service):
  322. p2p_serv_disc_req 00:00:00:00:00:00 upnp <version hex> <ST: from M-SEARCH>
  323. For example:
  324. p2p_serv_disc_req 00:00:00:00:00:00 upnp 10 urn:schemas-upnp-org:device:InternetGatewayDevice:1
  325. Additional examples for queries:
  326. # list of all Bonjour services
  327. p2p_serv_disc_req 00:00:00:00:00:00 02000101
  328. # list of all UPnP services
  329. p2p_serv_disc_req 00:00:00:00:00:00 02000201
  330. # list of all WS-Discovery services
  331. p2p_serv_disc_req 00:00:00:00:00:00 02000301
  332. # list of all Bonjour and UPnP services
  333. p2p_serv_disc_req 00:00:00:00:00:00 0200010102000202
  334. # Apple File Sharing over TCP
  335. p2p_serv_disc_req 00:00:00:00:00:00 130001010b5f6166706f766572746370c00c000c01
  336. # Bonjour SSTH (supported service type hash)
  337. p2p_serv_disc_req 00:00:00:00:00:00 05000101000000
  338. # UPnP examples
  339. p2p_serv_disc_req 00:00:00:00:00:00 upnp 10 ssdp:all
  340. p2p_serv_disc_req 00:00:00:00:00:00 upnp 10 upnp:rootdevice
  341. p2p_serv_disc_req 00:00:00:00:00:00 upnp 10 urn:schemas-upnp-org:service:ContentDirectory:2
  342. p2p_serv_disc_req 00:00:00:00:00:00 upnp 10 uuid:6859dede-8574-59ab-9332-123456789012
  343. p2p_serv_disc_req 00:00:00:00:00:00 upnp 10 urn:schemas-upnp-org:device:InternetGatewayDevice:1
  344. # Wi-Fi Display examples
  345. # format: wifi-display <list of roles> <list of subelements>
  346. p2p_serv_disc_req 00:00:00:00:00:00 wifi-display [source] 2,3,4,5
  347. p2p_serv_disc_req 02:01:02:03:04:05 wifi-display [pri-sink] 3
  348. p2p_serv_disc_req 00:00:00:00:00:00 wifi-display [sec-source] 2
  349. p2p_serv_disc_req 00:00:00:00:00:00 wifi-display [source+sink] 2,3,4,5
  350. p2p_serv_disc_req 00:00:00:00:00:00 wifi-display [source][pri-sink] 2,3,4,5
  351. p2p_serv_disc_req <Unicast|Broadcast mac address> asp <Transaction ID>
  352. <Service Name> [Service Information]
  353. The command can be used for service discovery for P2PS enabled devices.
  354. For example: p2p_serv_disc_req 00:00:00:00:00:00 asp a1 alt.example 'john'
  355. Parameters definition:
  356. MAC address - Mandatory Existing
  357. asp - Mandatory for ASP queries
  358. Transaction ID - Mandatory non-zero ASCII hex-encoded u8 for GAS
  359. Service Name Prefix - Mandatory UTF-8 string.
  360. Will match from beginning of remote Service Name
  361. Service Information Substring - Optional UTF-8 string
  362. If Service Information Substring is not included, all services matching
  363. Service Name Prefix will be returned.
  364. If Service Information Substring is included, both the Substring and the
  365. Service Name Prefix must match for service to be returned.
  366. If remote service has no Service Information, all Substring searches
  367. will fail.
  368. p2p_serv_disc_cancel_req <query identifier>
  369. Cancel a pending P2P service discovery request. This command takes a
  370. single parameter: identifier for the pending query (the value returned
  371. by p2p_serv_disc_req, e.g., "p2p_serv_disc_cancel_req 1f77628".
  372. p2p_serv_disc_resp
  373. Reply to a service discovery query. This command takes following
  374. parameters: frequency in MHz, destination address, dialog token,
  375. response TLV(s). The first three parameters are copied from the
  376. request event. For example, "p2p_serv_disc_resp 2437 02:40:61:c2:f3:b7
  377. 1 0300000101". This command is used only if external program is used
  378. to process the request (see p2p_serv_disc_external).
  379. p2p_service_update
  380. Indicate that local services have changed. This is used to increment
  381. the P2P service indicator value so that peers know when previously
  382. cached information may have changed. This is only needed when external
  383. service discovery processing is enabled since the commands to
  384. pre-configure services for internal processing will increment the
  385. indicator automatically.
  386. p2p_serv_disc_external <0|1>
  387. Configure external processing of P2P service requests: 0 (default) =
  388. no external processing of requests (i.e., internal code will process
  389. each request based on pre-configured services), 1 = external
  390. processing of requests (external program is responsible for replying
  391. to service discovery requests with p2p_serv_disc_resp). Please note
  392. that there is quite strict limit on how quickly the response needs to
  393. be transmitted, so use of the internal processing is strongly
  394. recommended.
  395. p2p_service_add bonjour <query hexdump> <RDATA hexdump>
  396. Add a local Bonjour service for internal SD query processing.
  397. Examples:
  398. # AFP Over TCP (PTR)
  399. p2p_service_add bonjour 0b5f6166706f766572746370c00c000c01 074578616d706c65c027
  400. # AFP Over TCP (TXT) (RDATA=null)
  401. p2p_service_add bonjour 076578616d706c650b5f6166706f766572746370c00c001001 00
  402. # IP Printing over TCP (PTR) (RDATA=MyPrinter._ipp._tcp.local.)
  403. p2p_service_add bonjour 045f697070c00c000c01 094d795072696e746572c027
  404. # IP Printing over TCP (TXT) (RDATA=txtvers=1,pdl=application/postscript)
  405. p2p_service_add bonjour 096d797072696e746572045f697070c00c001001 09747874766572733d311a70646c3d6170706c69636174696f6e2f706f7374736372797074
  406. # Supported Service Type Hash (SSTH)
  407. p2p_service_add bonjour 000000 <32-byte bitfield as hexdump>
  408. (note: see P2P spec Annex E.4 for information on how to construct the bitfield)
  409. p2p_service_del bonjour <query hexdump>
  410. Remove a local Bonjour service from internal SD query processing.
  411. p2p_service_add upnp <version hex> <service>
  412. Add a local UPnP service for internal SD query processing.
  413. Examples:
  414. p2p_service_add upnp 10 uuid:6859dede-8574-59ab-9332-123456789012::upnp:rootdevice
  415. p2p_service_add upnp 10 uuid:5566d33e-9774-09ab-4822-333456785632::upnp:rootdevice
  416. p2p_service_add upnp 10 uuid:1122de4e-8574-59ab-9322-333456789044::urn:schemas-upnp-org:service:ContentDirectory:2
  417. p2p_service_add upnp 10 uuid:5566d33e-9774-09ab-4822-333456785632::urn:schemas-upnp-org:service:ContentDirectory:2
  418. p2p_service_add upnp 10 uuid:6859dede-8574-59ab-9332-123456789012::urn:schemas-upnp-org:device:InternetGatewayDevice:1
  419. p2p_service_del upnp <version hex> <service>
  420. Remove a local UPnP service from internal SD query processing.
  421. p2p_service_del asp <adv id>
  422. Removes the local asp service from internal SD query list.
  423. For example: p2p_service_del asp 4d6fc7
  424. p2p_service_flush
  425. Remove all local services from internal SD query processing.
  426. Invitation
  427. p2p_invite [persistent=<network id>|group=<group ifname>] [peer=address]
  428. [go_dev_addr=address] [freq=<freq in MHz>] [ht40] [vht]
  429. [pref=<MHz>]
  430. Invite a peer to join a group (e.g., group=wlan1) or to reinvoke a
  431. persistent group (e.g., persistent=4). If the peer device is the GO of
  432. the persistent group, the peer parameter is not needed. Otherwise it is
  433. used to specify which device to invite. go_dev_addr parameter can be
  434. used to override the GO device address for Invitation Request should
  435. it be not known for some reason (this should not be needed in most
  436. cases). When reinvoking a persistent group, the GO device can specify
  437. the frequency for the group with the freq parameter. When reinvoking a
  438. persistent group, the P2P client device can use freq parameter to force
  439. a specific operating channel (or invitation failure if GO rejects that)
  440. or pref parameter to request a specific channel (while allowing GO to
  441. select to use another channel, if needed).
  442. Group Operations
  443. (These are used on the group interface.)
  444. wps_pin <any|address> <PIN>
  445. Start WPS PIN method. This allows a single WPS Enrollee to connect to
  446. the AP/GO. This is used on the GO when a P2P client joins an existing
  447. group. The second parameter is the address of the Enrollee or a string
  448. "any" to allow any station to use the entered PIN (which will restrict
  449. the PIN for one-time-use). PIN is the Enrollee PIN read either from a
  450. label or display on the P2P Client/WPS Enrollee.
  451. wps_pbc
  452. Start WPS PBC method (i.e., push the button). This allows a single WPS
  453. Enrollee to connect to the AP/GO. This is used on the GO when a P2P
  454. client joins an existing group.
  455. p2p_get_passphrase
  456. Get the passphrase for a group (only available when acting as a GO).
  457. p2p_presence_req [<duration> <interval>] [<duration> <interval>]
  458. Send a P2P Presence Request to the GO (this is only available when
  459. acting as a P2P client). If no duration/interval pairs are given, the
  460. request indicates that this client has no special needs for GO
  461. presence. The first parameter pair gives the preferred duration and
  462. interval values in microseconds. If the second pair is included, that
  463. indicates which value would be acceptable. This command returns OK
  464. immediately and the response from the GO is indicated in a
  465. P2P-PRESENCE-RESPONSE event message.
  466. Parameters
  467. p2p_ext_listen [<period> <interval>]
  468. Configure Extended Listen Timing. If the parameters are omitted, this
  469. feature is disabled. If the parameters are included, Listen State will
  470. be entered every interval msec for at least period msec. Both values
  471. have acceptable range of 1-65535 (with interval obviously having to be
  472. larger than or equal to duration). If the P2P module is not idle at
  473. the time the Extended Listen Timing timeout occurs, the Listen State
  474. operation will be skipped.
  475. The configured values will also be advertised to other P2P Devices. The
  476. received values are available in the p2p_peer command output:
  477. ext_listen_period=100 ext_listen_interval=5000
  478. p2p_set <field> <value>
  479. Change dynamic P2P parameters
  480. p2p_set discoverability <0/1>
  481. Disable/enable advertisement of client discoverability. This is
  482. enabled by default and this parameter is mainly used to allow testing
  483. of device discoverability.
  484. p2p_set managed <0/1>
  485. Disable/enable managed P2P Device operations. This is disabled by
  486. default.
  487. p2p_set listen_channel <channel> [<op_class>]
  488. Set P2P Listen channel. This is mainly meant for testing purposes and
  489. changing the Listen channel during normal operations can result in
  490. protocol failures.
  491. When specifying a social channel on the 2.4 GHz band (1/6/11) there is
  492. no need to specify the operating class since it defaults to 81. When
  493. specifying a social channel on the 60 GHz band (2), specify the 60 GHz
  494. operating class (180).
  495. p2p_set ssid_postfix <postfix>
  496. Set postfix string to be added to the automatically generated P2P SSID
  497. (DIRECT-<two random characters>). For example, postfix of "-testing"
  498. could result in the SSID becoming DIRECT-ab-testing.
  499. p2p_set per_sta_psk <0/1>
  500. Disabled(default)/enables use of per-client PSK in the P2P groups. This
  501. can be used to request GO to assign a unique PSK for each client during
  502. WPS provisioning. When enabled, this allow clients to be removed from
  503. the group securely with p2p_remove_client command since that client's
  504. PSK is removed at the same time to prevent it from connecting back using
  505. the old PSK. When per-client PSK is not used, the client can still be
  506. disconnected, but it will be able to re-join the group since the PSK it
  507. learned previously is still valid. It should be noted that the default
  508. passphrase on the GO that is normally used to allow legacy stations to
  509. connect through manual configuration does not change here, so if that is
  510. shared, devices with knowledge of that passphrase can still connect.
  511. set <field> <value>
  512. Set global configuration parameters which may also affect P2P
  513. operations. The format on these parameters is same as is used in
  514. wpa_supplicant.conf. Only the parameters listen here should be
  515. changed. Modifying other parameters may result in incorrect behavior
  516. since not all existing users of the parameters are updated.
  517. set uuid <UUID>
  518. Set WPS UUID (by default, this is generated based on the MAC address).
  519. set device_name <device name>
  520. Set WPS Device Name (also included in some P2P messages).
  521. set manufacturer <manufacturer>
  522. Set WPS Manufacturer.
  523. set model_name <model name>
  524. Set WPS Model Name.
  525. set model_number <model number>
  526. Set WPS Model Number.
  527. set serial_number <serial number>
  528. Set WPS Serial Number.
  529. set device_type <device type>
  530. Set WPS Device Type.
  531. set os_version <OS version>
  532. Set WPS OS Version.
  533. set config_methods <config methods>
  534. Set WPS Configuration Methods.
  535. set sec_device_type <device type>
  536. Add a new Secondary Device Type.
  537. set p2p_go_intent <GO intent>
  538. Set the default P2P GO Intent. Note: This value can be overridden in
  539. p2p_connect command and as such, there should be no need to change the
  540. default value here during normal operations.
  541. set p2p_ssid_postfix <P2P SSID postfix>
  542. Set P2P SSID postfix.
  543. set persistent_reconnect <0/1>
  544. Disable/enabled persistent reconnect for reinvocation of persistent
  545. groups. If enabled, invitations to reinvoke a persistent group will be
  546. accepted without separate authorization (e.g., user interaction).
  547. set country <two character country code>
  548. Set country code (this is included in some P2P messages).
  549. set p2p_search_delay <delay>
  550. Set p2p_search_delay which adds extra delay in milliseconds between
  551. concurrent search iterations to make p2p_find friendlier to concurrent
  552. operations by avoiding it from taking 100% of radio resources. The
  553. default value is 500 ms.
  554. Status
  555. p2p_peers [discovered]
  556. List P2P Device Addresses of all the P2P peers we know. The optional
  557. "discovered" parameter filters out the peers that we have not fully
  558. discovered, i.e., which we have only seen in a received Probe Request
  559. frame.
  560. p2p_peer <P2P Device Address>
  561. Fetch information about a known P2P peer.
  562. Group Status
  563. (These are used on the group interface.)
  564. status
  565. Show status information (connection state, role, use encryption
  566. parameters, IP address, etc.).
  567. sta
  568. Show information about an associated station (when acting in AP/GO role).
  569. all_sta
  570. Lists the currently associated stations.
  571. Configuration data
  572. list_networks
  573. Lists the configured networks, including stored information for
  574. persistent groups. The identifier in this list is used with
  575. p2p_group_add and p2p_invite to indicate which persistent group is to
  576. be reinvoked.
  577. remove_network <network id>
  578. Remove a network entry from configuration.
  579. P2PS Events/Responses:
  580. P2PS-PROV-START: This events gets triggered when provisioning is issued for
  581. either seeker or advertiser.
  582. For example,
  583. P2PS-PROV-START 00:55:44:33:22:11 adv_id=111 adv_mac=00:55:44:33:22:11 conncap=1 session=1234567 session_mac=00:11:22:33:44:55 info='xxxx'
  584. Parameters definition:
  585. MAC address - always
  586. adv_id - always ASCII hex-encoded u32
  587. adv_mac - always MAC address that owns/registered the service
  588. conncap - always mask of 0x01 (new), 0x02 (group client), 0x04 (group owner)
  589. bits
  590. session - always Session ID of the first session to be established
  591. session_mac - always MAC address that owns/initiated the session
  592. info - if available, UTF-8 string
  593. Escaped single quote & backslash with a backslash:
  594. \' == 0x27 == ', and \\ == 0x5c == \
  595. P2PS-PROV-DONE: When provisioning is completed then this event gets triggered.
  596. For example,
  597. P2PS-PROV-DONE 00:11:22:33:44:55 status=0 adv_id=111 adv_mac=00:55:44:33:22:11 conncap=1 session=1234567 session_mac=00:11:22:33:44:55 [dev_passwd_id=8 | go=p2p-wlan0-0 | join=11:22:33:44:55:66 | persist=0]
  598. Parameters definition:
  599. MAC address - always main device address of peer. May be different from MAC
  600. ultimately connected to.
  601. status - always ascii hex-encoded u8 (0 == success, 12 == deferred success)
  602. adv_id - always ascii hex-encoded u32
  603. adv_mac - always MAC address that owns/registered the service
  604. conncap - always One of: 1 (new), 2 (group client), 4 (group owner) bits
  605. session - always Session ID of the first session to be established
  606. session_mac - always MAC address that owns/initiated the session
  607. dev_passwd_id - only if conncap value == 1 (New GO negotiation)
  608. 8 - "p2ps" password must be passed in p2p_connect command
  609. 1 - "display" password must be passed in p2p_connect command
  610. 5 - "keypad" password must be passed in p2p_connect command
  611. join only - if conncap value == 2 (Client Only). Display password and "join"
  612. must be passed in p2p_connect and address must be the MAC specified
  613. go only - if conncap value == 4 (GO Only). Interface name must be set with a
  614. password
  615. persist - only if previous persistent group existed between peers and shall
  616. be re-used. Group is restarted by sending "p2p_group_add persistent=0"
  617. where value is taken from P2P-PROV-DONE
  618. Extended Events/Response
  619. P2P-DEVICE-FOUND 00:11:22:33:44:55 p2p_dev_addr=00:11:22:33:44:55 pri_dev_type=0-00000000-0 name='' config_methods=0x108 dev_capab=0x21 group_capab=0x0 adv_id=111 asp_svc=alt.example.chat
  620. Parameters definition:
  621. adv_id - if ASP ASCII hex-encoded u32. If it is reporting the
  622. "wildcard service", this value will be 0
  623. asp_svc - if ASP this is the service string. If it is reporting the
  624. "wildcard service", this value will be org.wi-fi.wfds
  625. wpa_cli action script
  626. ---------------------
  627. See examples/p2p-action.sh
  628. TODO: describe DHCP/DNS setup
  629. TODO: cross-connection