On Monday 01 December 2003 05:25 pm, Leo Bicknell wrote:
> In an effort to cut down on Sam's load...
>
> This is a known issue. Evidently there are some low level radio
> counters that are incorrectly being reported as input errors.
> Basically they should be ignored until the driver can be change
Hi Leo.
Thanks for the information, but do you know if is some thing to do
to fix this? or simply I need wait for another driver version, because
the driver looks so much better than a couple a week ago, the only bad
thing is this problem and when happen kill all the wireless network
Thanks
Hi there.
I running an script every 4 sec. on my Freebsd Atheros Access Point to
log the netstat errors and I can confirm every time I have more than 3
Ierrs per sec or Oerrs per sec.. my ping to the clients box start to
be very high and the connection work very slow until the error go down
In an effort to cut down on Sam's load...
This is a known issue. Evidently there are some low level radio
counters that are incorrectly being reported as input errors.
Basically they should be ignored until the driver can be changed
to not report them.
--
Leo Bicknell - [EMAIL PROTECTE
Hi there.
I running an script every 4 sec. on my Freebsd Atheros Access Point to
log the netstat errors and I can confirm every time I have more than 3
Ierrs per sec or Oerrs per sec.. my ping to the clients box start to be
very high and the connection work very slow until the error go down
aga
