An array with supported capabilities (e.g., "ap", "ibss-rsn", "p2p", "interworking").
+ +Wi-Fi Display subelements.
+Starts WPS configuration.
+Starts WPS configuration. Note: When used with P2P groups, this needs to be issued on the GO group interface.
Start P2P find operation (i.e., alternating P2P Search and Listen states to discover peers and be discoverable).
+| Key | Value type | Description | Required |
|---|---|---|---|
| Timeout | i | Timeout for operating in seconds | no |
| RequestedDevicesTypes | aay | WPS Device Types to search for | no |
| DiscoveryType | s | "start_with_full" (default, if not specified), "social", "progressive" | no |
Stop P2P find operation.
+Start P2P listen operation (i.e., be discoverable).
+Configure Extended Listen Timing. If the parameters are omitted, this feature is disabled. If the parameters are included, Listen State will be entered every interval msec for at least period msec. Both values have acceptable range of 1-65535 (with interval obviously having to be larger than or equal to duration). If the P2P module is not idle at the time the Extended Listen Timing timeout occurs, the Listen State operation will be skipped.
+| Key | Value type | Description | Required |
|---|---|---|---|
| period | i | Extended listen period in milliseconds; 1-65535. | no |
| interval | i | Extended listen interval in milliseconds; 1-65535. | no |
Request a specific GO presence in a P2P group where the local device is a P2P Client. Send a P2P Presence Request to the GO (this is only available when acting as a P2P client). If no duration/interval pairs are given, the request indicates that this client has no special needs for GO presence. The first parameter pair gives the preferred duration and interval values in microseconds. If the second pair is included, that indicates which value would be acceptable. + \note This needs to be issued on a P2P group interface if separate group interfaces are used. + \bug It would be cleaner to not require .P2PDevice methods to be issued on a group interface. In other words, args['group_object'] could be used to specify the group or this method could be moved to be a .Group PresenceRequest() method.
+| Key | Value type | Description | Required |
|---|---|---|---|
| duration1 | i | Duration in microseconds. | no |
| interval1 | i | Interval in microseconds. | no |
| duration2 | i | Duration in microseconds. | no |
| interval2 | i | Interval in microseconds. | no |
Request a P2P group to be started through GO Negotiation or by joining an already operating group.
+| Key | Value type | Description | Required |
|---|---|---|---|
| peer | o | yes | |
| persistent | b | Whether to form a persistent group. | no |
| join | b | Whether to join an already operating group instead of forming a new group. | no |
| authorize_only | b | Whether to authorize a peer to initiate GO Negotiation instead of initiating immediately. | no |
| frequency | i | Operating frequency in MHz | no |
| go_intent | i | GO intent 0-15 | no |
| wps_method | s | "pbc", "display", "keypad", "pin" (alias for "display") | yes |
| pin | s | no |
Request a P2P group to be started without GO Negotiation.
+| Key | Value type | Description | Required |
|---|---|---|---|
| persistent | b | Whether to form a persistent group. | no |
| persistent_group_object | o | no | |
| frequency | i | Operating frequency in MHz | no |
Invite a peer to join an already operating group or to re-invoke a persistent group.
+| Key | Value type | Description | Required |
|---|---|---|---|
| peer | o | yes | |
| persistent_group_object | o | no |
Terminate a P2P group. + \note This needs to be issued on a P2P group interface if separate group interfaces are used. + \bug It would be cleaner to not require .P2PDevice methods to be issued on a group interface. In other words, this would either need to be Disconnect(group_object) or moved to be a .Group Disconnect() method.
+Reject connection attempt from a peer (specified with a device address). This is a mechanism to reject a pending GO Negotiation with a peer and request to automatically block any further connection or discovery of the peer.
+Flush P2P peer table and state.
+| Key | Value type | Description | Required |
|---|---|---|---|
| service_type | s | "upnp", "bonjour" | yes |
| version | u | Required for UPnP services. | no |
| service | s | ||
| query | ay | ||
| response | ay |
| Key | Value type | Description | Required |
|---|---|---|---|
| service_type | s | "upnp", "bonjour" | yes |
| version | u | Required for UPnP services. | no |
| service | s | ||
| query | ay |
| Key | Value type | Description | Required |
|---|---|---|---|
| peer_object | o | no | |
| service_type | s | "upnp" | no |
| version | u | Required for UPnP services. | no |
| service | s | ||
| tlv | ay |
| Key | Value type | Description | Required |
|---|---|---|---|
| peer_object | o | yes | |
| frequency | i | yes | |
| dialog_token | i | yes | |
| tlvs | ay | yes |
| Key | Value type | Description | Required |
|---|---|---|---|
| bssid | s | P2P Device Address of the GO in the persistent group. | yes |
| ssid | s | SSID of the group | yes |
| psk | s | Passphrase (on the GO and optionally on P2P Client) or PSK (on P2P Client if passphrase ise not known) | yes |
| mode | s | "3" on GO or "0" on P2P Client | yes |
Dictionary with following entries. On write, only the included values are changed.
+| Key | Value type | Description |
|---|---|---|
| DeviceName | s | |
| PrimaryDeviceType | ay | |
| SecondaryDeviceTypes | aay | |
| VendorExtension | aay | |
| GOIntent | u | |
| PersistentReconnect | b | |
| ListenRegClass | u | |
| OperRegClass | u | |
| OperChannel | u | |
| SsidPostfix | s | |
| IntraBss | b | |
| GroupIdle | u | |
| disassoc_low_ack | u | |
| NoGroupIface | b | |
| p2p_search_delay | u |
\bug What is this trying to indicate? It does not make much sense to have a P2PDevice property role since there can be multiple concurrent groups and the P2P Device role is always active anyway.
+\bug What is this trying to indicate? It does not make much sense to have a P2PDevice property Group since there can be multiple concurrent groups.
+\bug What is this trying to indicate? It does not make much sense to have a P2PDevice property PeerGO since there can be multiple concurrent groups.
+A new P2P group was started or joined.
+| Key | Value type | Description |
|---|---|---|
| interface_object | o | D-Bus path of the interface on which this group is operating on. See \ref dbus_interface. |
| role | s | The role of the local device in the group: "GO" or "client". |
| group_object | o | D-Bus path of the group. See \ref dbus_group. |
| Key | Value type | Description |
|---|---|---|
| peer_object | o | D-Bus path of the peer. See \ref dbus_peer. |
| status | i | |
| passphrase | s | Passphrase for the group. Included only if this device becomes the GO of the group. |
| role_go | s | The role of the local device in the group: "GO" or "client". |
| ssid | ay | |
| peer_device_addr | ay | |
| peer_interface_addr | ay | |
| wps_method | s | |
| frequency_list | ai | |
| persistent_group | i | |
| peer_config_timeout | u |
| Key | Value type | Description |
|---|---|---|
| peer_object | o | D-Bus path of the peer. See \ref dbus_peer. |
| status | i |
| Key | Value type | Description |
|---|---|---|
| status | i | |
| BSSID | ay | Optionally present |
A P2P group was removed.
+| Key | Value type | Description |
|---|---|---|
| interface_object | o | D-Bus path of the interface on which this group is operating on. See \ref dbus_interface. |
| role | s | The role of the local device in the group: "GO" or "client". |
| group_object | o | D-Bus path of the group. See \ref dbus_group. |
| peer_object | o | |
| frequency | i | |
| dialog_token | i | |
| update_indicator | q | |
| tlvs | ay |
| peer_object | o | |
| update_indicator | q | |
| tlvs | ay |
| Key | Value type | Description |
|---|---|---|
| bssid | s | P2P Device Address of the GO in the persistent group. |
| ssid | s | SSID of the group |
| psk | s | Passphrase (on the GO and optionally on P2P Client) or PSK (on P2P Client if passphrase ise not known) |
| disabled | s | Set to "2" to indicate special network block use as a P2P persistent group information |
| mode | s | "3" on GO or "0" on P2P Client |
| Key | Value type | Description |
|---|---|---|
| msg | i | |
| config_error | n |
Group Capability field from the last frame from which this peer information was updated. + \note This field is only for debugging purposes and must not be used to determine whether the peer happens to be operating a group as a GO at the moment. +
+This is a confusingly named property that includes Wi-Fi Display subelements from the peer. + \bug This should really be renamed since "IEs" means something completely different.. +
+The P2P Device Address of the peer.
+The current groups in which this peer is connected.
+Some properties have changed. + \deprecated Use org.freedesktop.DBus.Properties.PropertiesChanged instead.
+ \todo Explain how ProertiesChanged signals are supposed to be of any real use with Peer objects (i.e., one signal for multiple peers). +Array of D-Bus object paths for the peer devices that are currently connected to the group. This is valid only on the GO device. An empty array is returned in P2P Client role. +
\todo Why is this here? This D-Bus object path is to this specific group and one needs to know it to fetching this information in the first place.. +
+The role of this device in the group: "GO", "client".
+P2P Group SSID.
+P2P Group BSSID (the P2P Interface Address of the GO).
+The frequency (in MHz) of the group operating channel.
+Passphrase used in the group. This is always available on the GO. For P2P Client role, this may be available depending on whether the peer GO provided the passphrase during the WPS provisioning step. If not available, an empty string is returned.
+PSK used in the group.
+WPS vendor extension attributes used on the GO. This is valid only the in the GO role. An empty array is returned in P2P Client role. At maximum, 10 separate vendor extension byte arrays can be configured. The GO device will include the configured attributes in WPS exchanges.
+A peer device has joined the group. This is indicated only on the GO device.
+A peer device has left the group. This is indicated only on the GO device.
+Properties of the persistent group. These are same properties as in the \ref dbus_network. When writing this, only the entries to be modified are included, i.e., any item that is not included will be left at its existing value. The following entries are used for persistent groups:
+| Key | Value type | Description |
|---|---|---|
| bssid | s | P2P Device Address of the GO in the persistent group. |
| ssid | s | SSID of the group |
| psk | s | Passphrase (on the GO and optionally on P2P Client) or PSK (on P2P Client if passphrase ise not known) |
| disabled | s | Set to "2" to indicate special network block use as a P2P persistent group information |
| mode | s | "3" on GO or "0" on P2P Client |