From owner-freebsd-current@FreeBSD.ORG Sun May 29 02:07:55 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B00BE16A41C for ; Sun, 29 May 2005 02:07:55 +0000 (GMT) (envelope-from emil@cs.rmit.edu.au) Received: from ppp162-47.static.internode.on.net (ppp162-47.static.internode.on.net [150.101.162.47]) by mx1.FreeBSD.org (Postfix) with ESMTP id 21CB943D48 for ; Sun, 29 May 2005 02:07:54 +0000 (GMT) (envelope-from emil@cs.rmit.edu.au) Received: by ppp162-47.static.internode.on.net (Poofix, from userid 1001) id B170C6218; Sun, 29 May 2005 12:07:53 +1000 (EST) Date: Sun, 29 May 2005 12:07:53 +1000 From: Emil Mikulic To: Sam Leffler Message-ID: <20050529020753.GA78539@dmr.ath.cx> Mail-Followup-To: Emil Mikulic , Sam Leffler , freebsd-current@freebsd.org References: <20050522110627.GA48162@dmr.ath.cx> <4290B89E.1040107@errno.com> <20050528100219.GC75204@dmr.ath.cx> <4298B3A9.9050906@errno.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4298B3A9.9050906@errno.com> X-PGP-ID: 1024D/344A699F X-PGP-Fingerprint: EE97 2C84 6D07 E76C F075 C0BA ED2A 9319 344A 699F X-Written-On: dmr.ath.cx (FreeBSD 6.0-CURRENT i386) User-Agent: Mutt/1.5.9i Cc: freebsd-current@freebsd.org Subject: Re: ath0 goes down periodically X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 29 May 2005 02:07:55 -0000 On Sat, May 28, 2005 at 11:08:41AM -0700, Sam Leffler wrote: > I thought you had a machine using the ath driver and acting as an ap. Sorry if I confused the situation: I have both an AP and a client, both with the same kind of ath card, both running FreeBSD. > when the machine acting as an ap stops working can you see still > see beacon frames being transmitted? > > To do this you need to have another machine. If the other machine is a > client to the ap and using an ath card then 80211stats should show the > count of beacon frames processed growing. Otherwise you can use tcpdump > on the other machine to see beacon frames using something like: > > tcpdump -i ath0 -y IEEE802_11 Got it. Thanks. Next time it happens, I'll do what you said. > If your problem is that the ap stops broadcasting beacons then all data > frames will backup behind because normal data frames are queued on a > different h/w tx queue that will be blocked by the inability to xmit the > beacon frames. That sounds like it could be the case, but I can't yet confirm that the beacons are stuck. I'll get back to you as soon as it happens again. Thanks for your time, and all the great work you're doing, Sam! --Emil