From owner-freebsd-wireless@FreeBSD.ORG Tue May 28 11:55:32 2013 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id B79CF907 for ; Tue, 28 May 2013 11:55:32 +0000 (UTC) (envelope-from david@catwhisker.org) Received: from albert.catwhisker.org (m209-73.dsl.rawbw.com [198.144.209.73]) by mx1.freebsd.org (Postfix) with ESMTP id 78734237 for ; Tue, 28 May 2013 11:55:31 +0000 (UTC) Received: from albert.catwhisker.org (localhost [127.0.0.1]) by albert.catwhisker.org (8.14.7/8.14.7) with ESMTP id r4SBtVoj018398 for ; Tue, 28 May 2013 04:55:31 -0700 (PDT) (envelope-from david@albert.catwhisker.org) Received: (from david@localhost) by albert.catwhisker.org (8.14.7/8.14.7/Submit) id r4SBtVMl018397 for freebsd-wireless@freebsd.org; Tue, 28 May 2013 04:55:31 -0700 (PDT) (envelope-from david) Date: Tue, 28 May 2013 04:55:31 -0700 From: David Wolfskill To: freebsd-wireless@freebsd.org Subject: iwn(4) link down/up cycling Message-ID: <20130528115531.GO1334@albert.catwhisker.org> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="Zvl510+jvRFHh8wJ" Content-Disposition: inline User-Agent: Mutt/1.5.21 (2010-09-15) X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list Reply-To: David Wolfskill , freebsd-wireless@freebsd.org 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 11:55:32 -0000 --Zvl510+jvRFHh8wJ Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable 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=3D0x028000 card=3D0x11218086 chip=3D0x4235808= 6 rev=3D0x00 hdr=3D0x00 vendor =3D 'Intel Corporation' device =3D 'Ultimate N WiFi Link 5300' class =3D network iwn0@pci0:3:0:0: class=3D0x028000 card=3D0x12118086 chip=3D0x4237808= 6 rev=3D0x00 hdr=3D0x00 vendor =3D 'Intel Corporation' device =3D 'PRO/Wireless 5100 AGN [Shiloh] Network Connection' class =3D 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 --=20 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. --Zvl510+jvRFHh8wJ Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.20 (FreeBSD) iEYEARECAAYFAlGkmzIACgkQmprOCmdXAD0+DgCdExMeh+K/pyUdAdogyLbRRaht 57UAn1FAGVxYXDQo89kjXpwTKpqlsTWi =0x4a -----END PGP SIGNATURE----- --Zvl510+jvRFHh8wJ--