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

WDS Issues

Discussion in 'Tomato Firmware' started by arrmo, Aug 18, 2012.

  1. arrmo

    arrmo Addicted to LI Member

    Hi,

    Perhaps a dumb question, but ... I have two routers linked by WDS. The link seems to be working, and wds0.1 shows up in the device list for both. So far so good ... :).

    However, devices hanging off the second (slave) router are not getting an IP address (via DHCP), and even with a static configuration I cannot ping the first (master) router.

    Any thoughts?

    Thanks!
     
  2. mvsgeek

    mvsgeek Addicted to LI Member

    You say the link "seems to be working"...

    1. Can you see actual numbers in the TX/RX Rate column on each router?
    2. Can you ping the master from a telnet/ssh session on the slave? Or vice versa?
    3. What brand/model/firmware are your routers?
    4. Which security scheme are you using?

    I suspect that the link isn't really working - the fact that wds0.1 shows up just means that a signal has been detected, but a connection has not necessarily been established (see item 1 above)
     
  3. arrmo

    arrmo Addicted to LI Member

    Hi,

    Thanks for the quick response! Some answers to your questions,
    1) Yes, I can - and also RSSI. Quality is ~ 80, and Tx/Rx Rate is 6/36.
    2) Nope - this is the problem. The wireless link seems to be up, but no ping between them ... :-(.
    3) Two ASUS routers, one RT-N16 (master), the other WL-520GU (slave).
    4) Security is WPA2 Personal, Encryption is TKIP/AES. Also, the wireless channel is the same on both (Ch 10), and Wireless Network Mode is Auto.

    Thoughts?

    Thanks again!
     
  4. mvsgeek

    mvsgeek Addicted to LI Member

    1. What firmware versions are you running?
    2. Is DHCP disabled on the slave?
    3. Is the failed ping from a PC connected to the slave, or from a telnet/ssh session on the slave itself?
    4. Have you tried disabling security, and/or setting wireless mode to 'G only' or 'N only'?
    Questions, questions...:confused:
     
  5. arrmo

    arrmo Addicted to LI Member

    Hi,

    The issue seems to be that you have to force AES - cannot be TKIP / AES as the setting. Then it works fine (though reconnect is a problem, if the connection drops).

    Thanks for the help!!!
     
  6. mvsgeek

    mvsgeek Addicted to LI Member

    Glad you got it working :)
    If you search this forum for "nas4not" you'll find some info about resolving the reconnect issue. The rather sparse nas4not documentation states that it's for WPA only - however, that doc may be out of date, because the version included in the firmware I'm using (see my sig) works for WPA2 also:D .
     
  7. arrmo

    arrmo Addicted to LI Member

    Will take a look - thanks again for all your help!
     

Share This Page