From owner-freebsd-net@FreeBSD.ORG  Tue Jul  7 10:09:01 2009
Return-Path: <owner-freebsd-net@FreeBSD.ORG>
Delivered-To: freebsd-net@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id 709BF106564A
	for <freebsd-net@freebsd.org>; Tue,  7 Jul 2009 10:09:01 +0000 (UTC)
	(envelope-from freebsdusb@bindone.de)
Received: from mail.bindone.de (mail.bindone.de [80.190.134.51])
	by mx1.freebsd.org (Postfix) with SMTP id B4D218FC20
	for <freebsd-net@freebsd.org>; Tue,  7 Jul 2009 10:09:00 +0000 (UTC)
	(envelope-from freebsdusb@bindone.de)
Received: (qmail 96311 invoked by uid 89); 7 Jul 2009 10:08:59 -0000
Received: from unknown (HELO ufo.bindone.de) (mg@bindone.de@87.152.182.110)
	by mail.bindone.de with ESMTPA; 7 Jul 2009 10:08:59 -0000
Message-ID: <4A531E96.4060005@bindone.de>
Date: Tue, 07 Jul 2009 12:08:22 +0200
From: Michael Gmelin <freebsdusb@bindone.de>
User-Agent: Thunderbird 2.0.0.17pre (X11/20090202)
MIME-Version: 1.0
To: Aragon Gouveia <aragon@phat.za.net>
References: <4A52C132.5080106@phat.za.net>
In-Reply-To: <4A52C132.5080106@phat.za.net>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: freebsd-net@freebsd.org
Subject: Re: iwn(4) doesn't like hardware RF switches
X-BeenThere: freebsd-net@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Networking and TCP/IP with FreeBSD <freebsd-net.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-net>,
	<mailto:freebsd-net-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-net>
List-Post: <mailto:freebsd-net@freebsd.org>
List-Help: <mailto:freebsd-net-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-net>,
	<mailto:freebsd-net-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 07 Jul 2009 10:09:01 -0000

Aragon Gouveia wrote:
> Hi,
> 
> Is it just me, or does the iwn driver in -CURRENT not play well with
> hardware RF switches on notebooks?  For me the only resemblence of an
> event I see is when I switch off RF - the kernel sends a log to syslog.
>  wpa_supplicant doesn't pick it up, and neither does devd.  The result
> is that I can't keep wpa_supplicant running and let it reassociate when
> I turn off/on, and neither can I start/stop wpa_supplicant from devd
> when I turn on/off.
> 
> I guess I could leave the RF switch on and just bind a key shortcut in
> Xorg to start/stop wpa_supplicant, but a standard approach would be
> nice... :)
> 
> 
> Thanks,
> Aragon
> 
> 
> _______________________________________________
> freebsd-net@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-net
> To unsubscribe, send any mail to "freebsd-net-unsubscribe@freebsd.org"

I can confirm this behaviour (+ sometimes iwn gets totally confused by
that). What laptop are you using?