| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
| |
Bug: 117508900
Change-Id: I4889513c0671ff2b689f1beca8084d6f149d473d
Test: Existing tests pass
(cherry picked from commit 29d54b87f121c79d5df87b0b2bcd7a1eb6090c1f)
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
ieee802_11_rx_wnmsleep_req() might be called for a short frame that has
no more payload after the Public Action field, i.e., with len == 0. The
bounds checking for the payload length was done only for the information
elements while the one octet Dialog Token field was read
unconditionally. This could result in reading one octet beyond the end
of the received frame data.
Depending on driver interface specific mechanism used for fetching the
frame, this could result in reading one octet beyond the end of a
stack/hash buffer or reading an uninitialized octet from within a
buffer. The actual value that was read as the Dialog Token field is not
used since the function returns immediately after having read this value
when there is no information elements following the field.
This issue was initially added in commit d32d94dbf47a ("WNM: Add
WNM-Sleep Mode implementation for AP") (with CONFIG_IEEE80211V=y build
option) and it remained in place during number of cleanup and fix
changes in this area and renaming of the build parameter to
CONFIG_WNM=y. The impacted function was not included in any default
build without one of the these optional build options being explicitly
enabled. CONFIG_WNM=y is still documented as "experimental and not
complete implementation" in hostapd/defconfig. In addition, commit
114f2830d2c2 ("WNM: Ignore WNM-Sleep Mode Request in wnm_sleep_mode=0
case") made this function exit before the impact read if WNM-Sleep Mode
support was not explicitly enabled in runtime configuration
(wnm_sleep_mode=1 in hostapd.conf).
Fix this by explicitly checking the frame has enough payload before
reading the Dialog Token field.
Bug: 111893132
Change-Id: I4b61e22c39d1a5683923eff34e43bb0c509913d4
Merged-In: I4b61e22c39d1a5683923eff34e43bb0c509913d4
Signed-off-by: Jouni Malinen <jouni@codeaurora.org>
(cherry picked from commit 7a543744db8ece2376b019040b5668ede68ebd8b)
CVE-2018-9589
|
|
|
|
|
|
|
|
|
|
| |
The Setup Response timer is relatively fast (500 ms) and there are
instances where it fires on the responder side after the initiator has
already sent out the TDLS Setup Confirm frame. Prevent the processing of
this stale TDLS Setup Response frame on the initiator side.
Change-Id: I595f41dc803d6707ee8d0ea220f594cce750139a
Signed-off-by: Arik Nemtsov <arikx.nemtsov@intel.com>
|
|
|
|
|
|
|
|
|
|
| |
Instead of setting the default PMK length for the cleared PMK, set the
length to 0 and explicitly check for this when deriving PTK to avoid
unexpected key derivation with an all-zeroes key should it be possible
to somehow trigger PTK derivation to happen before PMK derivation.
Change-Id: Ifef3b2ca5ee19e6e89df75fef697e7215f926cb1
Signed-off-by: Jouni Malinen <j@w1.fi>
|
|
|
|
|
|
|
|
| |
This makes it easier to understand the cases where PMK gets configured
based on information from upper layer call (e.g., a PSK).
Change-Id: Ic7cbb18ed37de89d7378503c6b3d0f1da63db4dd
Signed-off-by: Jouni Malinen <j@w1.fi>
|
|
|
|
|
|
|
|
|
|
|
|
| |
Currently, reinstallations of the PTK are prevented by (1) assuring the
same TPTK is only set once as the PTK, and (2) that one particular PTK
is only installed once. This patch makes it more explicit that point (1)
is required to prevent key reinstallations. At the same time, this patch
hardens wpa_supplicant such that future changes do not accidentally
break this property.
Change-Id: Id03f4790d93deb1bc34b1055fb85ec80c5229bcc
Signed-off-by: Mathy Vanhoef <Mathy.Vanhoef@cs.kuleuven.be>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This was originally added to allow the IEEE 802.11 protocol to be
tested, but there are no known fully functional implementations based on
this nor any known deployments of PeerKey functionality. Furthermore,
PeerKey design in the IEEE Std 802.11-2016 standard has already been
marked as obsolete for DLS and it is being considered for complete
removal in REVmd.
This implementation did not really work, so it could not have been used
in practice. For example, key configuration was using incorrect
algorithm values (WPA_CIPHER_* instead of WPA_ALG_*) which resulted in
mapping to an invalid WPA_ALG_* value for the actual driver operation.
As such, the derived key could not have been successfully set for the
link.
Since there are bugs in this implementation and there does not seem to
be any future for the PeerKey design with DLS (TDLS being the future for
DLS), the best approach is to simply delete all this code to simplify
the EAPOL-Key handling design and to get rid of any potential issues if
these code paths were accidentially reachable.
Change-Id: I10294a9ef31c46a27416a6063255939dcedc57d5
Signed-off-by: Jouni Malinen <j@w1.fi>
|
|
|
|
|
|
|
|
|
| |
This allows ext_mgmt_frame_handling=1 cases with hostapd to process TX
status events based on external processing. This is useful for increased
test coverage of management frame processing.
Change-Id: I056ec2a06334762245dfcb8261b9427e818ef52c
Signed-off-by: Jouni Malinen <j@w1.fi>
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The driver is expected to not report a second association event without
the station having explicitly request a new association. As such, this
case should not be reachable. However, since reconfiguring the same
pairwise or group keys to the driver could result in nonce reuse issues,
be extra careful here and do an additional state check to avoid this
even if the local driver ends up somehow accepting an unexpected
Reassociation Response frame.
Change-Id: Ie76301550e96bfcfe252d874f2e83deb0aeb9533
Signed-off-by: Jouni Malinen <j@w1.fi>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Do not try to reconfigure the same TPK-TK to the driver after it has
been successfully configured. This is an explicit check to avoid issues
related to resetting the TX/RX packet number. There was already a check
for this for TPK M2 (retries of that message are ignored completely), so
that behavior does not get modified.
For TPK M3, the TPK-TK could have been reconfigured, but that was
followed by immediate teardown of the link due to an issue in updating
the STA entry. Furthermore, for TDLS with any real security (i.e.,
ignoring open/WEP), the TPK message exchange is protected on the AP path
and simple replay attacks are not feasible.
As an additional corner case, make sure the local nonce gets updated if
the peer uses a very unlikely "random nonce" of all zeros.
Change-Id: I84131f30c358f27aaf6277e8957d165bca5102aa
Signed-off-by: Jouni Malinen <j@w1.fi>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The Authenticator state machine path for PTK rekeying ended up bypassing
the AUTHENTICATION2 state where a new ANonce is generated when going
directly to the PTKSTART state since there is no need to try to
determine the PMK again in such a case. This is far from ideal since the
new PTK would depend on a new nonce only from the supplicant.
Fix this by generating a new ANonce when moving to the PTKSTART state
for the purpose of starting new 4-way handshake to rekey PTK.
Change-Id: I7887f36a0f9e7710bc40fbe5014ea8867d7f5f72
Signed-off-by: Jouni Malinen <j@w1.fi>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Properly track whether a PTK has already been installed to the driver
and the TK part cleared from memory. This prevents an attacker from
trying to trick the client into installing an all-zero TK.
This fixes the earlier fix in commit
ad00d64e7d8827b3cebd665a0ceb08adabf15e1e ('Fix TK configuration to the
driver in EAPOL-Key 3/4 retry case') which did not take into account
possibility of an extra message 1/4 showing up between retries of
message 3/4.
Change-Id: I6b5f6f2a1c0495575eb5a1576462768ddc89f09c
Signed-off-by: Mathy Vanhoef <Mathy.Vanhoef@cs.kuleuven.be>
|
|
|
|
|
|
|
|
|
|
|
| |
This extends the protection to track last configured GTK/IGTK value
separately from EAPOL-Key frames and WNM-Sleep Mode frames to cover a
corner case where these two different mechanisms may get used when the
GTK/IGTK has changed and tracking a single value is not sufficient to
detect a possible key reconfiguration.
Change-Id: I6c377809a8590e7a6f2c1c87017d666b82602ad4
Signed-off-by: Jouni Malinen <j@w1.fi>
|
|
|
|
|
|
|
|
|
|
|
| |
Track the current GTK and IGTK that is in use and when receiving a
(possibly retransmitted) Group Message 1 or WNM-Sleep Mode Response, do
not install the given key if it is already in use. This prevents an
attacker from trying to trick the client into resetting or lowering the
sequence counter associated to the group key.
Change-Id: Ib0565e90e62115cc91ac36be3dae3b064e1baa1e
Signed-off-by: Mathy Vanhoef <Mathy.Vanhoef@cs.kuleuven.be>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Do not reinstall TK to the driver during Reassociation Response frame
processing if the first attempt of setting the TK succeeded. This avoids
issues related to clearing the TX/RX PN that could result in reusing
same PN values for transmitted frames (e.g., due to CCM nonce reuse and
also hitting replay protection on the receiver) and accepting replayed
frames on RX side.
This issue was introduced by the commit
0e84c25434e6a1f283c7b4e62e483729085b78d2 ('FT: Fix PTK configuration in
authenticator') which allowed wpa_ft_install_ptk() to be called multiple
times with the same PTK. While the second configuration attempt is
needed with some drivers, it must be done only if the first attempt
failed.
Change-Id: I45909184ad3dc8f3f608ce99ee853f3551323458
Signed-off-by: Mathy Vanhoef <Mathy.Vanhoef@cs.kuleuven.be>
|
|
|
|
|
|
|
|
|
|
|
|
| |
P802.11i/D3.0 described the Key Length as having value 16 for the group
key handshake. However, this was changed to 0 in the published IEEE Std
802.11i-2004 amendment (and still remains 0 in the current standard IEEE
Std 802.11-2016). We need to maintain the non-zero value for WPA (v1)
cases, but the RSN case can be changed to 0 to be closer to the current
standard.
Change-Id: I96d654977f7e801a8993d017dad7465cc4aba758
Signed-off-by: Jouni Malinen <j@w1.fi>
|
|\
| |
| |
| |
| |
| | |
git://codeaurora.org/platform/external/wpa_supplicant_8 into cm-13.0
Change-Id: I110d3aa8efe7861b7a5b0dd570bfe5b0ec88e6be
|
| |\
| | |
| | |
| | | |
wlan-service.lnx.1.0-dev.1.0
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
This new parameter allows hostapd to add Vendor Specific elements into
(Re)Association Response frames similarly to the way vendor_elements
parameter can be used for Beacon and Probe Response frames.
Git-commit: a9112270615dd68d422623ebc26c21a6887a2a11
Git-repo : git://w1.fi/srv/git/hostap.git
Signed-off-by: Jouni Malinen <jouni@qca.qualcomm.com>
Change-Id: I033aced040c894f4dc4791c4e5081135976ebd0c
CRs-Fixed: 1003412
|
| |/
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Add Transmit Power Envelope element defined in IEEE P802.11-REVmc/D4.3,
8.4.2.161.
Git-commit: 3c417499e71b0c7f2dfae69fb1b67eb31e467ba6
Git-repo : git://w1.fi/srv/git/hostap.git
CRs-Fixed: 979946
Change-Id: Ib3e11ee78cbe8e4d875d6c43dc2ec5539043fdb1
Signed-off-by: Rajkumar Manoharan <rmanohar@qti.qualcomm.com>
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This was previously handled for the case where the non-success
Invitation Response frame was sent out during the Listen phase. However,
in the case the Action frame TX ended up getting scheduled when the
Search phase scan had already started (e.g., due to the driver reporting
Invitation Request RX late enough for the Listen-to-Search transition
having already started), the postponed Action frame TX status processing
did not cover the specific case of non-success Invitation Response. This
could result in the p2p_find operation getting stopped (stuck in SEARCH
state) unexpectedly
Fix this by calling p2p_check_after_scan_tx_continuation() from
Invitation Response TX callback handler if the invitation was rejected.
CRs-Fixed: 1002261
Git-commit: 3433721c5f9073c0d45c1109b825f1dcbabbf517
Git-repo : git://w1.fi/srv/git/hostap.git
Signed-off-by: Jouni Malinen <jouni@qca.qualcomm.com>
Change-Id: Ic045516f31520fbe8ba068c88fe247df1746f29a
|
| |\
| | |
| | |
| | | |
wlan-service.lnx.1.0-dev.1.0
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Parent thread exits when daemonize. This will cause child threads
to die and eap_proxy_post_init is not executed
To fix this, child thread should be created after demonize
Change-Id: Ibd9e3dc79cb1a7650b3adc55afdc95818a2e011b
CRs-Fixed: 1032710
|
| |\ \
| | | |
| | | |
| | | | |
wlan-service.lnx.1.0-dev.1.0
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Spurious newlines output while writing the config file can corrupt the
wpa_supplicant configuration. Avoid writing these for the network block
parameters. This is a generic filter that cover cases that may not have
been explicitly addressed with a more specific commit to avoid control
characters in the psk parameter.
Signed-off-by: Paul Stewart <pstew@google.com>
Git-commit: 0fe5a234240a108b294a87174ad197f6b5cb38e9
Git-repo: git://w1.fi/srv/git/hostap.git
Change-Id: I35e8483bdda5c391b95da42c2f577d5e9217f2e2
CRs-fixed: 1007548
|
| |\| |
| | |/
| |/|
| | | |
wlan-service.lnx.1.0-dev.1.0
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
WPA/WPA2-Personal passphrase is not allowed to include control
characters. Reject a Credential received from a WPS Registrar both as
STA (Credential) and AP (AP Settings) if the credential is for WPAPSK or
WPA2PSK authentication type and includes an invalid passphrase.
This fixes an issue where hostapd or wpa_supplicant could have updated
the configuration file PSK/passphrase parameter with arbitrary data from
an external device (Registrar) that may not be fully trusted. Should
such data include a newline character, the resulting configuration file
could become invalid and fail to be parsed.
Signed-off-by: Jouni Malinen <jouni@qca.qualcomm.com>
Git-commit: ecbb0b3dc122b0d290987cf9c84010bbe53e1022
Git-repo: git://w1.fi/srv/git/hostap.git
Change-Id: I2b439a72af08a744ce5bf74a05b2cac817fe5b05
CRs-fixed: 1007548
|
| |/
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Commit 0603bcb7fe8babf183362518238c142afe8e2036 ('hostapd: Process MAC
ACLs on a station association event (SME in driver)') processes MAC ACL
on a station association event for drivers which use AP SME offload but
does not consider the scenario where the drivers offload ACL. This can
result in station disconnection, though the driver accepts the
connection. Address this by avoiding the hostapd ACL check for the
drivers offloading MAC ACL.
CRs-Fixed: 1031991
Git-commit: bb4e19e3f4c9d1973279b3b768bc0539ee7cb962
Git-repo : git://w1.fi/srv/git/hostap.git
Change-Id: I2934fbf676c803059e62ba2436c1181efb05a294
Signed-off-by: Jouni Malinen <jouni@qca.qualcomm.com>
|
| |
| |
| |
| |
| |
| |
| | |
* Not all branches support the new QMI invocations, so add
self-detection to deal with this.
Change-Id: Iff2c060505727cefab62715baaf82394257122ce
|
| |
| |
| |
| | |
Change-Id: I1e0259aad8516c8eacf50de6313a558f01032ae4
|
|/
|
|
|
|
|
|
|
|
| |
This code can't be built without linking to some proprietary libs
and headers. Split it off so a prebuilt can be distributed for
OSS builds
Ref: CYNGNOS-428
Change-Id: I430dda72e8cb156d86ef286244230bb3f511ca23
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Added support to disable ht2040 coex, New parameter
"ht2040_coex_disable" is added in hostapd.conf file
for disabling ht2040 coex. By default, HT2040 coex
is enabled, if user wants to disable, ht2040_coex_disable
can be set to 1.
Eg. ht2040_coex_disable=1 /* disable ht2040 coex */
ht2040_coex_disable=0 /* default,enable ht2040 coex */
Change-Id: Id460ff592648f2afb4ffec373badb7f6004b67f3
CRs-fixed: 681619
|
|
|
|
|
|
|
|
|
|
|
| |
This allows scans to be optimized when a response is needed only from a
single, known BSS.
Signed-off-by: Jouni Malinen <jouni@qca.qualcomm.com>
Git-commit: eb20cea590f1020835f09103d0290a0a7e7d5ada
Git-repo: git://w1.fi/srv/git/hostap.git
Change-Id: Ia449479732f6a15a78c9aabf821accf201970acf
CRs-Fixed: 996616
|
|
|
|
|
|
|
|
|
|
| |
earlier QMI message QMI_AUTH_SEND_EAP_PACKET_REQ can allow an eap
request packet size of only 256 bytes. Use new msg QMI_AUTH_EAP_
REQ_PACKET_EXT(supports max 4096 bytes) to send larger packets to
QMI.
Change-Id: I833a1b9e232485f3a7987ab824b88832cfd0821b
CRs-Fixed: 992076
|
|\
| |
| |
| | |
wlan-service.lnx.1.0-dev.1.0
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Trigger an event when wpa_supplicant accepts an invitation to re-invoke
a persistent group. Previously wpa_supplicant entered group formation
without triggering any specific events and it could confuse clients,
especially when operating with a driver that does not support
concurrency between P2P and infrastructure connection.
Change-Id: I8a8773d60adb4c69dc723281737a378b9dc7dd6e
Signed-off-by: Lior David <qca_liord@qca.qualcomm.com>
Git-commit: 0ee89250982cd3d424952d88cdc2f5c52e500a81
Git-repo: git://w1.fi/srv/git/hostap.git
CRs-Fixed: 985990
|
|/
|
|
|
|
|
|
|
| |
In eap_proxy_getKey(), instead of assigning(=) a NULL to key,
equalto(==) operator is used. This patch will modify it to use
the correct operator
Change-Id: I7d68543316266c311e5cc2ea5647601eb5dc1457
CRs-Fixed: 1005437
|
|\
| |
| |
| | |
wlan-service.lnx.1.0-dev.1.0
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Upon receiving FST setup request on old band, the peer is searched on
new band. The assumption is that MB IE from this peer on new band
previously received either in assoc event or in FST setup request.
There are cases in which above assumption doesn't work, peer is not
found and session setup fails. For example:
- STA connects over 11ac. Due to driver limitation, MB IE is not included
in assoc event
- STA connects over 11ad. MB IE included in assoc event.
- FST session established on 11ac band, with AP as initiator. i.e. FST
setup request sent in AP=>STA direction. STA searches for peer's (AP)
MB IE on 11ad band which exists.
- FST switch occur
- FST session established on 11ad band, with STA as initiator. i.e. FST
setup request sent in STA=>AP direction. AP searches for peer's (STA)
MB IE on 11ac band which are absent.
For fixing the above, consider also peers without MB IE as candidates in
the search algorithm.
Change-Id: I3db41951aeec860fef9a1abf9fe78fabef269999
Signed-off-by: Dedy Lansky <qca_dlansky@qca.qualcomm.com>
Git-commit: cc1af6faed963a33809c6bcd4b590c44a64b0d96
Git-repo: git://w1.fi/srv/git/hostap.git
CRs-Fixed: 987506
|
|\|
| |
| |
| | |
wlan-service.lnx.1.0-dev.1.0
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
STT guards the exchange of FST Action frames with the peer station.
It was observed that sometimes Action frames sending is delayed at
driver/FW layers for few hundreds millisec.
Enlarge the STT to overcome such cases.
Change-Id: I3ad7392cd725e2a26babd8dec83faae85e260739
Signed-off-by: Dedy Lansky <qca_dlansky@qca.qualcomm.com>
Git-commit: 0147afa9dfb03ee9f97101dc29bee178990d52a2
Git-repo: git://w1.fi/srv/git/hostap.git
CRs-Fixed: 987544
|
|\|
| |
| |
| | |
wlan-service.lnx.1.0-dev.1.0
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Inside management frame TX status callback, print the TX result where it
was missing. This is useful for debugging management frames drops.
Change-Id: Id104953efd981992b931c0c3cf0b565338ac422b
Signed-off-by: Dedy Lansky <qca_dlansky@qca.qualcomm.com>
Git-commit: 077dcfb8c48d2509a6e116c0de3ad57d2fbfe4fe
Git-repo: git://w1.fi/srv/git/hostap.git
CRs-Fixed: 987544
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
In the 60 GHz band, service discovery management frames are sent over
the control PHY and have a smaller maximum frame size (IEEE Std
802.11ad-2012, 21.4.3.2). Fix the code to use sufficiently small
fragment size when operating in the 60 GHz band.
The 60 GHz fragment size (928) is derived from the maximum frame size
for control PHY (1023) and subtracting 48 bytes of header size, and some
spare so we do not reach frames with the absolute maximum size.
Change-Id: I80ccbdc1a8a66e921a2da28f8ddb9487064f7dc0
Signed-off-by: Lior David <qca_liord@qca.qualcomm.com>
Git-commit: e4a1469cecee8d21044fb6e97f85aa807f498b62
Git-repo: git://w1.fi/srv/git/hostap.git
CRs-Fixed: 985990
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
When building P2P IE for Probe Request frames in P2P scan, add the
device information attribute if the 60 GHz band is included in the scan,
since this is required by the P2P specification.
Change-Id: Ib4439786cc1297859234e0b0661e7c1b5576c896
Signed-off-by: Lior David <qca_liord@qca.qualcomm.com>
Git-commit: c58eed6dc72f3169154d94cd258cdcbdcd24913a
Git-repo: git://w1.fi/srv/git/hostap.git
CRs-Fixed: 985990
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Expose the functions wpas_get_bands() and wpas_freq_to_band() and the
enum wpa_radio_work_band, since they will be needed outside
wpa_supplicant.c.
Change-Id: I2bea4838f852395d9df0d1c2ad2db51060722f1e
Signed-off-by: Lior David <qca_liord@qca.qualcomm.com>
Git-commit: 2b6e9f91df7acf19998f967fcc6c5f4bb911d1d8
Git-repo: git://w1.fi/srv/git/hostap.git
CRs-Fixed: 985990
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
PBSS (Personal Basic Service Set) is a new BSS type for DMG
networks. It is similar to infrastructure BSS, having an AP-like
entity called PCP (PBSS Control Point), but it has few differences.
PBSS support is mandatory for IEEE 802.11ad devices.
Add a new "pbss" argument to network block. The argument is used
in the following scenarios:
1. When network has mode=2 (AP), when pbss flag is set will start
as a PCP instead of an AP.
2. When network has mode=0 (station), when pbss flag is set will
connect to PCP instead of AP.
The function wpa_scan_res_match() was modified to match BSS according to
the pbss flag in the network block (wpa_ssid structure). When pbss flag
is set it will match only PCPs, and when it is clear it will match only
APs.
Change-Id: Ic93d717160b60ef61a6eceb574d31b3f142811fc
Signed-off-by: Lior David <qca_liord@qca.qualcomm.com>
Git-commit: b907491281b06b4dee9e0d0326e23c67ce486eb5
Git-repo: git://w1.fi/srv/git/hostap.git
CRs-Fixed: 985990
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
PBSS (Personal Basic Service Set) is a new BSS type for DMG
networks. It is similar to infrastructure BSS, having an AP-like
entity called PCP (PBSS Control Point), but it has few differences.
PBSS support is mandatory for IEEE 802.11ad devices.
Add a pbss flag to the relevant structures to support starting a PCP and
connecting to a PCP. Implement support in the nl80211 driver by using
the new PBSS flag attribute.
Change-Id: I35638f0d8e6d1b58190d53e90ffd386fc573ab12
Signed-off-by: Lior David <qca_liord@qca.qualcomm.com>
Git-commit: 86b5c400a0fe2567e40119c31657076b87cd5f18
Git-repo: git://w1.fi/srv/git/hostap.git
CRs-Fixed: 985990
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This brings in nl80211 definitions as of 2016-01-28.
Change-Id: If1134522b0ffd2ce797e2168080baeec8252b690
Signed-off-by: Jouni Malinen <j@w1.fi>
Git-commit: afa453a28aa63f447581e234341bd300a017d8eb
Git-repo: git://w1.fi/srv/git/hostap.git
CRs-Fixed: 985990
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This allows offloaded roaming to inform user space of the change in IP
subnet post roaming. The device may have roamed to a network which is in
a different subnet which will result in IP connectivity loss. Indicating
the change in subnet enables the user space to refresh the IP address or
to perform IP subnet validation if unknown status is indicated.
The driver indication is reported with a new event from wpa_supplicant
in the following format:
CTRL-EVENT-SUBNET-STATUS-UPDATE status=<0/1/2>
where
0 = unknown
1 = IP subnet unchanged (can continue to use the old IP address)
2 = IP subnet changed (need to get a new IP address)
Signed-off-by: Jouni Malinen <jouni@qca.qualcomm.com>
Git-commit: f32227ed9ec95524d670f9936f5bf87d4e39fa2b
Git-repo : git://w1.fi/srv/git/hostap.git
CRs-Fixed: 997716
Change-Id: I90dad050da7c279b54bbc12e0866c438f9ccaa16
|