• State Resolved
  • Locked Locked
  • Replies 6 replies
  • Subscribers 40 subscribers
  • Views 538 views
  • Users 0 members are here
Support feedback
Options
Options
Related

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

Original question:

WL1807MOD: Shielding De-Auth Attack

WL1831MOD: WL1831MOD 802.11w (Protected Management Frame) Support

x123x
Prodigy 180 points
Part Number: WL1831MOD

Tool/software:

We are using the WL1831MOD in a system running Linux Kernel Version 6.9 with the latest TI driver and latest firmware available. 

I see from this thread that it should be possible to connect to a network with Protected Management Frames enabled: e2e.ti.com/.../wl1807mod-shielding-de-auth-attack

It's not working for us. Is there something we need to enable, or a config we need to change to enable support for 802.11w on this module?

Supported Ciphers:
		* WEP40 (00-0f-ac:1)
		* WEP104 (00-0f-ac:5)
		* TKIP (00-0f-ac:2)
		* CCMP-128 (00-0f-ac:4)
		* WPI-SMS4 (00-14-72:1)

  • 0
    TI__Mastermind 23196 points

    Assigning to an expert.

  • 0 in reply to AB
    TI__Guru 64305 points

    Hi,

    First, make sure that the firmware you are using is at least 8.9.0.0.83.

    Second, the driver should support it. To make sure, please check that IGTK is added. You can check your drivers/net/wireless/ti/wlcore/cmd.h and look for this key type.

    Third, supplicant.conf should contain PMF related configuration. For example ieee80211w or pmf.

    Regards,

    Shlomi

  • 0 in reply to Shlomi Itzhak
    Prodigy 180 points

    Thank you.

    Our firmware version is 8.9.0.0.83 (I'm not sure why it references both 8.2.0.0.243 and 8.9.0.0.83, though):

    [   22.373307] wlcore: PHY firmware version: Rev 8.2.0.0.243
[   22.417679] wlcore: firmware booted (Rev 8.9.0.0.83)
[   22.518983] wlcore: down
[   23.046546] Bluetooth: MGMT ver 1.22
[   24.123741] wlcore: PHY firmware version: Rev 8.2.0.0.243
[   24.167487] wlcore: firmware booted (Rev 8.9.0.0.83)

    We are using mainline linux kernel v 6.9: https://github.com/torvalds/linux/blob/v6.9/drivers/net/wireless/ti/wlcore/cmd.h

    It would appear that the IGTK key was REMOVED due to stability issues?

    More details on that commit:

    https://github.com/torvalds/linux/commit/1264c1e0cfe55e2d6c35e869244093195529af37

    If we look at the tip of development, this reversion has never been undone - IGTK is still removed from the current mainline TI wlcore driver. Has this been added back in a way that addresses the above-mentioned cause for its removal in some fork of this driver somewhere?

    Regarding supplicant.conf, we are using iwd, which doesn't not require explicit enablement of this in a configuration file, to my knowledge. Regardless, it seems pretty clear that the issue is the removal of this from the driver.

  • +1 in reply to x123x
    TI__Guru 64305 points

    Hi,

    WiLink driver is not in mainline. It is maintained using patches on top of specific kernels.

    Latest is v4.19 (in the past it was).

    This is not the case with the newer transceivers, CC33xx, which are going to me upstream.

    If I remember correctly, the reason it was removed is because it didn't work with older firmware binaries and since it was not compatible with older versions, it was decided to remove it.

    I believe it is safe to revert and implement this patch.

    Regards,

    Shlomi

  • 0 in reply to Shlomi Itzhak
    Prodigy 180 points

    Thank you Shlomi. We put that patch back into the driver and we were able to connect to PMF-enabled and WPA3 networks with that change and the newest firmware. Thank you!

    Is there a reason why the newer firmware version cannot be enforced in mainline linux so that this patch can be reintroduced to the upstream kernel?

    Furthermore, we are now using the upstream linux driver with this patch present - you mentioned that this driver is actually maintained elsewhere - where should we be looking for the TI-maintained driver, and is there any reason we should be using it instead of what is included in the mainline kernel tree (with just this patch added)?

    Thanks!

  • 0 in reply to x123x
    TI__Guru 64305 points

    Hi,

    As I mentioned, upstreaming was abandoned few years back, not sure what the reason was.

    the driver on mainline is quite old, this is why it didn't work with the newer firmware.

    The updated set of patches can be found here https://git.ti.com/cgit/wilink8-wlan/build-utilites/log/?h=r8.9 and specifically under the 4.19.38 patches directory https://git.ti.com/cgit/wilink8-wlan/build-utilites/tree/patches/kernel_patches/4.19.38?h=r8.9

    Regards,

    Shlomi