From owner-freebsd-current@FreeBSD.ORG  Sat May 28 10:02:34 2005
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
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 A492D16A41C
	for <freebsd-current@freebsd.org>; Sat, 28 May 2005 10:02:34 +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 23C0C43D48
	for <freebsd-current@freebsd.org>; Sat, 28 May 2005 10:02:32 +0000 (GMT)
	(envelope-from emil@cs.rmit.edu.au)
Received: by ppp162-47.static.internode.on.net (Poofix, from userid 1001)
	id B83F76218; Sat, 28 May 2005 20:02:19 +1000 (EST)
Date: Sat, 28 May 2005 20:02:19 +1000
From: Emil Mikulic <emil@cs.rmit.edu.au>
To: Sam Leffler <sam@errno.com>
Message-ID: <20050528100219.GC75204@dmr.ath.cx>
Mail-Followup-To: Emil Mikulic <emil@cs.rmit.edu.au>,
	Sam Leffler <sam@errno.com>, freebsd-current@freebsd.org
References: <20050522110627.GA48162@dmr.ath.cx> <4290B89E.1040107@errno.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <4290B89E.1040107@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
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>, 
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sat, 28 May 2005 10:02:34 -0000

On Sun, May 22, 2005 at 09:51:42AM -0700, Sam Leffler wrote:
> Emil Mikulic wrote:
> >At home I have a FreeBSD 6-CURRENT machine with an ath card acting as
> >an access point.  Every once in a while, wireless traffic stops and I
> >have to log in to this machine and manually bounce the interface to
> >get it going again.
> 
> When this happens can you see beacons being xmit'd by the ap?  Also
> the output of athstats (src/tools/tools/ath) may be useful.

As well as the AP machine, I have a FreeBSD 5-STABLE machine upstairs
which is a WiFi client.  On which machine do you want me to turn debugging
on, and which flags?

I've played around with /usr/src/tools/tools/ath/athdebug.c and
/usr/src/tools/tools/ath/80211debug.c before.

What I remember is:

 - using one of the two tools to set some some flag lets me see beacons
   =)

 - not to turn on certain flags on the AP machine since it has a serial
   console and the flood of debugging output makes it grind to a halt
   =/

Is there an easy way around this?  Or do I only need to watch for
beacons on the client machine?

--Emil