From owner-freebsd-wireless@FreeBSD.ORG Tue May 28 16:21:49 2013 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id E182F2DC for ; Tue, 28 May 2013 16:21:49 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-qc0-x235.google.com (mail-qc0-x235.google.com [IPv6:2607:f8b0:400d:c01::235]) by mx1.freebsd.org (Postfix) with ESMTP id A9D00780 for ; Tue, 28 May 2013 16:21:49 +0000 (UTC) Received: by mail-qc0-f181.google.com with SMTP id u11so4115276qcx.40 for ; Tue, 28 May 2013 09:21:49 -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 :x-google-sender-auth:message-id:subject:from:to:content-type; bh=9+4CY9ATtK3NngLc+/nocgB8iJ9IwwgT5jUXgxbPmgc=; b=AHcm1gTPJGpkMbMCRHmiQYpM1qMUXjZf002QpNptkyI45SC5J+TlXIqkdrU3gmNQhu ifl2HORgv2z6GdLlkKBPSz3ZXOpKrCNE68Cpg5C2AQczbS/y+algsCsMrif6+Fbf45OV doUVXUcZJpu3NsMNHhLWn4HBKcAvRB0UPaJfqzRx2IKsM69GLZ9CENMrCrqn9b89a7Xo 3UxkQhATewlG9HhQdwtN/OXR2qGe5P0CKgwE1+MdA3SS0/1UHRXUE5PNcDA8a7o2eA9r 42UdURpxrXDnb3yesGQYf55Ks7S2P0D2GQMJI/JLY4dpCHKgqs2X44E6itIigaXyJ9jc I/bw== MIME-Version: 1.0 X-Received: by 10.49.5.202 with SMTP id u10mr37135356qeu.45.1369758109148; Tue, 28 May 2013 09:21:49 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.224.199.66 with HTTP; Tue, 28 May 2013 09:21:49 -0700 (PDT) In-Reply-To: <20130528115531.GO1334@albert.catwhisker.org> References: <20130528115531.GO1334@albert.catwhisker.org> Date: Tue, 28 May 2013 09:21:49 -0700 X-Google-Sender-Auth: Nlzqt1Qu3Lvejp1tGrbjf-n_VLM Message-ID: Subject: Re: iwn(4) link down/up cycling From: Adrian Chadd To: David Wolfskill , freebsd-wireless@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.14 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: Tue, 28 May 2013 16:21:49 -0000 You'll want to enable wpa_supplicant debugging and see what that says. It's your first hint to figuring out why the interface is flapping. It may be that the AP is disconnecting you for being idle too long. Try setting up a background ping. adrian On 28 May 2013 04:55, David Wolfskill wrote: > The laptop I've had for some time has an iwn(4) device that has > generally been working well. > > I recently acquired a laptop which I've set up for my spouse to use; its > wireless NIC is also detected as iwn(4). However, even when rather > little is going on (as in, she's not using it, because she's off doing > Something Else), I find that its IP address (and thus, its hostname) has > changed. Here's what "pciconf -lv" has to say about them -- first mine, > then the "new" one: > > iwn0@pci0:12:0:0: class=0x028000 card=0x11218086 chip=0x42358086 rev=0x00 hdr=0x00 > vendor = 'Intel Corporation' > device = 'Ultimate N WiFi Link 5300' > class = network > > > iwn0@pci0:3:0:0: class=0x028000 card=0x12118086 chip=0x42378086 rev=0x00 hdr=0x00 > vendor = 'Intel Corporation' > device = 'PRO/Wireless 5100 AGN [Shiloh] Network Connection' > class = network > > And here are some representative log entries for the latter: > > May 28 00:00:00 g1-241 kernel: wlan0: link state changed to DOWN > May 28 00:00:03 g1-241 kernel: wlan0: link state changed to UP > > May 28 04:31:22 g1-241 kernel: wlan0: link state changed to DOWN > May 28 04:31:23 g1-241 kernel: wlan0: link state changed to UP > > > Have I done something avoidable to encourage this behavior? > > Thanks.... > > Peace, > david > -- > David H. Wolfskill david@catwhisker.org > Taliban: Evil men with guns afraid of truth from a 14-year old girl. > > See http://www.catwhisker.org/~david/publickey.gpg for my public key.