From owner-freebsd-wireless@FreeBSD.ORG Wed Apr 9 03:32:59 2014 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id EFFA2261; Wed, 9 Apr 2014 03:32:59 +0000 (UTC) Received: from alogt.com (alogt.com [69.36.191.58]) (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 C69391062; Wed, 9 Apr 2014 03:32:59 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=alogt.com; s=default; h=Content-Transfer-Encoding:Content-Type:MIME-Version:References:In-Reply-To:Message-ID:Subject:Cc:To:From:Date; bh=oh6JtMe2D9oruCanTmo+ubTp37Q3DhneI4fCPEu5lNg=; b=vmCbvbS8ChahK4K3ix8aAnffRTUEqlKjphyo4giYW7T3iiKw3oMh/ANu2eDLq3KS36mHFVts9QfXdqfZqUmi9m9hleUNw/xMC2hNWF0yzCSC++iFxY42+VFPHjiRIlHxW2hvC0KQ27DaoGXjw+kPRAAEZfSx3mtF/dM3wLWe/Gk=; Received: from [182.55.101.96] (port=21624 helo=X220.alogt.com) by sl-508-2.slc.westdc.net with esmtpsa (SSLv3:DHE-RSA-AES128-SHA:128) (Exim 4.82) (envelope-from ) id 1WXjFy-003w4e-9T; Tue, 08 Apr 2014 21:32:58 -0600 Date: Wed, 9 Apr 2014 11:32:54 +0800 From: Erich Dollansky To: Adrian Chadd Subject: Re: iwn0 hangs randomly when starting the machine Message-ID: <20140409113254.3a3277a3@X220.alogt.com> In-Reply-To: References: <20140331073054.5d7642d6@X220.alogt.com> <1397006320.5173.2.camel@powernoodle.corp.yahoo.com> <20140409093642.19c2f5cb@X220.alogt.com> X-Mailer: Claws Mail 3.9.3 (GTK+ 2.24.22; amd64-portbld-freebsd10.0) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - sl-508-2.slc.westdc.net X-AntiAbuse: Original Domain - freebsd.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - alogt.com X-Get-Message-Sender-Via: sl-508-2.slc.westdc.net: authenticated_id: erichsfreebsdlist@alogt.com X-Source: X-Source-Args: X-Source-Dir: Cc: "freebsd-wireless@freebsd.org" , sean bruno X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.17 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: Wed, 09 Apr 2014 03:33:00 -0000 Hi, On Tue, 8 Apr 2014 20:07:39 -0700 Adrian Chadd wrote: > Coexistence is to deal with the fact that a 40MHz channel may overlap > a 20MHz-only AP in the extension channel. > > If the AP finds a 20MHz AP in the extension channel (ie, the other > half of its 40MHz) channel then it'll flip itself to 20MHz. If it > determines it isn't there any more, it'll flip the BSS to the 40MHz > channel. > > Now, why the hell it's causing the connection to fail? I have no idea. > > can someone file a PR that says it's all busted with 40MHz coxistence > enabled? We can then start debugging from that position. > I am not so sure if it is a general problem or just a DLink problem. I just activated my own access point and it worked there. The only problem is that it also works with DLink but only randomly. So, it still could have been that I was just always lucky when connecting to the ProLink access point I have. As the DLink is not mine, I am not even able to access its administration interface. Can I suggest to wait a bit to get more feedback to see if it is a general problem or a problem only linked to one manufacturer? Erich