From owner-freebsd-wireless@FreeBSD.ORG Wed Apr 9 01:31:57 2014 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 9A0574BB; Wed, 9 Apr 2014 01:31:57 +0000 (UTC) Received: from mail.ignoranthack.me (ujvl.x.rootbsd.net [199.102.79.106]) (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 7285A150F; Wed, 9 Apr 2014 01:31:57 +0000 (UTC) Received: from [192.168.1.101] (c-24-6-177-88.hsd1.ca.comcast.net [24.6.177.88]) (using SSLv3 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: sbruno@ignoranthack.me) by mail.ignoranthack.me (Postfix) with ESMTPSA id 16CA71929A9; Wed, 9 Apr 2014 01:31:56 +0000 (UTC) Subject: Re: iwn0 hangs randomly when starting the machine From: Sean Bruno To: Adrian Chadd In-Reply-To: References: <20140331073054.5d7642d6@X220.alogt.com> <1397006320.5173.2.camel@powernoodle.corp.yahoo.com> Content-Type: multipart/signed; micalg="pgp-sha1"; protocol="application/pgp-signature"; boundary="=-cMX9dq9auwirODEPmfTj" Date: Tue, 08 Apr 2014 18:31:55 -0700 Message-ID: <1397007115.5173.4.camel@powernoodle.corp.yahoo.com> Mime-Version: 1.0 X-Mailer: Evolution 2.32.1 FreeBSD GNOME Team Port Cc: "freebsd-wireless@freebsd.org" X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list Reply-To: sbruno@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: Wed, 09 Apr 2014 01:31:57 -0000 --=-cMX9dq9auwirODEPmfTj Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Tue, 2014-04-08 at 18:21 -0700, Adrian Chadd wrote: > Hi, >=20 > 20/40 coex is supposed to be some corner of the spec that notices > whether there's a 20mhz only AP on the extension channel and if so, > flip everyone over to 20MHz. >=20 > Is your DIR825 2GHz channel set to 20mhz or 40mhz? >=20 >=20 > -a=20 Well ... this goofy DLink firmware doesn't let you toggle the 20/40 coexistence radio button if you set the channel width to 20mhz only, so its still on "auto 20/40" in order to toggle the 20/40 coexistence off. Does that make sense at all? sean --=-cMX9dq9auwirODEPmfTj Content-Type: application/pgp-signature; name="signature.asc" Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQEcBAABAgAGBQJTRKMLAAoJEBkJRdwI6BaHZHAH/jn3YKPEFDqzNIkP4XWgxX71 GT7EuWrXVoZP65L65S7fPatlnD4OX42kGMqWByEMaFb+EUY4s8F+VssM6KTV8Pdn XVXufCbUaljzM9tXGKATeM5qdcuSwrM86p257j0Ttj8E/1H3BYo0q9nVhOyUZQgH 2dZrX8zW0En4pA/COgzVjYgXjglaVnmICoXbUDkrEhe7gO8to+y+67BFk0qtwGyL 0zMWdkoeWSzmWfy6nVN6IVgleshypkvPqvrwo48sLhfSVwGSTM1Isy1rZIKefh7M zo2nQ1wUEUcgbW/mUV2Y3DO/a+ABGy804OyaO6FZVwM/8tUx+Ms+BBW2xtqCgiU= =rFQn -----END PGP SIGNATURE----- --=-cMX9dq9auwirODEPmfTj--