From owner-freebsd-net@FreeBSD.ORG Tue Nov 25 21:32:00 2014 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 834BAD21; Tue, 25 Nov 2014 21:32:00 +0000 (UTC) Received: from tweddell.vserver-on.de (tweddell.de [84.38.66.62]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 49414B15; Tue, 25 Nov 2014 21:31:59 +0000 (UTC) Received: from bastian by tweddell.vserver-on.de with local (Exim 4.80) (envelope-from ) id 1XtNiA-0007tp-OZ; Tue, 25 Nov 2014 22:31:50 +0100 Date: Tue, 25 Nov 2014 22:31:50 +0100 From: Bastian To: Adrian Chadd Subject: Re: iwn fails to scan on E6330 Message-ID: <20141125213150.GH30752@tweddell.de> References: <20141124141234.GG30752@tweddell.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) Cc: FreeBSD Net X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 25 Nov 2014 21:32:00 -0000 On 24Nov14 08:27 -0800, Adrian Chadd wrote: > You need to create wlan0 first before you use it. > > # ifconfig wlan0 create wlandev iwn0 > # ifconfig wlan0 up > # ifconfig wlan0 list scan (bringing it 'up' will start scanning) > Many thanks. I skiped that one while reading the manual. But now it works well. May I assume, that you can create multiple wlan\d devices on one and the sane iwn0 kernel device? Now, I have wpa_supplicant working, in a way that it is automatically searching for an available wifi network. This is triggered in the /etc/rc.conf file during boot. I may have some follow-up questions: Q: service netif stop, shuts everything down, but the wpa_supplicant process withstands from going down and starts to loop 100% cpu cyles :/ Q: How can I just shutdown a single network interface? Keeping others up and with the adjustment of the default routing. Many thanks in advance, -- Bastian