Lines Matching refs:with
15 Redistribution and use in source and binary forms, with or without
24 documentation and/or other materials provided with the distribution.
49 - WPA with EAP (e.g., with RADIUS authentication server) ("WPA-Enterprise")
50 Following authentication methods are supported with an integrate IEEE 802.1X
68 * LEAP (note: only with WEP keys, i.e., not for WPA; in addition, LEAP
72 material, they cannot be used with WPA or IEEE 802.1X WEP keying)
99 with Windows NDIS driver for your wlan card supporting WPA.
117 Linux ndiswrapper (http://ndiswrapper.sourceforge.net/) with
121 used with IEEE 802.1X (i.e., not WPA) when using ap_scan=0 option in
133 - libpcap (tested with 0.7.2, most relatively recent versions assumed to work,
134 this is likely to be available with most distributions,
136 - libdnet (tested with v1.4, most versions assumed to work,
142 USE_DNET_PCAP and link with these libraries).
146 - openssl (tested with 0.9.7c and 0.9.7d, assumed to work with most
147 relatively recent versions; this is likely to be available with most
154 EAP-GTC, EAP-OTP, and EAP-MSCHAPV2 cannot be used alone with WPA, so
157 algorithms with EAP-PEAP and EAP-TTLS.
178 enhancements that can be implemented with existing wlan hardware. This
185 for protecting wireless networks. WEP uses RC4 with 40-bit keys,
197 hardware. It still uses RC4 for the encryption like WEP, but with
225 robust encryption algorithm (CCMP: AES in Counter mode with CBC-MAC)
233 combinations seem to be working with equipment from different vendors.
244 negotiation with a WPA Authenticator and EAP authentication with
251 example text-based frontend, wpa_cli, is included with wpa_supplicant.
253 Following steps are used when associating with an AP using WPA:
257 - wpa_supplicant requests the kernel driver to associate with the chosen
260 completes EAP authentication with the authentication server (proxied
265 with the Authenticator (AP)
278 format: CONFIG_<option>=y. Lines starting with # are considered
289 TLS, PEAP, or TTLS will require linking wpa_supplicant with openssl
351 wpa_supplicant and wpa_cli with 'make' command. You may then install
363 /etc/wpa_supplicant.conf, with network configuration for the networks
367 configuration work by first running wpa_supplicant with following
368 command to start it on foreground with debugging enabled:
404 (this can also be used with Linuxant DriverLoader)
413 In most common cases, wpa_supplicant is started with
432 reloading can be triggered with 'wpa_cli reconfigure' command.
442 1) WPA-Personal (PSK) as home network and WPA-Enterprise with EAP-TLS as work
457 # work network; use EAP-TLS with WPA; allow only CCMP and TKIP ciphers
473 2) WPA-RADIUS/EAP-PEAP/MSCHAPv2 with RADIUS servers that use old peaplabel
491 3) EAP-TTLS/EAP-MD5-Challenge configuration with anonymous identity for the
509 4) IEEE 802.1X (i.e., no WPA) with dynamic WEP keys (require both unicast and
574 wpa_supplicant. This can be done, e.g., with following commands:
586 wpa_cli is a text-based frontend program for interacting with
603 file). This makes it possible to run wpa_cli with a normal user
622 interactive mode. wpa_cli shows these requests with
628 The reply to these requests can be given with 'identity', 'password',
632 between these two commands is that values given with 'password' are
634 with 'otp' are used only once and then forgotten, i.e., wpa_supplicant
672 Integrating with pcmcia-cs/cardmgr scripts
675 wpa_supplicant needs to be running when using a wireless network with
709 started--and will then negotiate keys with the AP.
713 Optional integration with Xsupplicant
718 experimental interface for integrating it with Xsupplicant
719 (http://www.open1x.org/) for the WPA with EAP authentication.
728 configured with the network security policy. See Xsupplicant documents