Unterschiede

Hier werden die Unterschiede zwischen zwei Versionen angezeigt.

--- stellar-wireless-wpa3-sae-raspberry-pi [2019/05/20 20:25] – [TODO] benny
+++ stellar-wireless-wpa3-sae-raspberry-pi [2024/06/09 10:29] (aktuell) – Externe Bearbeitung 127.0.0.1
@@ Zeile 3: / Zeile 3: @@
 Connecting with WPA3-Personal (SAE/PMF) on the Raspberry Pi 3 B+ via on-board wireless NIC is not exactly straight forward, but it works. On this page I'll document what needs to be done, to get it to work.
-**Equipement & Access Point used:**
+**Equipment & Access Point used:**
   * [[https://www.al-enterprise.com/en/products/wlan/omniaccess-stellar-access-point-1201|Alcatel-Lucent Enterprise OmniAccess Stellar AP1201]]
   * AWOS v3.0.6.20
@@ Zeile 9: / Zeile 9: @@
   * Raspberry Pi Model 3 B+
 {{ :omniaccess-stellar-ap1201.png?direct&400 |}}
+<WRAP center round tip 60%>
+If you'd like to know how to connect a Windows 10 laptop via WPA3-Personal, [[stellar-wireless-win10-windows-10-wpa3-sae|you may want to review this article]]!
+</WRAP>
 Connecting to SSID "ov44b39" mandates MFP/PMF (as SAE-only), as you can tell from following **Wifi Explorer** screenshot.
@@ Zeile 1352: / Zeile 1356: @@
 # Install a libssl-dev to make the compilation successful
-sudo apt-get install libssl-dev
+sudo apt-get install libssl-dev libnl-dev
 # Depending on your system, you might need some libnl packages
-# Those are the ones I have ...
+# Those are the ones I have, but the above should be sufficient
 dpkg -l | grep libnl
 ii  libnl-3-200:armhf                     3.2.27-2                          armhf        library for dealing with netlink sockets
@@ Zeile 1382: / Zeile 1386: @@
 ==== Content of my wpa_supplicant.conf ====
-You'll need to adapt this to your needs.
+You'll need to adapt this to your needs. Please note that "pmf=1" signals that the client is capable to do Protected Management Frames (PMF), while SAE makes it mandatory (required) to enable/use PMF.
 <code>
 ctrl_interface=DIR=/var/run/wpa_supplicant GROUP=netdev