From owner-freebsd-wireless@FreeBSD.ORG Sun Nov 2 15:31:32 2014 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id EB2ECDD9; Sun, 2 Nov 2014 15:31:32 +0000 (UTC) Received: from d.mail.sonic.net (d.mail.sonic.net [64.142.111.50]) (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 CD251FA; Sun, 2 Nov 2014 15:31:32 +0000 (UTC) Received: from comporellon.tachypleus.net (polaris.tachypleus.net [75.101.50.44]) (authenticated bits=0) by d.mail.sonic.net (8.14.9/8.14.9) with ESMTP id sA2FVPuZ001899 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Sun, 2 Nov 2014 07:31:26 -0800 Message-ID: <54564E4D.4020703@freebsd.org> Date: Sun, 02 Nov 2014 07:31:25 -0800 From: Nathan Whitehorn User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:31.0) Gecko/20100101 Thunderbird/31.1.0 MIME-Version: 1.0 To: Matthias Apitz Subject: Re: Issues with urtwn References: <540C92D6.4030106@freebsd.org> <540CC53A.90600@freebsd.org> <540E2A2D.4090301@freebsd.org> <20141026073605.GA1819@unixarea.DDR.dd> <20141101081736.GA2857@unixarea.DDR.dd> <20141102084605.GA60031@unixarea.DDR.dd> <54564C92.8040104@freebsd.org> <20141102152953.GA20263@unixarea.DDR.dd> In-Reply-To: <20141102152953.GA20263@unixarea.DDR.dd> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit X-Sonic-CAuth: UmFuZG9tSVZqq22SGSexv+SHN4rUBl+s9uKzMM9RR24xVd7qfN3Ih/vOGtZFpa+Otvxwd4SlXhx5ON/LW5T4Iho3RyvhCYkSUfEunT7ooDc= X-Sonic-ID: C;jpCfTqVi5BGDpygW/FJGkA== M;UtndTqVi5BGDpygW/FJGkA== X-Spam-Flag: No X-Sonic-Spam-Details: 0.0/5.0 by cerberusd 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: Sun, 02 Nov 2014 15:31:33 -0000 On 11/02/14 07:29, Matthias Apitz wrote: > El día Sunday, November 02, 2014 a las 07:24:02AM -0800, Nathan Whitehorn escribió: > >> Are you running wpa_supplicant? If you can connect to a plain network >> with ifconfig, these will stop. >> -Nathan > I do run wpa_supplicant. But I don't understand what you mean with "If > you can connect to a plain network with ifconfig ..." > > wlan0 has an IP addr (via DHCP from the AP) and I can connect. What do > you mean with "to a plain network with ifconfig ..."? > > Thx > > matthias > > You can connect to an unencrypted network by doing ifconfig wlan0 -bgscan ssid blah. The issue is that wpa_supplicant is doing scanning in the background, which forces the adapter into power-save mode. -Nathan