From owner-freebsd-wireless@FreeBSD.ORG Wed Apr 9 03:40:02 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 50F6B66D; Wed, 9 Apr 2014 03:40:02 +0000 (UTC) Received: from mail-qg0-x232.google.com (mail-qg0-x232.google.com [IPv6:2607:f8b0:400d:c04::232]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id F3C9510E1; Wed, 9 Apr 2014 03:40:01 +0000 (UTC) Received: by mail-qg0-f50.google.com with SMTP id q108so1734122qgd.37 for ; Tue, 08 Apr 2014 20:40:01 -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:message-id:subject :from:to:cc:content-type; bh=+Yk+tA25x5/wnEbTVFjr+2+zCn1yIxr3BIKBg/sYgkM=; b=rY808hYbmM+q2N5A/eb8y+bAQqHmtVIchzrqSz1N6C7yzdQOprydGgqnq24skXP7x0 9jdaC6wSHaD0aZ6MKFo4aH5iU66pafMXgoEsDLGsFnoMXr1W82FgonDxOqKMpMxsnOYk eQPgI4UTuguAhdMUoNXocjeNvn7EA2YPI9qMcCG4ivfbOL/WEa5xv6+2+d24zLmqQQ5m KI8jle5A0Oz7Qzo7OBe9GSeWVKjG+WkEuNS6fbPvXZzh52tahrb3ItFiCNHebTavl9Pc ruobUby6v939Gsx8entf7OUS1+4WVPpqqdb+9Bol8jpap/Vuk0yDZr3X1iZmQK4/9Igv st7Q== MIME-Version: 1.0 X-Received: by 10.140.39.103 with SMTP id u94mr9018039qgu.46.1397014801155; Tue, 08 Apr 2014 20:40:01 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.224.50.206 with HTTP; Tue, 8 Apr 2014 20:40:01 -0700 (PDT) In-Reply-To: <20140409113254.3a3277a3@X220.alogt.com> References: <20140331073054.5d7642d6@X220.alogt.com> <1397006320.5173.2.camel@powernoodle.corp.yahoo.com> <20140409093642.19c2f5cb@X220.alogt.com> <20140409113254.3a3277a3@X220.alogt.com> Date: Tue, 8 Apr 2014 20:40:01 -0700 X-Google-Sender-Auth: gyHfuBRiYsOJQGSJEY7C6_jFoMw Message-ID: Subject: Re: iwn0 hangs randomly when starting the machine From: Adrian Chadd To: Erich Dollansky Content-Type: text/plain; charset=ISO-8859-1 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:40:02 -0000 I'm not sure. I'd really like to see what the story is with coexistence somehow. -a On 8 April 2014 20:32, Erich Dollansky wrote: > 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