I can understand that you would get rx errors from interference but not tx. The router is sat in the middle of an open plan office, no microwaves, no TV's, no cordless phones etc. nothing I can really think of to cause any interference. after 10 hours of uptime I have 71% success on TX, 100% on RX
Received (RX) 100% 134978 OK, no error
Transmitted (TX) 71% 1077467 OK, 442931 errors
Basically the question is, is it normal to have an error count so high if not does anyone know a beter firmware version that could help?
Joined: 10 May 2008 Posts: 1380 Location: Pacific North West, USA
Posted: Wed Sep 08, 2010 7:47 Post subject:
Stick with 13525 for the WRT54G's - one of the better builds for them.
As far as error testing - try the following:
Do a Wiviz survey or Site survey and see what channels are being used around you.
Maybe if you switched to another channel thats not being used, you would have better TX rates.
Also, does anyone in the office use Wireless headsets?
Bluetooth is another common interference as well.
Wireless headsets and Bluetooth both operate in the 2.4ghz range and can cause interference. _________________ Soylent Green Is People !
=-=-=-=-=-=-=-=-=-=-=
Netgear Nighthawk R7000 - DD-WRT Build R46220
Linksys EA8500 - OpenWRT IPQ806x Trunk R16375 5.4 Kernel
Another thing you could try is setting the beacon interval to a more frequent setting. By default it is at 100. I have changed mine to 95 and it seems to have decreased the Tx errors significantly.
Do a Wiviz survey or Site survey and see what channels are being used around you.
Done. No other networks in the area, we really are quite isolated!!
Quote:
Maybe if you switched to another channel thats not being used, you would have better TX rates.
Tried 1, 6, 8, 11 all the same
Quote:
Also, does anyone in the office use Wireless headsets?
No headsets
Quote:
Bluetooth is another common interference as well.
Wireless headsets and Bluetooth both operate in the 2.4ghz range and can cause interference
I suppose there will be some bluetooth but nothing major, there are only 20 people in a 2500 sq/ft office.
Quote:
Another thing you could try is setting the beacon interval to a more frequent setting. By default it is at 100. I have changed mine to 95 and it seems to have decreased the Tx errors significantly.
Trying this at the moment, but doesn't seem to be having much of an effect
Even with the errors wireless seems to be functioning OK. I am just trying to find what could be causing the errors.
Those type of errors are almost always a signal problem. However try using different/no enryption to test, and make sure there are not conflicts with dhcp service. Seems to me there was something similar in the past with someone using a windows server. _________________ I fix "shortcuts". If you don't have time to read thoroughly, I don't have time to re-type what you missed.
Joined: 04 Mar 2008 Posts: 160 Location: Charlotte, NC
Posted: Thu Sep 09, 2010 22:53 Post subject:
blaughtmon wrote:
DSMunky
Another thing you could try is setting the beacon interval to a more frequent setting. By default it is at 100. I have changed mine to 95 and it seems to have decreased the Tx errors significantly.
Just another thought
Anyone know of a way to check the accuracy of the timing of a unit. I'm sure 100 ms is +/- some percentage which would account for having to tweak this value.