From owner-freebsd-wireless@FreeBSD.ORG Mon Sep 8 06:21:11 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 D3563CD3; Mon, 8 Sep 2014 06:21:11 +0000 (UTC) Received: from mail-qa0-x232.google.com (mail-qa0-x232.google.com [IPv6:2607:f8b0:400d:c00::232]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 7EB641B0C; Mon, 8 Sep 2014 06:21:11 +0000 (UTC) Received: by mail-qa0-f50.google.com with SMTP id cm18so13348113qab.37 for ; Sun, 07 Sep 2014 23:21:10 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=2teQV2OkxzV3td5GDMt5RlrOmGJtezGccEibuNER6Fs=; b=PdYhv/WBu5fTvH6j3MaRcljF6JOfvQP14nUNHKUUdwFaZO2/2MeKAXL/oWq7VCzoDU kbQn7IJTEkNIXmSbamr9WSp3daXeIrD617ZBYOoF405Wc/CeN/Wp+y4YMZbL52mXsp1V qc6FJb8Q8m+YE00hFdxdz9adBJn5/mC23kpPLOCM6gfgsVg5CYjRYzUajB7xvNyjAlkv i9Fmc1ysW2g8sawDINbSBKi7Ti9VRSpvj/7dDTt8OZHIho61ddLeuYWBXevSaWoL7oG+ ePp9m4ZNjzy7LkdYhWqEf7d8DJWX749lzCGn9nbrSdmUV1GKF+TuXV99IY2v0dO3CHXV Q26g== MIME-Version: 1.0 X-Received: by 10.140.42.17 with SMTP id b17mr26522677qga.52.1410157270624; Sun, 07 Sep 2014 23:21:10 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.224.39.139 with HTTP; Sun, 7 Sep 2014 23:21:10 -0700 (PDT) Received: by 10.224.39.139 with HTTP; Sun, 7 Sep 2014 23:21:10 -0700 (PDT) In-Reply-To: <20140908054658.GA1349@tiny-r269739> References: <540C751F.6050202@freebsd.org> <20140908054658.GA1349@tiny-r269739> Date: Sun, 7 Sep 2014 23:21:10 -0700 X-Google-Sender-Auth: ZtL_QJW1dLK1kFToNjQ1z5hOYDk Message-ID: Subject: Re: Issues with urtwn From: Adrian Chadd To: Matthias Apitz Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.18-1 Cc: freebsd-wireless@freebsd.org, Nathan Whitehorn 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 06:21:11 -0000 Please file PR entries for each of the problems you're seeing. I don't use the USB devices and I have my hands full with the atheros and Intel stuff as it is. Thanks! Adriabln On Sep 7, 2014 10:47 PM, "Matthias Apitz" wrote: > El d=C3=ADa Sunday, September 07, 2014 a las 07:36:27PM -0700, Adrian Cha= dd > escribi=C3=B3: > > > > I think what you are relating here is what I observed recently too. > > > Sorry, I'm new to FreeBSD. Just installed it recently, and I noticed > > > that after I left it idle (I went to do something for some hours) for > > > some time it lost the connection. Only rebooting makes it connect > > > again to my network. > > > > Which NIC are you seeing this on? > > Hi, > > I do not know if this helps. I adquired some weeks ago a small USB > adapter which presents itself in HEAD as: > > ugen4.4: at usbus4 > urtwn0: > on usbus4 > urtwn0: MAC/BB RTL8188CUS, RF 6052 1T1R > wlan0: Ethernet address: 80:1f:02:ee:16:37 > > I have no problems at all at my home AP (doing WPA PSK). The 'dongle' is > very small, only 5-6mm are looking out of the laptop after you plug it > in. The 6 euro investment ended all my searches to get the laptop's > Broadcom BCM4312 working. > > I only encountered one problem while traveling through Italy in a hotel: > They gave me a piece of paper saying "Password: "N@tur%Wieser" and I > could not construct a good /etc/wpa_supplicant.conf to connect > correctly. I could figure out the SSID of the AP ("Naturhotel Wieserhof") > and tried a lot of network=3D{ ... } settings, nothing worked. Sometimes > I could associate and got an IP addr from the AP, but only in places > where the hotel said it should not work (im my room). In places where it > should work (in the lobby) I could not even associate. I have a lot of > wpa_supplicant debug if someone is willing to check for details. At the > end I was frustated and gave up, more frustated due to the fact that all > the other clients with their stupid smartphones did not have had any > problem at all :-( > > matthias > -- > Matthias Apitz | /"\ ASCII Ribbon Campaign: > E-mail: guru@unixarea.de | \ / - No HTML/RTF in E-mail > WWW: http://www.unixarea.de/ | X - No proprietary attachments > phone: +49-170-4527211 | / \ - Respect for open standards > | en.wikipedia.org/wiki/ASCII_Ribbon_Campaig= n >