Hello, I am unable to get an ip address from my college wifi access point. My college uses Tunneled TLS with two possible inner authentication mechanisms (PAP or GTC). I have tried a few different configurations but none of them worked. Am I potentially looking in the wrong place? Could this be an issue with dhclient? Please note that this issue did not exist in the 12.x release series (although my tests then were with drivers other than iwn) here are the combinations I have tried in /etc/wpa_supplicant.conf that I can remember: // this one usually works when I try it network={ ssid="networkname" // this is just a placeholder for the real ssid key_mgmt=WPA-EAP identity="insert my identity here" password="insert my password here" } // specifying anything other than the above has always given me problems but I // tried it anyways network={ ssid="networkname" key_mgmt=WPA-EAP eap=TTLS phase1="peaplabel=0" phase2="auth=GTC" identity="insert my identity here" password="insert my password here" } // I also tried it with PAP network={ ssid="networkname" key_mgmt=WPA-EAP eap=TTLS phase1="peaplabel=0" phase2="auth=PAP" identity="insert my identity here" password="insert my password here" } none of these combinations have worked. The hardware I am working with is a System76 galago pro (not the most recent one). the wifi chipset is an intel Wireless AC 9560. If there is any other information I need to add, please tell me. Thanks, Ian Sutter
Created attachment 223735 [details] dmesg | grep iwm0 log file
Created attachment 223750 [details] netstat -m
I haven't tried this in forever :( But it's possible the updates to wpa_supplicant and net80211 changed things. Which hardware were you using in 12.x?
Also, you can get a LOT more debugging from the supplicant, run it in the foreground with '-ddd' on the command line and capture that.
I would like to request a change of the title of this bug to "Unable to get IP address from WPA-EAP TTLS network with iwm driver" I just tested connecting to the same network with a wifi dongle and it worked like a charm. This leads me a believe that it is a bug with iwm driver specifically, and not a problem with the DHCP stack.