Re: ath0 timeout problem - again

2006-12-31 Thread JoaoBR
On Sunday 31 December 2006 01:33, Sam Leffler wrote: > JoaoBR wrote: > > On Saturday 30 December 2006 18:29, Sam Leffler wrote: > >> See my previous reply to you. Lamont is directing you to look for > >> stations in your network operating with power save enabled. > > > > even if there are stations

Re: ath0 timeout problem - again

2006-12-31 Thread JoaoBR
On Sunday 31 December 2006 01:31, Sam Leffler wrote: > >>> I really do not know what this event means (ether type 5e4), for my > >>> understandings it is vague in the source, so I am lost here > >> > >> Seems pretty clear: it's the type field extracted from the ethernet > >> header of the oversized

Re: ath0 timeout problem - again

2006-12-30 Thread Sam Leffler
JoaoBR wrote: > On Saturday 30 December 2006 18:37, Sam Leffler wrote: >> JoaoBR wrote: >>> 572 cabq frames transmitted >>> 11 cabq xmit overflowed beacon interval >>> >>> >>> media: IEEE 802.11 Wireless Ethernet DS/11Mbps mode 11b >> So one other thing came to mind. If your ap is operati

Re: ath0 timeout problem - again

2006-12-30 Thread Sam Leffler
JoaoBR wrote: > On Saturday 30 December 2006 18:29, Sam Leffler wrote: >> See my previous reply to you. Lamont is directing you to look for >> stations in your network operating with power save enabled. >> > > even if there are stations with powersaving on we can do anything against it > > this

Re: ath0 timeout problem - again

2006-12-30 Thread Sam Leffler
JoaoBR wrote: > On Saturday 30 December 2006 18:20, Sam Leffler wrote: > > thank you for answering, lots of good points and I will try to answer any of > them > > >>> I really do not know what this event means (ether type 5e4), for my >>> understandings it is vague in the source, so I am lost h

Re: ath0 timeout problem - again

2006-12-30 Thread JoaoBR
On Saturday 30 December 2006 18:37, Sam Leffler wrote: > JoaoBR wrote: > > 572 cabq frames transmitted > > 11 cabq xmit overflowed beacon interval > > > > > > media: IEEE 802.11 Wireless Ethernet DS/11Mbps mode 11b > > So one other thing came to mind. If your ap is operating in 11b and yo

Re: ath0 timeout problem - again

2006-12-30 Thread JoaoBR
On Saturday 30 December 2006 18:29, Sam Leffler wrote: > > See my previous reply to you. Lamont is directing you to look for > stations in your network operating with power save enabled. > even if there are stations with powersaving on we can do anything against it this is an ISP environment whe

Re: ath0 timeout problem - again

2006-12-30 Thread JoaoBR
On Saturday 30 December 2006 18:20, Sam Leffler wrote: thank you for answering, lots of good points and I will try to answer any of them > > > > I really do not know what this event means (ether type 5e4), for my > > understandings it is vague in the source, so I am lost here > > Seems pretty c

Re: ath0 timeout problem - again

2006-12-30 Thread Sam Leffler
JoaoBR wrote: > On Thursday 28 December 2006 21:52, you wrote: >> check this message: >> >> http://lists.freebsd.org/pipermail/freebsd-stable/2006-December/031216.html >> >> run "/usr/src/tools/tools/net80211/wlandebug/wlandebug -i ath0 power" and >> see if one of the hosts on your wlan has powersa

Re: ath0 timeout problem - again

2006-12-30 Thread Sam Leffler
JoaoBR wrote: > I need some help here, this is not a single case, I get this on a several > machines, this is releng_6 , recent, but old problem getting ugly > > > first I get this kind of events in messages, independent if it is client mode > or hostap or adhoc > > Dec 28 16:50:53 ap1-cds ker

Re: ath0 timeout problem - again

2006-12-30 Thread Sam Leffler
JoaoBR wrote: > 572 cabq frames transmitted > 11 cabq xmit overflowed beacon interval > > media: IEEE 802.11 Wireless Ethernet DS/11Mbps mode 11b So one other thing came to mind. If your ap is operating in 11b and you have many multicast frames q'd up for power save stations then they

Re: ath0 timeout problem - again

2006-12-29 Thread JoaoBR
On Thursday 28 December 2006 21:52, you wrote: > check this message: > > http://lists.freebsd.org/pipermail/freebsd-stable/2006-December/031216.html > > run "/usr/src/tools/tools/net80211/wlandebug/wlandebug -i ath0 power" and > see if one of the hosts on your wlan has powersaving turned on. > > "s

Re: ath0 timeout problem - again

2006-12-29 Thread Lamont Granquist
check this message: http://lists.freebsd.org/pipermail/freebsd-stable/2006-December/031216.html run "/usr/src/tools/tools/net80211/wlandebug/wlandebug -i ath0 power" and see if one of the hosts on your wlan has powersaving turned on. "stops forever" was not one of my symptoms though, so your

ath0 timeout problem - again

2006-12-28 Thread JoaoBR
I need some help here, this is not a single case, I get this on a several machines, this is releng_6 , recent, but old problem getting ugly first I get this kind of events in messages, independent if it is client mode or hostap or adhoc Dec 28 16:50:53 ap1-cds kernel: ath0: discard oversize fr