# Mark 2 and WPA3

**URL:** https://community.openconversational.ai/t/mark-2-and-wpa3/3255
**Category:** Mark II
**Tags:** markii
**Created:** [March 12, 2018, 7:12pm UTC](https://community.openconversational.ai/t/mark-2-and-wpa3/3255 "2018-03-12T19:12:43Z")
**Posts on this page:** 7
**Page:** 1

<div class="post-metadata">

### Author: ![Spacesurfer](https://community.openconversational.ai/letter_avatar_proxy/v4/letter/s/9d8465/32.png) [@Spacesurfer](https://community.openconversational.ai/u/Spacesurfer)
#### Post date: [March 12, 2018, 7:12pm UTC](https://community.openconversational.ai/t/mark-2-and-wpa3/3255/1 "2018-03-12T19:12:43Z")

</div>

Will the Mark 2 will support WPA3 out of the box or in a later update?

---

<div class="post-metadata">

### Author: ![KathyReid](https://community.openconversational.ai/user_avatar/community.openconversational.ai/kathyreid/32/1949_2.png) [@KathyReid](https://community.openconversational.ai/u/KathyReid)
#### Post date: [March 13, 2018, 8:39am UTC](https://community.openconversational.ai/t/mark-2-and-wpa3/3255/2 "2018-03-13T08:39:13Z")

</div>

Good question, I’m going to pass this one to @derick-mycroft for more information.

---

<div class="post-metadata">

### Author: ![suisat](https://community.openconversational.ai/letter_avatar_proxy/v4/letter/s/34f0e0/32.png) [@suisat](https://community.openconversational.ai/u/suisat)
#### Post date: [April 28, 2020, 8:05am UTC](https://community.openconversational.ai/t/mark-2-and-wpa3/3255/3 "2020-04-28T08:05:51Z")

</div>

Did you got a reply for this? I want to know that too.

THX

---

<div class="post-metadata">

### Author: ![j1nx](https://community.openconversational.ai/user_avatar/community.openconversational.ai/j1nx/32/1260_2.png) [@j1nx](https://community.openconversational.ai/u/j1nx)
#### Post date: [April 28, 2020, 10:16am UTC](https://community.openconversational.ai/t/mark-2-and-wpa3/3255/4 "2020-04-28T10:16:29Z")

</div>

Depends of course a bit on what hardware they eventually are going to choose / use, but if it is the RPI3b+ or RPI4 the hardware supports it, so should be able to support.

Quickly looked into it before for my own project…

---

<div class="post-metadata">

### Author: ![j1nx](https://community.openconversational.ai/user_avatar/community.openconversational.ai/j1nx/32/1260_2.png) [@j1nx](https://community.openconversational.ai/u/j1nx)
#### Post date: [April 28, 2020, 8:12pm UTC](https://community.openconversational.ai/t/mark-2-and-wpa3/3255/5 "2020-04-28T20:12:17Z")

</div>

Must add to that; If you really talking about WPA3/SAE (encryption) and not WPA3/DDP (easy setup).

Doubt, DDP is implemented in the wifi firmware already. And then again, it will only be useful to do that over Bluetooth, which is really “new stuff”.

---

<div class="post-metadata">

### Author: ![baconator](https://community.openconversational.ai/letter_avatar_proxy/v4/letter/b/d07c76/32.png) [@baconator](https://community.openconversational.ai/u/baconator)
#### Post date: [February 1, 2023, 2:00am UTC](https://community.openconversational.ai/t/mark-2-and-wpa3/3255/6 "2023-02-01T02:00:54Z")

</div>

Resurrecting this to mention that none of the images for mk2 currently support wpa3/SAE out of the box. There’s no raspbian-based fix coming for this any time soon:

> <https://github.com/raspberrypi/linux/issues/3619#issuecomment-1357926601>
>
> \*\*Is this the right place for my bug report?\*\*
> It might be related to brcmfmac …firmware. I am using the firmware from https://github.com/RPi-Distro/firmware-nonfree
> 
> \*\*Describe the bug\*\*
> It looks like brcmfmac does not support ieee80211w/MFP in AP mode. Clients are unable to connect to the network because the RSN IE message during handshake is different from the one in the beacon frame.
> 
> Disabling ieee80211w fixes the issue.
> 
> If I run the same hostapd.conf on my laptop (iwlwifi/iwlmvm), my phone connects to it just fine.
> 
> \*\*To reproduce\*\*
> hostapd.conf:
> \`\`\`
> ctrl\_interface=/var/run/hostapd
> ctrl\_interface\_group=wheel
> 
> driver=nl80211
> 
> macaddr\_acl=0
> wmm\_enabled=1
> country\_code=BG
> ignore\_broadcast\_ssid=0
> hw\_mode=g
> ieee80211n=1
> ieee80211w=1
> ieee80211d=1
> channel=6
> 
> interface=wlan0
> 
> ssid=REDACTED
> wpa=2
> wpa\_key\_mgmt=WPA-PSK
> rsn\_pairwise=CCMP
> wpa\_passphrase=REDACTED
> \`\`\`
> 
> \*\*Expected behaviour\*\*
> Clients can connect to the network.
> 
> \*\*Actual behaviour\*\*
> Clients cannot connect to the network.
> 
> \*\*System\*\*
> Device: Raspberry Pi 4 Model B Rev 1.2
> Kernel: rpi-5.6.y from 5377449ffb6ffe9ebfee939d52b2611130fbb836
> Firwmare version: May 11 2020 18:59:41, 21bfdeee3a6ea823e2113b983390acd1eec8edfb (clean) (release) (start)
> OS: Fedora 32 aarch64
> hostapd: hostapd-2.9-3.fc32.aarch64
> 
> \*\*Logs\*\*
> No errors appear on the Pi.
> 
> Here is what happens on my laptop when it tries to connect:
> \`\`\`
> wpa\_supplicant: wlan: SME: Trying to authenticate with dc:a6:32:87:2a:8d (SSID='REDACTED' freq=2437 MHz)
> kernel: wlan: authenticate with dc:a6:32:87:2a:8d
> kernel: wlan: send auth to dc:a6:32:87:2a:8d (try 1/3)
> wpa\_supplicant: wlan: Trying to associate with dc:a6:32:87:2a:8d (SSID='REDACTED' freq=2437 MHz)
> kernel: wlan: authenticated
> kernel: wlan: associate with dc:a6:32:87:2a:8d (try 1/3)
> kernel: wlan: RX AssocResp from dc:a6:32:87:2a:8d (capab=0x411 status=0 aid=1)
> wpa\_supplicant: wlan: Associated with dc:a6:32:87:2a:8d
> wpa\_supplicant: wlan: CTRL-EVENT-SUBNET-STATUS-UPDATE status=0
> kernel: wlan: associated
> wpa\_supplicant: wlan: WPA: IE in 3/4 msg does not match with IE in Beacon/ProbeResp (src=dc:a6:32:87:2a:8d)
> wpa\_supplicant: WPA: RSN IE in Beacon/ProbeResp - hexdump(len=22): 30 14 01 00 00 0f ac 04 01 00 00 0f ac 04 01 00 00 0f ac 02 0c 00
> wpa\_supplicant: WPA: RSN IE in 3/4 msg - hexdump(len=26): 30 18 01 00 00 0f ac 04 01 00 00 0f ac 04 02 00 00 0f ac 02 00 0f ac 08 0c 00
> kernel: wlan: deauthenticating from dc:a6:32:87:2a:8d by local choice (Reason: 17=IE\_DIFFERENT)
> wpa\_supplicant: wlan: CTRL-EVENT-DISCONNECTED bssid=dc:a6:32:87:2a:8d reason=17 locally\_generated=1
> \`\`\`

but there are other possible workarounds:

> <https://github.com/raspberrypi/linux/issues/4718>
>
> I bought a Raspberry Pi Zero 2 W and apparently it does not support my home wifi… which uses WPA3.
> 
> I excepted that to be the case, since on Debian usually works just fine, and this device is a new release.
> 
> It should be at last officialy stated somewhere that is not supported. I basically bought something I can't use.
> 
> Notice that WPA3 is not anymore a theory, many commercial routers now ship with it in mixed mode or add that through firmware update.
> 
> Side note: actually run just fine on common operating systems from Windows to Android, including Linux if you have no firmware issues.

Not a mycroft issue, more a raspberry pi one.

---

<div class="post-metadata">

### Author: ![j1nx](https://community.openconversational.ai/user_avatar/community.openconversational.ai/j1nx/32/1260_2.png) [@j1nx](https://community.openconversational.ai/u/j1nx)
#### Post date: [February 1, 2023, 8:24am UTC](https://community.openconversational.ai/t/mark-2-and-wpa3/3255/7 "2023-02-01T08:24:34Z")

</div>

OpenVoiceOS - Buildroot edition has WPA compiled with WPA3 support enabled since the beginning.

The wifi-hotspot method does not support it I believe (but by all means give it a try and please report back), however with the GUI method it has been confirmed WPA3 networks can be setup and is working.
