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

Previously perfect WDS, now crap.

Discussion in 'Tomato Firmware' started by wetwilly, Aug 30, 2008.

  1. wetwilly

    wetwilly Addicted to LI Member

    Hello.

    I've been using two WRT54GL with Tomato as a WDS setup and it's been running really well for some months. Recently I noticed that that LAN clients connected to the second WDS were slow and laggy. I've been troubleshooting, done total reset and alot of reconfiguring, changed channel, updated to 1.21 firmware but no solution so far.

    The problem is that there is packetloss in the WDS. Here is a ping sample from AP(10.0.0.1) to second WDS(10.0.0.2)

    Code:
    0	10.0.0.2 (10.0.0.2)	64	64	7.00	
    1	10.0.0.2 (10.0.0.2)	64	64	68.80	61.80
    3	10.0.0.2 (10.0.0.2)	64	64	441.90	373.10
    4	10.0.0.2 (10.0.0.2)	64	64	20.30	-421.60
    6	10.0.0.2 (10.0.0.2)	64	64	455.90	435.60
    7	10.0.0.2 (10.0.0.2)	64	64	13.80	-442.10
    8	10.0.0.2 (10.0.0.2)	64	64	9.70	-4.10
    9	10.0.0.2 (10.0.0.2)	64	64	7.40	-2.30
    10	10.0.0.2 (10.0.0.2)	64	64	13.20	5.80
    11	10.0.0.2 (10.0.0.2)	64	64	8.90	-4.30
    12	10.0.0.2 (10.0.0.2)	64	64	2.30	-6.60
    13	10.0.0.2 (10.0.0.2)	64	64	3.40	1.10
    14	10.0.0.2 (10.0.0.2)	64	64	73.20	69.80
    16	10.0.0.2 (10.0.0.2)	64	64	243.20	170.00
    17	10.0.0.2 (10.0.0.2)	64	64	27.80	-215.40
    19	10.0.0.2 (10.0.0.2)	64	64	26.50	-1.30
    21	10.0.0.2 (10.0.0.2)	64	64	24.30	-2.20
    22	10.0.0.2 (10.0.0.2)	64	64	8.40	-15.90
    23	10.0.0.2 (10.0.0.2)	64	64	23.30	14.90
    24	10.0.0.2 (10.0.0.2)	64	64	27.60	4.30
    
    Round-Trip: 2.3 min, 75.3 avg, 455.9 max (ms)
       Packets: 25 transmitted, 20 received, 20% lost
    :eek:

    When pinging from 10.0.0.2 to 10.0.0.1 its even worse;

    Round-Trip: 2.7 min, 115.1 avg, 424.9 max (ms)
    Packets: 25 transmitted, 19 received, 24% lost

    Screenshots of the current config:
    This is my gateway and WDS AP
    [​IMG]

    This is the second WDS(not configured as AP)
    [​IMG]

    Advanced wireless settings, (exactly the same on both routers)
    [​IMG]

    According to the device list the wireless signal beetwen the two are fine, I don't know if noise floor of -99dBm is good or bad though? The routers are placed less than 10m apart.
    [​IMG]

    Any suggestions for further troubleshooting will be highly appreciated.
     
  2. michse

    michse Addicted to LI Member

    Configure both as ap with wds because that is what you want. maybe use tkip than aes. and you shold not use the "nd" versions (my opinion)

    Michse
     
  3. HennieM

    HennieM Network Guru Member

    Wow, you have strong signal there with the 84mW Tx power.... most likely TOO STRONG, and this is bottoming out your signals, which in turn is causing the packet loss. With the 2 WRTs less than 10m apart, I'd suggest Tx power (on both of course) of around 20mW or less. You need your Rx signal to be max about -50dBm, but preferably around -55 to -60dBm. (Remember -45dB is more that -50dBm).

    The noise margin indicated may be misleading, as this is not measured continuously, so do try different channels with the lower Tx power, like channel 13 - not many people use channel 12 or 13 even in ETSI countries...

    If you lower the Tx strengths, and still have the packet loss, I'd start looking for interference from microwaves, power transformers, or HAM radio operators in your vicinity.

    NEVER USE TKIP if you can use AES! TKIP is a software algorithm, with lots of CPU overhead, which slow you down relative to AES. AES is hardware based, so much less load on the CPU (and slightly better encryption), and thus better speed.

    I don't know if this really makes a difference, but I turn Frameburst on on my WDS links - it does seem to speed up large file transfers a bit.

    What type of wireless clients do you have connected to WDS+AP1? A funny client card/driver could be screwing the wireless around, so perhaps remove all wireless clients, reboot both routers, and see what you get in ping times.

    As a last resort, reset both WRTs to defaults, and respecify all settings. Sometimes old "invisible" settings are retained, and this makes for proplems.
     

Share This Page