From owner-freebsd-mips@FreeBSD.ORG Tue Nov 23 16:44:00 2010 Return-Path: Delivered-To: freebsd-mips@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 4B3271065673; Tue, 23 Nov 2010 16:44:00 +0000 (UTC) (envelope-from larry.vaden@gmail.com) Received: from mail-ww0-f50.google.com (mail-ww0-f50.google.com [74.125.82.50]) by mx1.freebsd.org (Postfix) with ESMTP id A84B18FC0C; Tue, 23 Nov 2010 16:43:59 +0000 (UTC) Received: by wwd20 with SMTP id 20so8520245wwd.31 for ; Tue, 23 Nov 2010 08:43:58 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:sender:received :in-reply-to:references:date:x-google-sender-auth:message-id:subject :from:to:cc:content-type; bh=ZExMKBrwnloRDIS4STVYAJSuBE8u3Ra/ogNn9CVSekQ=; b=jANaR8vOGeLIlwM+/qyR8Eq5edUA3HKVOo4pVbGHQhKmr7E/IvI4wPcIZ1uq6LBOv3 6gsc9lhG9eTcSxzzcbJ+ZRkm2ttVkYtCTDQUGAuqphwhoohe3L29QwG1qwNOnk91JgKT Q7DF770LygVa4sM6mgzyPMCKrJtFWl4sIE/EA= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; b=n3Ik/ChwTtKkoYy+00A8BqQIkgjadq/+HBXO1C4WxkPPdMvfTW0CLVx2kOUX0lCoet Ef78ZZvZtWUlOjNncDDQVNWeYM935bkQXzSGD8uB8N3S3ACK8TZDieCSuZMIHgYw7Pb7 7qS2oAFflLJ/+6zkD8vLPlMJCIhRA0c3xzAf8= MIME-Version: 1.0 Received: by 10.227.174.206 with SMTP id u14mr7876652wbz.40.1290530637447; Tue, 23 Nov 2010 08:43:57 -0800 (PST) Sender: larry.vaden@gmail.com Received: by 10.216.242.12 with HTTP; Tue, 23 Nov 2010 08:43:57 -0800 (PST) In-Reply-To: References: Date: Tue, 23 Nov 2010 10:43:57 -0600 X-Google-Sender-Auth: D8ZQAStZTmIwcbER_Zx55QEdAGc Message-ID: From: Larry Vaden To: Adrian Chadd Content-Type: text/plain; charset=UTF-8 Cc: freebsd-mips@freebsd.org Subject: Re: does anyone have a recommendation for a solid FreeBSD-based 802.11b/g/n AP package for MIPS-based APs and CPEs? X-BeenThere: freebsd-mips@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to MIPS List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 23 Nov 2010 16:44:00 -0000 On Tue, Nov 23, 2010 at 9:30 AM, Adrian Chadd wrote: > > I've no idea. I haven't at all looked at WDS. > > As Sam likely pointed out, stuck beacons can include: > > * because the RF environment is somehow hilariously bad, congested or > dirty (seen this); > * because the code needing to setup the beacon frames, flush it to RAM > before the TBTT (and related) timers fire just doesn't get a chance to > run (seen this); > * because your backend PCI bus/CPU/FSB bus/etc is busy, and thus the > beacon frame doesn't go out in time (haven't seen this); > * because the chip is being fondled in the wrong way somehow and it's > locking up something (definitely seen this.) > > It's just a shame that people focus on "stuck beacon!" rather than > trying to figure out what other events are occuring at the same time. > :-) > > To track down stuck beacons at my wireless contract, I ended up doing > a -lot- of instrumentation to try and figure out what was going on > when stuck beacons occured. For example, stuck beacons were occuring > in the deep past because the initial noise floor calibrations were > being done every 1/10th of a second during a periodic calibration > (every 20 minutes), rather than every few seconds, and this tended to > upset the radio. > > Adrian Adrian, Thanks for your reply. I agree with you and we are trying to understand the underlying causes and what can be done. I also agree that changing the intervals can help; we found that a beacon interval of 200-250 msec resulted in better latency for subscribers, but that higher beacon intervals seemed to be unstable (CPEs would reassociate every few seconds). This was on Ubiquiti gear. AFAIK, the beacon interval on Mikrotik's RouterOS is fixed at 100 msec (read: not under operator control), and the recalibration interval is 00:01:00, also not under operator control. In these cases, I refer to WinBox, not the CLI, which I haven't checked. kind regards/ldv