Home
last modified time | relevance | path

Searched refs:device (Results 1 – 25 of 37) sorted by relevance

12

/hostap-3.7.0/tests/remote/
Dconfig.py74 for device in devices:
75 if device['name'] == name:
76 return device
77 for device in devices:
79 device_flags = device['flags']
81 return device
Dtest_devices.py28 for device in devices:
29 host = rutils.get_host(devices, device['name'])
Drun-tests.py244 for device in devices:
245 print("\t", device['name'])
/hostap-3.7.0/wpa_supplicant/
DREADME-DPP6 the STA device and AP can be configured to connect each other using DPP
47 Any STA or AP device can act as a Configurator. Enable DPP in build
102 Generate QR code for the device. Store the QR code id returned by the
105 …bootstrap_gen type=qrcode mac=<mac-address-of-device> chan=<operating-class/channel> key=<key of t…
109 device is waiting. This uses global operating classes; e.g., 81/1 is the 2.4
112 Get URI for the QR Code of device using the bootstrap info id.
115 Make device listen to DPP request. The central frequency of the 2.4 GHz
116 band channel 1 is 2412 MHz) in case the Enrollee is a client device. An
136 values to the hostapd config file. If the Enrollee is a client device,
152 in config files, they are taken up in next restart), the client device
[all …]
DREADME-P2P75 [dev_id=<addr>] [dev_type=<device type>] \
93 The optional dev_type option can be used to specify a single device type
105 dev_id - Optional to request responses from a single known remote device
121 testing. It can also be used to keep the device discoverable without
126 Stop ongoing P2P device discovery or other operation (connect, listen
135 p2p_prov_disc <peer device address> <display|keypad|pbc> [join|auto]
138 parameters for this command are the P2P device address of the peer and
148 out whether the peer device is operating as a GO and if so, use
151 p2p_connect <peer device address> <pbc|pin|PIN#|p2ps> [display|keypad|p2ps]
170 group where this device was the GO. The previously used parameters will
[all …]
DREADME-WPS30 - Registrar: a device that control a network and can authorize
32 Registrar") or in an external device, e.g., a laptop, ("external
34 - Enrollee: a device that is being authorized to use the network
36 It should also be noted that the AP and a client device may change
37 roles (i.e., AP acts as an Enrollee and client device as a Registrar)
75 the device. This is configured in the runtime configuration for
98 WPS requires either a device PIN code (usually, 8-digit number) or a
110 If the client device has a display, a random PIN has to be generated
122 If the client device does not have a display that could show the
145 be enabled by either a physical button in the client device or a
[all …]
/hostap-3.7.0/tests/
Dcipher-and-key-mgmt-testing.txt25 tested device at all or without knowing details of its
28 traffic is used to verify reaction of the tested device to such
37 wpa_supplicant is used to control a test device in station mode to test
38 an AP and hostapd is similarly used to control a test device in AP mode
87 beginning if the other device is not yet in the ARP table, so working
162 Testing replay protection on a station device
165 Start hostapd and use hostapd_cli on the test device to control testing
185 device increases beyond the value used prior to that RESET_PN command.
197 from the test device increases beyond the value used prior to that
201 Testing replay protection on an AP device
[all …]
/hostap-3.7.0/hostapd/
DREADME-WPS29 - Registrar: a device that control a network and can authorize
31 Registrar") or in an external device, e.g., a laptop, ("external
33 - Enrollee: a device that is being authorized to use the network
35 It should also be noted that the AP and a client device may change
36 roles (i.e., AP acts as an Enrollee and client device as a Registrar)
86 # Enable random per-device PSK generation for WPS clients
120 WPS requires either a device PIN code (usually, 8-digit number) or a
132 When a client device (WPS Enrollee) connects to hostapd (WPS
135 with a device password (PIN) for this Enrollee. This is an operation
139 The PIN request with information about the device is appended to the
[all …]
Ddefconfig237 # generator or by storing state over device reboots.
361 # of client device like "Nexus 6P" or "iPhone 5s".
/hostap-3.7.0/doc/
Dp2p.doxygen71 machine, i.e., only a single operation per device can be in progress
141 In addition to the per-device state, the P2P module maintains
179 \section p2p_go_neg P2P device discovery and group formation
182 to implement P2P device discovery and group formation. The function
187 An upper layer management entity starts P2P device discovery by
196 Search states until the device discovery operation times out or
209 function. If a group owner negotiation from another P2P device is
210 received during the device discovery phase, that is indicated to the
229 to display a PIN for the local device to enter (and vice versa). Upper
232 \ref p2p_config::prov_disc_resp() callback. If the peer device started
[all …]
Dctrl_iface.doxygen385 Start P2P device discovery. Optional parameter can be used to specify
398 social channel scans. Progressive device discovery can be used to find
406 Stop ongoing P2P device discovery or other operation (connect, listen
416 P2P_CONNECT <peer device address> <pbc|pin|PIN#>
430 keypad=PIN entered from peer device label or display). "persistent"
437 device without actually starting GO Negotiation (i.e., the peer is
450 for testing. It can also be used to keep the device discoverable
472 parameters for this command are the P2P device address of the peer and
487 command are the device address of the peer device (or 00:00:00:00:00:00
493 are sent during device discovery (see \ref ctrl_iface_P2P_FIND).
[all …]
Dwpa_supplicant.fig108 4 0 0 50 -1 0 12 0.0000 4 135 2145 3600 8025 kernel network device driver\001
Dhostapd.fig62 4 0 0 50 -1 0 12 0.0000 4 135 2145 3600 8025 kernel network device driver\001
Ddbus.doxygen1318 …<tr><td>Role</td><td>s</td><td>The device's role. Possible values are "enrollee" and "registrar".<…
1363 <p>User-friendly description of device; up to 32 octets encoded in UTF-8.</p>
1367 <p>The manufacturer of the device (up to 64 ASCII characters).</p>
1371 <p>Model of the device (up to 32 ASCII characters).</p>
1375 <p>Additional device description (up to 32 ASCII characters).</p>
1379 <p>Serial number of the device (up to 32 characters).</p>
1502 …<p>Request a specific GO presence in a P2P group where the local device is a P2P Client. Send a P2…
1597 …<p>Reject connection attempt from a peer (specified with a device address). This is a mechanism to…
1804 <p>A new peer device has been found.</p>
1808 <dd>A D-Bus path to an object representing the found peer device.</dd>
[all …]
Dporting.doxygen88 operating between the device driver and the OS network stack. If such
90 directly in the device driver.
/hostap-3.7.0/wpa_supplicant/systemd/
Dwpa_supplicant.service.arg.in3 Requires=sys-subsystem-net-devices-%i.device
4 After=sys-subsystem-net-devices-%i.device
Dwpa_supplicant-nl80211.service.arg.in3 Requires=sys-subsystem-net-devices-%i.device
4 After=sys-subsystem-net-devices-%i.device
Dwpa_supplicant-wired.service.arg.in3 Requires=sys-subsystem-net-devices-%i.device
4 After=sys-subsystem-net-devices-%i.device
/hostap-3.7.0/wpadebug/
DREADME14 not supposed to be installed on a production use device and doing so may
15 result in complete loss of security protections on the device.
52 done. It should be obvious that these steps require a rooted device. In
/hostap-3.7.0/src/l2_packet/
Dl2_packet_freebsd.c164 static int eth_get(const char *device, u8 ea[ETH_ALEN]) in eth_get() argument
172 retval = dlpi_open(device, &dh, 0); in eth_get()
211 os_memcmp(sdl->sdl_data, device, sdl->sdl_nlen) != 0) in eth_get()
/hostap-3.7.0/tests/hwsim/vm/
Dvm-run.sh179 -device virtio-9p-pci,id=fs-root,fsdev=fsdev-root,mount_tag=/dev/root \
181 -device virtio-9p-pci,id=fs-logs,fsdev=fsdev-logs,mount_tag=logshare \
/hostap-3.7.0/src/drivers/
Ddriver_zephyr.c30 const struct zep_wpa_supp_dev_ops *get_dev_ops(const struct device *dev) in get_dev_ops()
1019 const struct device *device; in wpa_drv_zep_init() local
1024 device = net_if_get_device(iface); in wpa_drv_zep_init()
1025 if (!device) { in wpa_drv_zep_init()
1037 if_ctx->dev_ctx = device; in wpa_drv_zep_init()
Ddriver_zephyr.h118 const struct device *dev_ctx;
/hostap-3.7.0/wpa_supplicant/doc/docbook/
Dwpa_supplicant.sgml72 must be available. That means that the physical device must be
73 present and enabled, and the driver for the device must be
74 loaded. The daemon will exit immediately if the device is not already
78 network device, higher level configuration such as DHCP may
/hostap-3.7.0/src/wps/
Dwps_upnp.c870 static int eth_get(const char *device, u8 ea[ETH_ALEN]) in eth_get() argument
893 os_memcmp(sdl->sdl_data, device, sdl->sdl_nlen) != 0) in eth_get()

12