meta data for this page
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| network:wifi:wpae [2023/06/21 11:54] – niziak | network:wifi:wpae [2023/10/23 11:14] (current) – niziak | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| ====== WiFi WPA Enterprise ====== | ====== WiFi WPA Enterprise ====== | ||
| - | ===== Android | + | ===== Win 11 ===== |
| + | Windows 11 22H2 not connecting to WPA Enterprise | ||
| + | - Open Registry Editor | ||
| + | - Navigate to '' | ||
| + | - Create '' | ||
| + | |||
| + | '' | ||
| + | - 0000 1100 0000 = 0x0C0 TLS1.0 | ||
| + | - 0011 0000 0000 = 0x300 TLS1.1 | ||
| + | - 1100 0000 0000 = 0xC00 TLS1.2 | ||
| + | |||
| + | ===== Android 11+ Devices ===== | ||
| + | |||
| + | **NOTE: DRAFT!** | ||
| Freeradius log: | Freeradius log: | ||
| Line 17: | Line 30: | ||
| </ | </ | ||
| - | [[https:// | + | Background: |
| + | * [[https:// | ||
| + | * [[https:// | ||
| + | |||
| + | Hints: | ||
| + | * | ||
| Workaround for Android based phone: | Workaround for Android based phone: | ||
| Line 28: | Line 46: | ||
| * CA certificate: | * CA certificate: | ||
| * Online certificate status: Do not verify | * Online certificate status: Do not verify | ||
| + | |||
| + | |||
| + | |||
| + | |||
| + | TODO | ||
| + | |||
| + | |||
| + | Android: | ||
| + | * " | ||
| + | * Possible to add alternate names to cert to use short domain | ||
| + | [[https:// | ||
| + | |||
| + | [[https:// | ||
| + | |||
| + | |||
| + | |||
| + | [[https:// | ||
| + | < | ||
| + | I don't disagree, but bottom line is that 11 will never connect without a trusted CA root (and all intermediates in the chain, if there are any, above the certificate your RADIUS server is presenting) physically installed to the phone. Just how it is. | ||
| + | </ | ||
| + | |||
| + | Starting with Android 11 QPR1, you must enter the domain for server certification validation in order to successfully connect. | ||
| + | |||
| + | |||
| + | [[https:// | ||
| + | < | ||
| + | The RADIUS certificate used by the 802.1X wireless controller or access point must use either: | ||
| + | |||
| + | A certificate signed by a trusted public Root certificate authority and configured to supply clients with the full certificate chain (root -> intermediate(s) -> server), OR | ||
| + | In the case of self-signed or private CA, pre-load the root and any intermediate certificates on the device' | ||
| + | </ | ||
| + | Add both certs to client ? how to add intermediate ca ? | ||
| + | |||
| + | New CA are added to '' | ||
| + | |||
| + | |||
| + | |||
| + | [[https:// | ||
| + | |||
| + | / | ||
| + | |||
| + | Use '' | ||
| + | |||
| + | <file / | ||
| + | tls-config tls-common { | ||
| + | private_key_password = | ||
| + | private_key_file = ${certdir}/ | ||
| + | |||
| + | certificate_file = ${certdir}/ | ||
| + | ca_path = ${cadir} | ||
| + | |||
| + | auto_chain = yes | ||
| + | } | ||
| + | </ | ||
| + | |||
| + | <file / | ||
| + | tls-config tls-common { | ||
| + | private_key_password = | ||
| + | private_key_file = ${certdir}/ | ||
| + | |||
| + | certificate_file = ${certdir}/ | ||
| + | auto_chain = no | ||
| + | } | ||
| + | </ | ||
| + | |||
| + | apt-get install eapoltest | ||
| + | |||
| + | |||
| + | Consider one selfsigned CA: [[https:// | ||