Commit message (Collapse)AuthorAgeFilesLines
* Fix EAPOL supplicant port authorization with PMKSA cachingJouni Malinen2012-10-271-4/+1
| | | | | | | | | | | | | | | | | | | | | | | | The previous eapol_sm_notify_cached() implementation forced the port to be authorized when receiving EAPOL-Key msg 1/4 that included a matching PMKID in cases when PMKSA caching is used. This is too early since the port should really be authorized only after the PTK has been configured which is the case when PMKSA caching is not used. Fix this by using the EAPOL supplicant PAE state machine to go through the AUTHENTICATING and AUTHENTICATED states instead of forcing a jump to AUTHENTICATED without performing full state machine steps. This can be achieved simply by marking eapSuccess TRUE at least with the current version of EAP and EAPOL state machines (the earlier commits in this function seemed to indicate that this may have not been that easy in the older versions due to the hacks needed here). This addresses an issue with nl80211-based driver interface when the driver depends on the STA Authorized flag being used to prevent unprotected frames from being accepted (both TX and RX) prior to PTK configuration. Signed-hostap: Jouni Malinen <j@w1.fi> intended-for: hostap-1
* P2P: Allow all channels with multi-channel concurrencyJouni Malinen2012-10-264-24/+45
| | | | | | | | | | If the driver indicates support for multi-channel concurrency, change the p2p_connect behavior to not force the current operating channel, but instead, just mark it as preferred for GO Negotiation. This change applies only for the case when the freq parameter is not used with the p2p_connect command. Signed-hostap: Jouni Malinen <jouni@qca.qualcomm.com>
* Fix EAPOL processing when STA switches between multi-BSSesDavid Bird2012-10-251-3/+6
| | | | | | | | | | | | | | | | | | | | | There was an issue with EAPOL frame exchanges in a multi-BSS configuration when a station switches between the BSSes controlled by the same hostapd process. When processing the EAPOL packet, the array of virtual APs (iface->bss) is searched looking for the station that sent the packet in order to identify which signal context should be used during processing. The first match of the station in its list gets used in the ieee802_1x_receive() function. However, even after a station has disassociated, it remains in the list of stations pending an inactivity timeout. This leads to the wrong hapd context (one where the station had already disassociated) being used in some cases (if the current/active bss entry appears in the list after one where the station has just disassociated from) for EAPOL processing. Fix this by checking the WLAN_STA_ASSOC flag before assuming the right hapd context was found for the given station. Signed-hostap: David Bird <dbird@powercloudsystems.com> intended-for: hostap-1
* P2P: Add secondary device types into p2p_peer outputJouni Malinen2012-10-251-0/+13
| | | | | | | This allows the P2P_PEER command to be used to fetch the list of secondary device types that each P2P peer has advertised. Signed-hostap: Jouni Malinen <jouni@qca.qualcomm.com>
* nl80211: Add support for SAE operationsJouni Malinen2012-10-241-0/+13
| | | | | | | This uses the recent cfg80211 changes to allow SAE authentication to be implemented with the nl80211 driver interface. Signed-hostap: Jouni Malinen <j@w1.fi>
* Sync with linux/nl80211.h in wireless-testing.gitJouni Malinen2012-10-241-0/+48
| | | | Signed-hostap: Jouni Malinen <j@w1.fi>
* P2P: Improve robustness against lost ctrl::ack framesJouni Malinen2012-10-132-0/+24
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | P2P includes two use cases where one of the devices is going to start a group and likely change channels immediately after processing a frame. This operation may be fast enough to make the device leave the current channel before the peer has completed layer 2 retransmission of the frame in case the ctrl::ack frame was lost. This can result in the peer not getting TX status success notification. For GO Negotiation Confirm frame, p2p_go_neg_conf_cb() has a workaround that ignores the TX status failure and will continue with the group formation with the assumption that the peer actually received the frame even though we did not receive ctrl::ack. For Invitation Response frame to re-invoke a persistent group, no such workaround is used in p2p_invitation_resp_cb(). Consequently, TX status failure due to lost ctrl::ack frame results in one of the peers not starting the group. Increase the likelihood of layer 2 retransmission getting acknowledged and ctrl::ack being received by waiting a short duration after having processed the GO Negotiation Confirm and Invitation Response frames for the re-invocation case. For the former, use 20 ms wait since this case has been worked around in deployed devices. For the latter, use 50 ms wait to get even higher likelihood of getting ctrl::ack through since deployed devices (and the current wpa_supplicant implementation) do not have a workaround to ignore TX status failure. 20 ms is long enough to include at least couple of retries and that should increase likelihood of getting ctrl::ack through quite a bit. The longer 50 ms wait is likely to include full set of layer 2 retries. Signed-hostap: Jouni Malinen <jouni@qca.qualcomm.com>
* Fix regression in LEAPJouni Malinen2012-10-111-1/+4
| | | | | | | | | Commit 458cb3019108b6cb8c0c1cab94ae6ebf244eda27 broke LEAP since it rejects EAP-Success packet that is used within LEAP and this frame does not have a payload. Fix LEAP by relaxing the generic EAP packet validation if LEAP has been negotiated. Signed-hostap: Jouni Malinen <jouni@qca.qualcomm.com>
* WPS: Limit number of active wildcard PINs to oneJouni Malinen2012-10-101-0/+20
| | | | | | | | | | | Previously, WPS Registrar allowed multiple wildcard PINs to be configured. This can get confusing since these PINs get assigned to any Enrollee that does not have a specific PIN and as such, cannot really be used with different PIN values in reasonable ways. To avoid confusion with multiple enabled PINs, invalidate any previously configured wildcard PIN whenever adding a new one. Signed-hostap: Jouni Malinen <jouni@qca.qualcomm.com>
* WPS: Allow PIN timeout to be specified with wpa_supplicant AP/GOJouni Malinen2012-10-106-7/+27
| | | | | | | | Extend the wpa_cli wps_pin command to support specification of the PIN expiration time in seconds similarly to hostapd_cli wps_pin command when using wpa_supplicant for AP mode (including P2P GO). Signed-hostap: Jouni Malinen <jouni@qca.qualcomm.com>
* P2P: Allow P2P functionality to be disabled per interfaceJouni Malinen2012-10-104-1/+10
| | | | | | | | | | | | | | | | By default, P2P is enabled globally for all virtual interfaces and this makes wpa_supplicant include WSC and P2P IEs in Probe Request frames for all scans even if this is for a non-P2P station connection to speed up device discovery. If an interface is dedicated for non-P2P station mode operations, it is now possible to disable addition of WSC and P2P IEs into Probe Request frames with a per-interface p2p_disabled parameter. This can be set either in the configuration file (p2p_disabled=1) or at run time ("wpa_cli -i wlan0 set p2p_disabled 1"). Unlike the previous mechanism ("wpa_cli p2p_set disabled 1"), the new parameter changes the behavior only for the specified interface while other interfaces continue to follow the global P2P enabled/disabled state. Signed-hostap: Jouni Malinen <jouni@qca.qualcomm.com>
* Do not clear PMKSA cache on all network block parameter changesJouni Malinen2012-10-091-1/+3
| | | | | | | | | | | The bssid and priority parameters in a network block do not have any effect on the validity of a PMKSA cache entry, so avoid flushing the PMKSA cache when only these parameters are changed. This is mainly to allow forced roaming or network selection changes without causing a disconnection if the changes are done during RSN association that used EAP. Signed-hostap: Jouni Malinen <jouni@qca.qualcomm.com>
* Filter out unlikely "pre-shared key may be incorrect" messagesJouni Malinen2012-10-081-2/+23
| | | | | | | | | | | | | Add a function to filter out known cases of disconnection during 4-way handshake that are caused by something else than mismatch in PSK. This commit adds the case where the local end determines a mismatch in WPA/RSN element between Beacon/Probe Response frames and EAPOL-Key msg 3/4. This can avoid some potentially confusing "WPA: 4-Way Handshake failed - pre-shared key may be incorrect" ctrl_iface messages. Signed-hostap: Jouni Malinen <jouni@qca.qualcomm.com>
* EAP-TLS: Add extra validation for TLS Message LengthJouni Malinen2012-10-072-0/+15
| | | | | | | | | | | | While the existing code already addresses TLS Message Length validation for both EAP-TLS peer and server side, this adds explicit checks and rejection of invalid messages in the functions handling reassembly. This does not change externally observable behavior in case of EAP server. For EAP peer, this starts rejecting invalid messages instead of addressing them by reallocating the buffer (i.e., ignoring TLS Message Length in practice). Signed-hostap: Jouni Malinen <j@w1.fi>
* EAP-TLS server: Fix TLS Message Length validationJouni Malinen2012-10-071-0/+8
| | | | | | | | | | | | | | | | | | | | EAP-TLS/PEAP/TTLS/FAST server implementation did not validate TLS Message Length value properly and could end up trying to store more information into the message buffer than the allocated size if the first fragment is longer than the indicated size. This could result in hostapd process terminating in wpabuf length validation. Fix this by rejecting messages that have invalid TLS Message Length value. This would affect cases that use the internal EAP authentication server in hostapd either directly with IEEE 802.1X or when using hostapd as a RADIUS authentication server and when receiving an incorrectly constructed EAP-TLS message. Cases where hostapd uses an external authentication are not affected. Thanks to Timo Warns for finding and reporting this issue. Signed-hostap: Jouni Malinen <j@w1.fi> intended-for: hostap-1
* SAE: Add Finite Cyclic Group negotiation and Send-ConfirmJouni Malinen2012-10-064-17/+170
| | | | | | | | This replaces the previously used bogus test data in SAE messages with the first real field. The actual SAE authentication mechanism is still missing and the Scaler, Element, and Confirm fields are not included. Signed-hostap: Jouni Malinen <j@w1.fi>
* P2P: Fix network removal on P2P connect to select correct blockJouni Malinen2012-10-051-1/+1
| | | | | | | | | | | If wpa_s->current_ssid is not set (e.g., after disconnection that did not result in immediate group removal), an incorrect group could have been removed since the network block iteration here could select the network block that is used to store persistent group credentials. Fix this by verifying that disabled != 2 to avoid picking the network block that could not have been the temporary P2P group. Signed-hostap: Jouni Malinen <jouni@qca.qualcomm.com>
* WPS: Reenable the networks disabled during wpa_wpas_reassocSunil Dutt2012-10-042-2/+55
| | | | | | | | During the association for the WPS handshake all the other configured networks are disabled. This patch makes wpa_supplicant reenable the disabled networks after the success/failure of the WPS handshake. Signed-hostap: Sunil Dutt Undekari <duttus@codeaurora.org>
* 60 GHz: Fix error while processing scan resultsVladimir Kondratiev2012-10-041-1/+1
| | | | | | | | Channel frequency for 60 GHz band do not fit into 'short int', as was used. Expand it to 'int' Signed-off-by: Vladimir Kondratiev <qca_vkondrat@qca.qualcomm.com> Signed-hostap: Jouni Malinen <jouni@qca.qualcomm.com>
* Interworking: Unshare ANQP results on explicit ANQP requestsJouni Malinen2012-10-034-2/+61
| | | | | | | | | When ANQP_GET or HS20_ANQP_GET is used to request ANQP information, unshare the ANQP information (i.e., create a per-BSS copy of it) to make sure the information from the specified BSS is available in case the APs provide different information within HESSID. Signed-hostap: Jouni Malinen <jouni@qca.qualcomm.com>
* HS 2.0: Include parsed WAN Metrics in RX-HS20-ANQP eventJouni Malinen2012-10-031-2/+9
| | | | | | | | | | | | | | | | | | | | | This adds parsed version of WAN Metrics information to the control event message as follows: RX-HS20-ANQP 02:00:00:00:01:00 WAN Metrics 01:8000:1000:80:240:3000 format: <WAN Info>:<DL Speed>:<UL Speed>:<DL Load>:<UL Load>:<LMD> WAN Info: B0-B1: Link Status, B2: Symmetric Link, B3: At Capabity (encoded as two hex digits) Downlink Speed: Estimate of WAN backhaul link current downlink speed in kbps; 1..4294967295; 0 = unknown Uplink Speed: Estimate of WAN backhaul link current uplink speed in kbps 1..4294967295; 0 = unknown Downlink Load: Current load of downlink WAN connection (scaled to 255 = 100%) Uplink Load: Current load of uplink WAN connection (scaled to 255 = 100%) Load Measurement Duration: Duration for measuring downlink/uplink load in tenths of a second (1..65535); 0 if load cannot be determined Signed-hostap: Jouni Malinen <jouni@qca.qualcomm.com>
* WPS: Fix a potential memory leak on wps_init() error pathJouni Malinen2012-10-021-0/+1
| | | | Signed-hostap: Jouni Malinen <jouni@qca.qualcomm.com>
* Fix build without CONFIG_WPS=yJouni Malinen2012-10-011-1/+1
| | | | | | | | | Commit 620c783753bddd37988269314862dc7e4a62f700 modified wpas_wps_ssid_bss_match() prototype but forgot to update the non-WPS wrapper inline function. Fix that to match with the new bss parameter type. Signed-hostap: Jouni Malinen <jouni@qca.qualcomm.com>
* P2P: Add a conf parameter to start a GO as HT40 if allowedArik Nemtsov2012-09-304-3/+16
| | | | | | | | | | When specified in the conf file this parameter will make all invocations of p2p_group_add, p2p_connect, and p2p_invite behave as if "ht40" has been specified on the command line. This shouldn't do harm since regulatory constraints and driver capabilities are consulted anyway before starting HT40 mode. Signed-hostap: Arik Nemtsov <arik@wizery.com>
* Reserve AKM and cipher suite valuesJouni Malinen2012-09-307-4/+60
| | | | | | | | These values are used with WAPI and CCX and reserving the definitions here reduces the number of merge conflicts with repositories that include these functions. Signed-hostap: Jouni Malinen <j@w1.fi>
* Add initial parts for SAEJouni Malinen2012-09-3019-8/+301
| | | | | | | | | | | | | This introduces new AKM for SAE and FT-SAE and adds the initial parts for going through the SAE Authentication frame exchange. The actual SAE algorithm and new fields in Authentication frames are not yet included in this commit and will be added separately. This version is able to complete a dummy authentication with the correct authentication algorithm and transaction values to allow cfg80211/mac80211 drivers to be tested (all the missing parts can be handled with hostapd/wpa_supplicant changes). Signed-hostap: Jouni Malinen <j@w1.fi>
* Sync with linux/nl80211.h in wireless-testing.gitJouni Malinen2012-09-301-4/+50
| | | | Signed-hostap: Jouni Malinen <j@w1.fi>
* dbus: Add global capabilities propertyDan Williams2012-09-293-0/+46
| | | | | | | | | | | | Otherwise it's difficult to determine if the supplicant was built with CONFIG_AP, CONFIG_IBSS_RSN, CONFIG_P2P, etc. CONFIG_AP and CONFIG_P2P can be inferred from the introspection data of the Interface object, but CONFIG_IBSS_RSN does not change the introspection data at all and thus it's impossible to determine whether the supplicant supports it without knowing its compile-time options. Signed-hostap: Dan Williams <dcbw@redhat.com> intended-for: hostap-1
* nl80211: Don't send BSSID with disconnect commandMykyta Iziumtsev2012-09-291-57/+10
| | | | | | | NL80211_CMD_DISCONNECT doesn't need BSSID, because cfg80211 uses locally saved value. Signed-hostap: Mykyta Iziumtsev <mykyta.iziumtsev@gmail.com>
* P2P: Fix p2p_cancel processing during group formationJouni Malinen2012-09-281-0/+4
| | | | | | | | | | The wpa_s->p2p_in_provisioning flag did not get cleared in some cases where p2p_cancel command is used to stop group formation. This can result in some operations (like p2p_find) failing afterwards. Fix this by using wpas_group_formation_completed() when processing p2p_cancel for a group that has not yet completed group formation. Signed-hostap: Jouni Malinen <jouni@qca.qualcomm.com>
* Interworking: Support Android JB keystore with EAP-TLSJouni Malinen2012-09-281-0/+11
| | | | | | | If the keystore:// prefix is used in the private_key entry, convert that to the OpenSSL engine style configuration used for Android JB keystore. Signed-hostap: Jouni Malinen <jouni@qca.qualcomm.com>
* Interworking: Fix failed GAS query processingJouni Malinen2012-09-281-0/+1
| | | | | | | | The pending GAS entry must be removed from the list when it is removed. This fixes an issue with potential segfault due to freed memory being accessed if the driver fails to accept a GAS query. Signed-hostap: Jouni Malinen <jouni@qca.qualcomm.com>
* Add disallow_aps parameter to disallow BSSIDs/SSIDsJouni Malinen2012-09-274-0/+194
| | | | | | | | | | | | | | | | | | | | | | | External programs can use this new parameter to prevent wpa_supplicant from connecting to a list of BSSIDs and/or SSIDs. The disallowed BSSes will still be visible in scan results and it is possible to run ANQP operations with them, but BSS selection for connection will skip any BSS that matches an entry in the disallowed list. The new parameter can be set with the control interface SET command using following syntax: SET disallow_aps <disallow_list> disallow_list ::= <ssid_spec> | <bssid_spec> | <disallow_list> | “” SSID_SPEC ::= ssid <SSID_HEX> BSSID_SPEC ::= bssid <BSSID_HEX> For example: wpa_cli set disallow_list "ssid 74657374 bssid 001122334455 ssid 68656c6c6f" wpa_cli set disallow_list (the empty value removes all entries) Signed-hostap: Jouni Malinen <jouni@qca.qualcomm.com>
* Include connected time in AP mode STA-* commandsRaja Mani2012-09-264-2/+34
| | | | | | | This allows hostapd_cli and wpa_cli all_sta command to be used to display connected time (in seconds) of each station in AP mode. Signed-hostap: Raja Mani <rmani@qca.qualcomm.com>
* P2P: Fix ignoring of PD Response due to dialog token mismatchJouni Malinen2012-09-251-5/+5
| | | | | | | | | | | | | | | Commit 6b56cc2d97fe9efd1feea8d418714b4658b056f1 added clearing of the p2p->pending_action_state too early in this function. This should not be done if we are going to silently ignore the frame due to dialog token mismatch. Fix this by moving the code around to check the dialog token first. This issue resulted in PD Request retries getting stopped too early if the peer is sending out an unexpected PD Response (e.g., because of it being excessively slow with the response so that the response is received only after the next TX attempt with a new dialog token). Signed-hostap: Jouni Malinen <jouni@qca.qualcomm.com>
* P2P: Clear sta_scan_pending on group removalJouni Malinen2012-09-241-0/+1
| | | | | | | | | | | | | It is possible for the P2P client group to be removed while waiting for a pending scan operation (e.g., when p2p_group_idle timeout hits after getting disconnected from the GO with something else than Deauthentication with reason code 3). If this happens with a P2P interface that is used both for P2P Device and group roles, scan state could get stuck while waiting for the next scan to complete since no more station (P2P client) mode scans are scheduled. Fix this by clearing sta_scan_pending when removing the temporary group network block. Signed-hostap: Jouni Malinen <jouni@qca.qualcomm.com>
* P2P: Allow peer to propose channel in invitation processJouni Malinen2012-09-244-10/+80
| | | | | | | | | | | | | | Make Invitation process for re-invoking a persistent group behave similarly to GO Negotiation as far as channel negotiation is concerned. The Operating Channel value (if present) is used as a starting point if the local device does not have a forced operating channel (e.g., due to concurrent use). Channel lists from devices are then compared to check that the selected channel is in the intersection. If not, channel is selected based on GO Negotiation channel rules (best channel preferences etc.). Invitation Request is rejected if no common channel can be selected. Signed-hostap: Jouni Malinen <jouni@qca.qualcomm.com>
* P2P: Show own channel list in debug logJouni Malinen2012-09-241-1/+2
| | | | | | This makes it easier to debug channel negotiation mechanisms. Signed-hostap: Jouni Malinen <jouni@qca.qualcomm.com>
* P2P: Fix pending-sta-scan processing for concurrent operation casesJouni Malinen2012-09-242-1/+8
| | | | | | | | | | | | | | | | | If two P2P_FIND commands and a station mode SCAN command are issued in a sequence with the second P2P_FIND and SCAN commands started before the initial scan from the first P2P_FIND command has completed, sta_scan_pending may be left set without an automatic way of getting it cleared. This can get P2P search stuck if no further station mode scan operations are run. Fix this by clearing the sta_scan_pending flag whenever station mode scans are stopped due to no enabled networks resulting in INACTIVE mode getting entered. In addition, avoid setting sta_scan_pending flag when a special scan_res_handler is set so that this does not get enabled on the P2P Device interface during a P2P search operation. Signed-hostap: Jouni Malinen <jouni@qca.qualcomm.com>
* P2P: Add more debug prints for GO start routinesJouni Malinen2012-09-233-4/+24
| | | | | | This makes it easier to debug issues in starting GO mode. Signed-hostap: Jouni Malinen <j@w1.fi>
* Add debug print for no-enabled-networks caseJouni Malinen2012-09-231-1/+7
| | | | | | | | If there are any disabled networks, show a debug print with the count of those networks when no enabled networks are found. This can be helpful in trying to figure out why scans are being skipped. Signed-hostap: Jouni Malinen <j@w1.fi>
* Print control interface commands in easier formatJouni Malinen2012-09-231-0/+1
| | | | | | | | | | The ASCII hexdump is somewhat difficult to search for (especially on Android builds), so make the debug log easier to parse by printing the full control interface command as a text string. In addition, use wpa_dbg() to get the interface name printed so that multi-interface cases can be debugged. Signed-hostap: Jouni Malinen <j@w1.fi>
* P2P: Fix PSK configuration for GO networkJouni Malinen2012-09-231-0/+7
| | | | | | | | | | | | | | | | | | | Setting just ssid->passphrase is not enough to complete the network block for the GO entry. Also the PSK needs to be derived so that the network is considered enabled by wpas_network_disabled(). The previous version worked as long as something else allowed the scan request to be performed (this is needed even though the actual scan is skipped when starting GO). The first GO start was allowed because wpa_s->scan_req is initialized to 1 in wpa_supplicant_alloc(). However, other attempts may fail if wpa_s->scan_req is cleared. This failure shows up as "No enabled networkas - do not scan" in debug log followed by state change to INACTIVE when trying to start GO. Fix this by deriving PSK from the passphrase for GO mode. Signed-hostap: Jouni Malinen <j@w1.fi>
* P2P: Fix p2p_group_idle in no-group-interface P2P client caseJouni Malinen2012-09-231-4/+3
| | | | | | | | | | | | | | | | | | Commit 30ee769235f3170d9bf6b62c11c6e018e97deb84 started skipping P2P group removal if wpa_s->current_ssid is not set and commit 0d30cc240fa36905b034dc9676f9d8da0ac18e56 started clearing wpa_s->current_ssid on disconnection. This combination broke p2p_group_idle timeout on P2P client interface in a case where no separate P2P group interface is used and when the disconnection is triggered by something else than an explicit indication of GO terminating the group. Fix this by relaxing network block matching rules when figuring out whether any of the configured network blocks could be in P2P use. The p2p_group flag alone should be enough for this since temporary P2P group network blocks are removed once the P2P group is terminated. Signed-hostap: Jouni Malinen <j@w1.fi>
* wpa_supplicant: Set state to DISCONNECTED on AP creation errorsDan Williams2012-09-231-1/+4
| | | | | | | | | | If the AP creation failed (missing freq= or driver error) the supplicant would previously stay in SCANNING state forever. Instead, it should handle the error a bit better and drop back to DISCONNECTED so clients know something went wrong. Signed-hostap: Dan Williams <dcbw@redhat.com> intended-for: hostap-1
* nl80211: Use the monitor interface if socket tx status is not supportedFelix Fietkau2012-09-231-3/+3
| | | | | | Fixes hostapd on recent compat-wireless builds with older kernels. Signed-hostap: Felix Fietkau <nbd@openwrt.org>
* hostapd: Add check for the wds sta flag before creating 4addr VLANsFelix Fietkau2012-09-231-0/+3
| | | | Signed-hostap: Felix Fietkau <nbd@openwrt.org>
* hostapd: Clear WLAN_STA_ASSOC_REQ_OK if sending the assoc response failedFelix Fietkau2012-09-231-12/+13
| | | | | | | | | As long as WLAN_STA_ASSOC_REQ_OK is set in sta->flags, Class 3 frames do not trigger a disassoc/deauth. If it is still set even after the assoc response tx has already failed, it may take somewhat longer for clients to realize that the connection wasn't fully established. Signed-hostap: Felix Fietkau <nbd@openwrt.org>
* P2P: Remove channel 14 from supported P2P channelsMykyta Iziumtsev2012-09-231-1/+0
| | | | | | | | | | | | Channel 14 is available only in Japan and is DSSS-only according to IEEE 802.11-2012 19.4.3 and MIC Equipment Ordinance (EO) for Regulating Radio Equipment article 49.20. At the same time, P2P should avoid using DSSS modulation in normal operation according to P2P specification v1.2 2.4.1. Signed-hostap: Mykyta Iziumtsev <mykyta.iziumtsev@gmail.com> intended-for: hostap-1
* hostapd: Send EAPOL frames from the VO queue if WMM is activeFelix Fietkau2012-09-161-2/+2
| | | | | | | This avoids extra latency caused by establishing an aggregation session and makes the initial connection attempt more reliable Signed-hostap: Felix Fietkau <nbd@openwrt.org>