Date: Sun, 29 May 2005 12:07:53 +1000 From: Emil Mikulic <emil@cs.rmit.edu.au> To: Sam Leffler <sam@errno.com> Cc: freebsd-current@freebsd.org Subject: Re: ath0 goes down periodically Message-ID: <20050529020753.GA78539@dmr.ath.cx> In-Reply-To: <4298B3A9.9050906@errno.com> References: <20050522110627.GA48162@dmr.ath.cx> <4290B89E.1040107@errno.com> <20050528100219.GC75204@dmr.ath.cx> <4298B3A9.9050906@errno.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20050529020753.GA78539>