Using a wireless LAN, I was having trouble when I started getting far enough away to start pulling from -80 to -90 db’s @ 1Mb/s transfer speed to the router. Lots of “refresh”'es necessary to get a page to load…
So, I was thinking of making an antenna…directional, tunable for specific channels in the 2.4 ghz ranges, etc.
But, before I do something like that, I was thinking, nah, let me read a little bit on-line. Came up with some stuff to do to the router (like jacking up the signal strength, installing a directional on the AP versus the compy, etc.), but it was not recommended to crank them up really high (read: rf signals and cancer), and the chances of destroying (“bricking”) the router trying to play with signal strength wasn’t worth it.
By trial and error and some understanding of how TCP/IP works on an optimized wired network, I found some settings in the Windows Registry that make a greater distance possible with a wlan card…without a directional antenna and without flashing the OS on a WRT54GL wireless AP and risking a bricked router. Read on…
OK, so I’m thinking maybe I have a decent signal, it’s just weak. Maybe the link to the AP’s getting interrupted, I don’t know exactly what’s happenning?
How can I figure it out…using NetStumbler, of course!!! NetStumbler is a program (located here http://www.netstumbler.com/downloads/) that allows charting signal strength versus time to allow you to map out in real time a particular AP’s signal strength at a given time during the scan.
So I walk out, yeah, I get a good -86 to -90 on that one corner of the house consistently. Consistent quality signal everywhere, just weaker than usually acceptable (for a “Default” OS anyway).
OK I can work with this…plug everything in and start tweaking.
regedit.exe:
…nav over to
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters]
This registry key holds the values for TCP/IP service paramaters. There’s a bunch of settings that do not get put in there by default in a base OS install. They are described here:
http://support.microsoft.com/kb/314053
So I know I have a clean signal, but it’s weak. I’ll try dynamically reducing packet fragmentation client side, increase response tries and packet request tries, send shorter interval keep-alives, and limit the TCP maximum number of connections and reduce the time tcp time-wait state is held…
Here’s the additional numbers I came up with for a signal in the -86 to -90 dbs range:
[code=regedit4.reg]
REGEDIT4
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters]
"EnablePMTUBHDetect "=dword:00000001
“IGMPLevel”=dword:00000000
“KeepAliveTime”=dword:00600000
“TcpMaxConnectRetransmissions”=dword:00000003
“TcpMaxDataRetransmissions”=dword:00000006
"TcpNumConnections "=dword:00000120
"TcpTimedWaitDelay "=dword:00000010
Basically, I tweaked the TCP settings to allow for a more "sloppy" or "lazy" connnection and made it so that less things were being held in a state where the OS had to keep track of it.
Results: less interrupted page loads in browser (IOW, less dropped packets due to retransmission request time and number of times being hit).