From owner-freebsd-net@FreeBSD.ORG Thu Mar 26 02:21:34 2015 Return-Path: Delivered-To: net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 681F66C1; Thu, 26 Mar 2015 02:21:34 +0000 (UTC) Received: from albert.catwhisker.org (mx.catwhisker.org [198.144.209.73]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 14DBF8C6; Thu, 26 Mar 2015 02:21:33 +0000 (UTC) Received: from albert.catwhisker.org (localhost [127.0.0.1]) by albert.catwhisker.org (8.14.9/8.14.9) with ESMTP id t2Q2LW84029138; Wed, 25 Mar 2015 19:21:32 -0700 (PDT) (envelope-from david@albert.catwhisker.org) Received: (from david@localhost) by albert.catwhisker.org (8.14.9/8.14.9/Submit) id t2Q2LWfh029137; Wed, 25 Mar 2015 19:21:32 -0700 (PDT) (envelope-from david) Date: Wed, 25 Mar 2015 19:21:32 -0700 From: David Wolfskill To: Adrian Chadd Subject: Re: iwn(4) works (mostly) in stable/10; fails to associate in head Message-ID: <20150326022132.GI7594@albert.catwhisker.org> References: <20150323131918.GN7594@albert.catwhisker.org> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="1IYcr18XUmgwOrO2" Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.23 (2014-03-12) Cc: "net@freebsd.org" 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: Thu, 26 Mar 2015 02:21:34 -0000 --1IYcr18XUmgwOrO2 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Mar 25, 2015 at 06:17:48PM -0700, Adrian Chadd wrote: > Hi, >=20 > I'm unfortunately too busy to really help you dig into it. >=20 > I'd start by using tcpdump on wlan0 to see what's going on - see if > it's sending/receiving DHCP responses. Well, in head, it won't even associate, so I suspect that DHCP is a moot point. > Then I'd look at if_iwn_debug.h and enable TX/RX debugging - see if > it's actually transmitting the DHCP requests and the TX status code is > OK rather than one of the errors. > .... Thanks for the hints/tips.... Peace, david --=20 David H. Wolfskill david@catwhisker.org Those who murder in the name of God or prophet are blasphemous cowards. See http://www.catwhisker.org/~david/publickey.gpg for my public key. --1IYcr18XUmgwOrO2 Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQJ8BAEBCgBmBQJVE20rXxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQ4RThEMDY4QTIxMjc1MDZFRDIzODYzRTc4 QTY3RjlDOERFRjQxOTNCAAoJEIpn+cje9Bk7J0oP/2Sx25gzFmlnv230qlLzWcmw JNAiXz/l+dklsqS6RW3h72kcJ92bszY7/L8QH1mWoxGk6HSO0h7mpvv8Wg0QyAhB wK9MDOStqXw4SwAAYAq+1RouJZFN5Lm/ZYruEgcfAZurhgIN3jGDxuSTifOjbnLe SD6Bj1atKRMql4sM0gypvi81qnnK7IpVCoARZbgbjE5IPoYg45CgZURCRBjvxGtc 0sRlcWVk2AP0HB+TJuBizAufeZBMZIjDefAgh2TaDgI+E0iU0Ucl8Hccp3WeQ2NP VuqYaRbUd81miQwiNde1wDHoNCx41lO6KH3PaC8WI3KhsKbhxsSkWE5sCl9vox1S saDMgGIDdl9/lDzeFuuhNzotB9XuFi8/Tx0wUpOAvClS7uNEIeyJe8Q2TsRherYT uNQdhW9O6w5zp+fRlfQWcUyYrf+sc0nJ1dUgxSpJ+h5Dv3I8DN2U4hEsljE9pEYu 9iqElVAztkqxd80HTeCBezk7oP1V6wO4u1zbLdoQv0Ev7JQ7WxRUhagECPX2UyWd dKxTSnIJhLLDEZu2iQ2NoG8FujG+HGVRx871fAgU1tWNy3AetyGjeSqfg/a8q94a upz8cpdN9y5wVa8edjZEnLDMEcCImYgsGw0TNNPPjFmAThZ0DcYynKjzGd4HZ6Lz A11ArYix0BLuaci0jAbX =xSg+ -----END PGP SIGNATURE----- --1IYcr18XUmgwOrO2--