From owner-freebsd-wireless@FreeBSD.ORG Sat Apr 27 18:56:31 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 E6E8DEE4; Sat, 27 Apr 2013 18:56:31 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-wi0-x22a.google.com (mail-wi0-x22a.google.com [IPv6:2a00:1450:400c:c05::22a]) by mx1.freebsd.org (Postfix) with ESMTP id 5185215B4; Sat, 27 Apr 2013 18:56:31 +0000 (UTC) Received: by mail-wi0-f170.google.com with SMTP id l13so1779889wie.1 for ; Sat, 27 Apr 2013 11:56:30 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=orFkRKqB8KggO4z92dbEaA3qpnrQgliEYb+vBrJd6WI=; b=nbexs32op+AVffGVdCCK3V+fntkA/mgrzQS1Vjx/C4z+QvwIu84m6HygbDmTBp9kyf TFejktJXiE6CXOt1BEV3IrvIYejdjXcQihVuIstisbh2x63M4f5Ob4741n+QgWzA5CH/ iH98F3REeDqdoNowWLTrMZX9rCEYCBDoKFI3SL1aBotCLvs+Ty1nZftaE2puBeVg4v89 ucGDAv6XsSszVLVFRTbe8emWHi7o4OcTxr17+QFZ2ZmWmGoQSdicgOpi2i8Rkn0ytsT9 7tlGk6W1nmLfeJifu2aM2ovDiO+RqcC5/8DrJDursfGjbAKUTf06fd/hBQTyPcM7QCSy r2VQ== MIME-Version: 1.0 X-Received: by 10.194.93.133 with SMTP id cu5mr88697039wjb.56.1367088990408; Sat, 27 Apr 2013 11:56:30 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.217.58.138 with HTTP; Sat, 27 Apr 2013 11:56:30 -0700 (PDT) In-Reply-To: <777510536.20130427123352@serebryakov.spb.ru> References: <2810538978.20130423164137@serebryakov.spb.ru> <1813905823.20130423184528@serebryakov.spb.ru> <184105677.20130424002002@serebryakov.spb.ru> <1936997795.20130424003555@serebryakov.spb.ru> <886711115.20130424004702@serebryakov.spb.ru> <6010292503.20130426001447@serebryakov.spb.ru> <99510815.20130426122508@serebryakov.spb.ru> <777510536.20130427123352@serebryakov.spb.ru> Date: Sat, 27 Apr 2013 11:56:30 -0700 X-Google-Sender-Auth: CZdHd6u1zQP9ys0oD9l2cDBkYGY Message-ID: Subject: Re: New hardware, old problem: stuck beacon when here is WiFi traffic From: Adrian Chadd To: lev@freebsd.org Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Cc: freebsd-wireless@freebsd.org X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.14 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: Sat, 27 Apr 2013 18:56:32 -0000 On 27 April 2013 01:33, Lev Serebryakov wrote: > Hello, Adrian. > You wrote 27 =D0=B0=D0=BF=D1=80=D0=B5=D0=BB=D1=8F 2013 =D0=B3., 1:34:24: > > AC> You're not doing something like leaving bgscan enabled, or not > AC> defining a channel up front? > Here is my config: > > ifconfig_wlan0=3D"inet 192.168.135.1 netmask 255.255.255.0 mode 11ng chan= nel 3:ht/40 -bgscan ssid home.serebryakov.spb.ru country DE regdomain row t= xpower 30" Is it a bridge? If so, put an IP address on the bridge, not wlan0. By putting inet there early on, it's bringing the interface up very early. It's a side effect of hte network stack - if you assign an IP address, the VAP comes up immediately. thus i do the inet line after _all_ other things are done, and on a separate line. Anyway, leave it how it is for now. Just update to the latest -HEAD ath code and redo the testing. It will now log the whole TX queue contents, not just the completed frames. Hopefully it'll be more obvious. Thanks, adrian