1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

Tweaking Fragmentation & RTS thresholds and beacon interval

Discussion in 'Networking Issues' started by astehn, Oct 26, 2008.

  1. astehn

    astehn Addicted to LI Member

    I've got a WPA wireless network set up that utilizes a total of 4 WRT54GL routers running Tomato 1.21 as access points (on channels 1, 6, and 11 [the two APs furthest from each other both utilize 11). Each AP generally supports about 5 clients at a time (though sometimes as high as 10).

    Generally, everything is working, but the clients furthest from the access points occasionally lose their connections, and some users have reported periods when they are completely unable to obtain an IP. I am virtually certain that this is based on poor signal strength resulting from distance from the APs and/or RF interference from other APs in the building. From the Device List in tomato, I'm able to see that the users having connectivity issues generally show an RSSI of around -89dBm with a quality of 10 (the Noise Floor is -99dBm).

    I have done everything possible to improve signal strength by router placement, optimizing channel usage based upon RF surveys, using 84mw transmit power, and upgrading to high-gain omnis. This leaves nothing to do apart from tweaking the advanced wireless settings to marginally improve problems related to weak signal and/or RF interference, so I've been reading everything I can find on these boards and elsewhere about changing Fragmentation Threshold, RTS threshold, and beacon interval. However, I'm left with the following questions.

    1) There seems to be disagreement about Fragmentation threshold and RTS threshold settings. Generally, I understand what the settings do, but I am reluctant to change them when there doesn't seem to be a consensus about exactly what they should be. Some (including the Linksys Technical Troubleshooting Wizard) recommend that both be set to 2304. I have also seen people insist that Fragmentation be set to 2306 and RTS to 2304. A few recommend 2306 for both thresholds, and some advise 2306 for Fragmentation and 2307 for RTS (though by my limited understanding, it simply disables RTS when the value is higher than the fragmentation threshold value). Which of these settings is best? And more importantly, WHY is it the best?

    2) With respect to beacon interval, I'm a little less clear as to exactly WHY this would improve connectivity, mostly because it's hard to understand why a client would see much difference between, say 10 beacons a second and 20 beacons a second). I've seen both 75ms and 50ms recommended to replace the default of 100ms. For a network of my size (4 APs, averaging 5 users each), will increasing the number of beacons (and hence the RF traffic even when the network is idle) pose a problem? If not, should I use 75ms or 50ms? Will more frequent beacons decrease the lifespan of the radio?

    Since these settings will affect all users, I want to make sure that I'm using settings that will be beneficial on the whole. The last thing I want to do is inadvertantly make things worse, and since I can't test things directly from the standpoint of each user, I was hoping that someone could explain to me in greater detail what settings I should try and, more importantly, why.

    Thank you for your help!
  2. cg770

    cg770 Network Guru Member

    Hi astehn,

    I run a similar setup with a WRT54G and Tomato 1.21, but in addressing the problem you're having I would focus on the client side and draw from my experience in long distance piggybacking.

    Signal quality 10 is very low, barely useable even at low speed. If your external antenna doesn't have a wire, consider upgrading. I bought a $6 magnetic mount eBay unit with 2 meters of cable that works great. Being able to move the antenna around a bit makes a world of difference. A metal mount is not necessary.

    If you enable (lower) the RTS and Fragment threshold on the routers, everyone suffers higher overhead. However, you can do so at the client side and get better range with less retrys.

    The best solution I have found is to obtain & install the chipset utility for each particular client. An AT&T card or a Zyxtel card will come with their own utility, but the chipset will be made by a major mfg, like Cisco, Realtek, or Atheos.

    Something like PC Wizard can tell you the model number of the card, Google for the chipset. Install the utility provided by the chipset mfg and perhaps their own driver as well. Often these will give you many more options and much more feedback on what the connection is really doing.

    Of course, if your existing WLAN utility or device driver has RTS and Fragment threshold settings, access them. On the client side, it won't hurt anything to tweak them. If your utility displays packets and retrys, you can really see what you're doing.

    To enable RTS and Fragment, set them below your MTU. RTS 1216 and Threshold 1184 are good starting points. When set at max, they are basically disabled.

    Of course, an inexpensive antenna with a wire will be the quick and easy solution, if it works for you. Moving it around while watching a signal strength meter (NetStumbler)can really make a whopping difference.

Share This Page