Sie sind hier: Startseite / Studentinnen- und Studentenrat / Referate / Referat Hochschulpolitik / Bereich Datenkultur / Nachrichten / eduroam (HTW Dresden) meets wpa_supplicant after Syatag 3185

eduroam (HTW Dresden) meets wpa_supplicant after Syatag 3185

eduroam (HTW Dresden) meets wpa_supplicant at all the (geeky) *nix systems after Syatag 3185 (aka 2019-05-31)
eduroam (HTW Dresden) meets wpa_supplicant after Syatag 3185

eduroam works on *nix

 

There is one "big" thing to be added:

You have to check that there is the dubious predefined anonymous identity 69873312454253036930@htw-dresden.de. One line of the wpa_supplicant.conf file (in the eduroam network section) should look like this:

anonymous_identity="69873312454253036930@htw-dresden.de"

 

So the following wpa_supplicant.conf file is tested (and works fine (on Project Trident (TrueOS (FreeBSD(-CURRENT)))) and OpenBSD):

PEAP/MSCHAPV2
style
TTLS/PAP
style
network={
# priority=123
 scan_ssid=1
 ssid="eduroam"
 proto=RSN
 key_mgmt=WPA-EAP
 eap=PEAP
# domain_suffix_match="radius.htw-dresden.de"
 domain_suffix_match="radius.htw-dresden.de"
 anonymous_identity="69873312454253036930@htw-dresden.de"
 identity="s23542@htw-dresden.de"
 password="P4SSW0RD!"
# ca_cert="/usr/local/openssl/cert.pem"
 ca_cert="/usr/local/openssl/cert.pem"
 phase1="peaplabel=0"
 phase2="auth=MSCHAPV2"
}
network={
# priority=123
 scan_ssid=1
 ssid="eduroam"
 proto=RSN
 key_mgmt=WPA-EAP
 eap=TTLS
# domain_suffix_match="radius.htw-dresden.de"
 domain_suffix_match="radius.htw-dresden.de"
 anonymous_identity="69873312454253036930@htw-dresden.de"
 identity="s23542@htw-dresden.de"
 password="P4SSW0RD!"
# ca_cert="/usr/local/openssl/cert.pem"
 ca_cert="/usr/local/openssl/cert.pem"
 phase2="auth=PAP"
}
recommended (by "the HTW Dresden eduroam Linux script") also well known

This change is needed (as announced) after Syaday (YOLD 3185).

thx for the #love2eduroam (at our HTW Dresden) :
Anja L.
Richard Sch.
Florian K.

Artikelaktionen

Versenden
Drucken