From owner-freebsd-current@FreeBSD.ORG Sun Dec 5 08:59:41 2010 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 912AF106566C for ; Sun, 5 Dec 2010 08:59:41 +0000 (UTC) (envelope-from bschmidt@techwires.net) Received: from mail-bw0-f54.google.com (mail-bw0-f54.google.com [209.85.214.54]) by mx1.freebsd.org (Postfix) with ESMTP id 271118FC08 for ; Sun, 5 Dec 2010 08:59:40 +0000 (UTC) Received: by bwz2 with SMTP id 2so10135834bwz.13 for ; Sun, 05 Dec 2010 00:59:40 -0800 (PST) Received: by 10.204.113.131 with SMTP id a3mr4455225bkq.123.1291538139456; Sun, 05 Dec 2010 00:35:39 -0800 (PST) Received: from julie.lab.techwires.net (dslb-088-067-219-237.pools.arcor-ip.net [88.67.219.237]) by mx.google.com with ESMTPS id d11sm1132356bkd.22.2010.12.05.00.35.37 (version=SSLv3 cipher=RC4-MD5); Sun, 05 Dec 2010 00:35:38 -0800 (PST) Sender: Bernhard Schmidt From: Bernhard Schmidt To: Steve Kargl Date: Sun, 5 Dec 2010 09:34:46 +0100 User-Agent: KMail/1.13.5 (FreeBSD/8.1-RELEASE; KDE/4.5.4; amd64; ; ) References: <20101205062103.GA63430@troutmask.apl.washington.edu> In-Reply-To: <20101205062103.GA63430@troutmask.apl.washington.edu> MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <201012050934.46566.bschmidt@freebsd.org> Cc: freebsd-current@freebsd.org Subject: Re: wlan0 going UP/DOWN problem X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 05 Dec 2010 08:59:41 -0000 On Sunday 05 December 2010 07:21:03 Steve Kargl wrote: > It seems some recent change (as in the last 7-10 days) > has caused an instability in wlan0. Just a small > excerpt from /var/log/messages, > > Dec 4 18:54:16 laptop kernel: wlan0: link state changed to UP > Dec 4 19:11:16 laptop kernel: wlan0: link state changed to DOWN > Dec 4 19:11:16 laptop kernel: wlan0: link state changed to UP > Dec 4 19:19:46 laptop kernel: wlan0: link state changed to DOWN > Dec 4 19:19:46 laptop kernel: wlan0: link state changed to UP > Dec 4 19:37:01 laptop kernel: wlan0: link state changed to DOWN > Dec 4 19:37:01 laptop kernel: wlan0: link state changed to UP > Dec 4 19:45:31 laptop kernel: wlan0: link state changed to DOWN > Dec 4 19:45:31 laptop kernel: wlan0: link state changed to UP > Dec 4 19:54:01 laptop kernel: wlan0: link state changed to DOWN > Dec 4 19:54:01 laptop kernel: wlan0: link state changed to UP > Dec 4 20:11:16 laptop kernel: wlan0: link state changed to DOWN > Dec 4 20:11:16 laptop kernel: wlan0: link state changed to UP > Dec 4 20:19:46 laptop kernel: wlan0: link state changed to DOWN > Dec 4 20:19:46 laptop kernel: wlan0: link state changed to UP > Dec 4 20:36:46 laptop kernel: wlan0: link state changed to DOWN > Dec 4 20:36:46 laptop kernel: wlan0: link state changed to UP > Dec 4 20:45:16 laptop kernel: wlan0: link state changed to DOWN > Dec 4 20:45:16 laptop kernel: wlan0: link state changed to UP > Dec 4 20:53:46 laptop kernel: wlan0: link state changed to DOWN > Dec 4 20:53:46 laptop kernel: wlan0: link state changed to UP > > So, every 18 minutes the devices is going DOWN/UP. :-/ More details please. Which driver? How is that stuff configured? wpa_supplicant involved? Try running it with debug messages enabled. We need to figure out what entity is causing the device to go down/up, this can either be wpa_supplicant or net80211 (or a cronjob calling ifconfig down/up every 18 minutes ;). The appropriate debug options enabled (wlandebug 0xffffffff or wpa_supplicant with -dd) should reveal that. -- Bernhard