The package table lists three "full featured" wpad packages: wpad, wpad-openssl, and wpad-wolfssl.
First question, is the vanilla wpad just a simplified renaming of wpad-mbedtls that I found mentioned in this thread? If not, what is it?
Second question, which package should I prefer for WPA3 Enterprise? The same thread above suggests less cipher coverage with mbedtls, but is there anything else to consider?
It works for me with wpad-mbedtls. Regarding the cipher coverage, it applies to the use of these TLS libraries for TLS. However, WPA3 Enterprise wants only the crypto needed for EAP-SHA256-CCMP, which is supported even in this minimal variant.
Thank you.
But I'm still left with the question of why wpad-mbedtls doesn't appear in the package table. Is plain wpad the same thing?
No, it isn't. Official descriptions for both read:
This package contains a full featured IEEE 802.1x/WPA/EAP/RADIUS Authenticator and Supplicant
However, the plain wpad does not support WPA3 (or at least didn't when the current release candidate was 23.05.0-rc3), while wpad-mbedtls does.
Thank you for explaining the distinction!
I'm still puzzled about wpad-mbedtls not existing in the package table, though. And the package table is misbehaving, so it's hard to verify that easily, but I downloaded the most recent CSV dump and it's not in there.
Can packages be missing from the table but still available for use? If so, how/why does that happen?
Perhaps you are on a 22.03.x release? mbedtls was not a thing until 23.05.x.
I mean the table here:
Ignore that table. Only opkg list output after opkg update is authoritative.
OK, I didn't realize that. Thanks!
This topic was automatically closed 10 days after the last reply. New replies are no longer allowed.