From owner-freebsd-wireless@FreeBSD.ORG Mon Sep 8 07:59:17 2014 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 313BBF88 for ; Mon, 8 Sep 2014 07:59:17 +0000 (UTC) Received: from srv.netng.org (srv.netng.org [185.34.0.178]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id B35641483 for ; Mon, 8 Sep 2014 07:59:16 +0000 (UTC) Received: by srv.netng.org (Postfix, from userid 58) id E2A98F1998; Mon, 8 Sep 2014 03:59:13 -0400 (EDT) Received: from planb.g3.netng.org (unknown [188.175.210.2]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by srv.netng.org (Postfix) with ESMTPSA id 9BEF4F1993; Mon, 8 Sep 2014 03:59:11 -0400 (EDT) Date: Mon, 8 Sep 2014 09:59:09 +0200 From: Vladimir Botka To: Matthias Apitz Subject: Re: Issues with urtwn Message-ID: <20140908095909.12c56bde@planb.g3.netng.org> In-Reply-To: <20140908073229.GA1766@tiny-r269739> References: <540C751F.6050202@freebsd.org> <20140908054658.GA1349@tiny-r269739> <20140908081945.23015a99@planb.g3.netng.org> <20140908073229.GA1766@tiny-r269739> Organization: na X-Mailer: Claws Mail 3.10.1 (GTK+ 2.24.23; i686-pc-linux-gnu) MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; boundary="Sig_/q+=DhfVCdjQvuPnuuOtC2cH"; protocol="application/pgp-signature" Cc: "freebsd-wireless@freebsd.org" X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.18-1 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: Mon, 08 Sep 2014 07:59:17 -0000 --Sig_/q+=DhfVCdjQvuPnuuOtC2cH Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Hi Matthias, On Mon, 8 Sep 2014 09:32:29 +0200 Matthias Apitz wrote: > El d=C3=ADa Monday, September 08, 2014 a las 08:19:45AM +0200, Vladimir > Botka escribi=C3=B3: >=20 > Hi Vladimir, >=20 > > maybe the wpa_passphrase utility could help you to create the > > config. In this particular case: > >=20 > > $ wpa_passphrase "Naturhotel Wieserhof" "N@tur%Wieser" > > network=3D{ > > ssid=3D"Naturhotel Wieserhof" > > #psk=3D"N@tur%Wieser" > > psk=3Db853709a9edcd50edf0835f68bf099255cb32fc462e492117fe3c42ab= 2a387cb > > } >=20 > What is the benefit of coding the PSK? I have never used it; the > wpa_supplicant.conf file tested was: >=20 > ctrl_interface=3D/var/run/wpa_supplicant > ctrl_interface_group=3Dwheel > eapol_version=3D1 > ap_scan=3D1 > fast_reauth=3D1 >=20 > # Hotel Wieserhof > # > network=3D{ > ssid=3D"Naturhotel Wieserhof" > scan_ssid=3D1 > # key_mgmt=3DWPA-PSK WPA-EAP IEEE8021X > key_mgmt=3DWPA-PSK > # key_mgmt=3DWPA-PSK WPA-EAP > psk=3D"N@tur%Wieser" > # key_mgmt=3DNONE > # wep_tx_keyidx=3D0 > # wep_key0=3D"N@tur%Wieser" > } >=20 > as you see in the comments, I tested a lot of different key_mgmt=3D > values; the one shown active, gave the best results (but only in my > hotel room, not in the lobby); >=20 > > ,or you might want to try wpa_gui. >=20 > I have never used it, but will install the port and give it a try next > time. >=20 > Thx >=20 > matthias >=20 > PD: To Adrian, I'm willing to file a PR, but the problem is, I will > not return to this hotel and can not provide more information or > tests. psk=3D"N@tur%Wieser" and psk=3Db853709a9edcd50edf0835f68bf099255cb32fc462e492117fe3c42ab2a387cb are equivalent. If you have troubles to configure it manually, I recommend to try wpa_gui as a next step. In the upstream, wpa_gui is maintained together with wpa_supplicant by the same maintainer. Therefor wpa_gui has always been working fine with wpa_supplicant and might help you to create a consistent configuration. If this doesn't work, there might be a problem in the (1) lower layer (driver), (2) AP, or (3) HW in general. If so, to debug it might be a complex issue suitable for a bug entry.=20 Cheers, -vlado --Sig_/q+=DhfVCdjQvuPnuuOtC2cH Content-Type: application/pgp-signature; name=signature.asc Content-Disposition: attachment; filename=signature.asc -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQEcBAEBAgAGBQJUDWHNAAoJEKzxHYF8kx9kwO8H/3YiY0XsuzXLxIp6Dp2wa12V RxN5o5akFKVBMG550R/CFsZ/fTllt2mYoqo172Tt91HBqarbmj1Mo4zEp9LXDLUg fDDQt1ByR+Wu/UQtgyXVmC2/JRO+2NmF5l4wuQmVaigDtbe8SdTCbUWWh0eDuuOv Hls12w4jlO6f5Df/i8c70ZxAVgU6xOdr3Z85IULfCPBKuFecNzU3c6/hk6SMLl7W q8Ip3giZIhy3VEdqT4xWC8xtRxawGkKJEPUaWpHAoiXA+dQazcXUxwffqrRMu9NM xO+TCrAQA+L+UAZamRfEJCblW82oDkZxg9M1r/3CxvW4p4Vph+Xz33ZyqBxpQRg= =7WtP -----END PGP SIGNATURE----- --Sig_/q+=DhfVCdjQvuPnuuOtC2cH--