From owner-freebsd-wireless@freebsd.org Wed Mar 31 21:03:57 2021 Return-Path: Delivered-To: freebsd-wireless@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 2BF915B0872 for ; Wed, 31 Mar 2021 21:03:57 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mailman.nyi.freebsd.org (unknown [127.0.1.3]) by mx1.freebsd.org (Postfix) with ESMTP id 4F9f1n0Zlqz4fKH for ; Wed, 31 Mar 2021 21:03:57 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.nyi.freebsd.org (Postfix) id 13E535B0C33; Wed, 31 Mar 2021 21:03:57 +0000 (UTC) Delivered-To: wireless@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 13A735B0A72 for ; Wed, 31 Mar 2021 21:03:57 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.nyi.freebsd.org (mxrelay.nyi.freebsd.org [IPv6:2610:1c1:1:606c::19:3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mxrelay.nyi.freebsd.org", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4F9f1m72n0z4fCG for ; Wed, 31 Mar 2021 21:03:56 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2610:1c1:1:606c::50:1d]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id E4BE420523 for ; Wed, 31 Mar 2021 21:03:56 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.5]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id 12VL3urp089761 for ; Wed, 31 Mar 2021 21:03:56 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id 12VL3ukj089760 for wireless@FreeBSD.org; Wed, 31 Mar 2021 21:03:56 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: wireless@FreeBSD.org Subject: [Bug 254683] Unable to connect get IP address from WPA-EAP TTLS network on FreeBSD 13.0-RC4 Date: Wed, 31 Mar 2021 21:03:57 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: wireless X-Bugzilla-Version: 13.0-STABLE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: stormchaser30000@gmail.com X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: wireless@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_id short_desc product version rep_platform op_sys bug_status bug_severity priority component assigned_to reporter Message-ID: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 31 Mar 2021 21:03:57 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D254683 Bug ID: 254683 Summary: Unable to connect get IP address from WPA-EAP TTLS network on FreeBSD 13.0-RC4 Product: Base System Version: 13.0-STABLE Hardware: amd64 OS: Any Status: New Severity: Affects Only Me Priority: --- Component: wireless Assignee: wireless@FreeBSD.org Reporter: stormchaser30000@gmail.com Hello, I am unable to get an ip address from my college wifi access point. My coll= ege 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 (altho= ugh my tests then were with drivers other than iwn) here are the combinations I have tried in /etc/wpa_supplicant.conf that I c= an remember: // this one usually works when I try it network=3D{ ssid=3D"networkname" // this is just a placeholder for the real ssid key_mgmt=3DWPA-EAP identity=3D"insert my identity here" password=3D"insert my password here" } // specifying anything other than the above has always given me problems bu= t I=20 // tried it anyways network=3D{ ssid=3D"networkname" key_mgmt=3DWPA-EAP eap=3DTTLS phase1=3D"peaplabel=3D0" phase2=3D"auth=3DGTC" identity=3D"insert my identity here" password=3D"insert my password here" } // I also tried it with PAP network=3D{ ssid=3D"networkname" key_mgmt=3DWPA-EAP eap=3DTTLS phase1=3D"peaplabel=3D0" phase2=3D"auth=3DPAP" identity=3D"insert my identity here" password=3D"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 --=20 You are receiving this mail because: You are the assignee for the bug.=