WDS won't reconnect after power outage

Discussion in 'Tomato Firmware' started by Jedis, May 29, 2012.

  1. Jedis

    Jedis LI Guru Member

    I'm having an issue where one part of the house is being renovated and needs to have the electricity shut off periodically. Unfortunately, this is the main router and the WDS client will no longer reconnect to the main router without manual intervention.

    From this thread, it appears I can just schedule a 'kill -s HUP 1' to run every morning to reestablish the connection. However, this doesn't help when power is lost during the day.

    Is there a better way to force WDS to reconnect all slaves? I've been fighting with this for days and am ready to just go with client ethernet bridge mode...
  2. Goggy

    Goggy Network Guru Member

  3. mvsgeek

    mvsgeek LI Guru Member

    @Jedis - I feel your pain, I've been struggling with this for a while too. Are you using WPA or WPA2? If WPA, you might take a look at nas4not. I've had limited success with it - sometimes it works, and sometimes it doesn't. Here's a little script to run it:

    # Script to force nas connection to secondary router

    # Get SSID & WPA_PSK

    TRSSID=`nvram get wl0_ssid`
    TRPSK=`nvram get wl0_wpa_psk`

    # If no target router WDS specified, default to 1


    if [ "$1" != "" ]; then

    # execute nas4not

    echo executing : nas4not lan "$TRWDS" up auto aes psk "$TRPSK" "$TRSSID"...
    nas4not lan "$TRWDS" up auto aes psk "$TRPSK" "$TRSSID"
    echo nas4not is running with pid `pidof nas4not`
    echo kill nas4not processes after successful completion...
    sleep 10
    kill -9 `pidof nas4not`

    exit 0
  4. Jedis

    Jedis LI Guru Member

    Thanks Goggy. I will try that.

    mvsgeek, unfortunately I am running WPA2, so I do not believe that script will work. Thanks for the effort though :)
  5. mvsgeek

    mvsgeek LI Guru Member

    I had to revert to WPA from WPA2 after replacing my old "main" router (WRT54GL running Tomato 1.28) with the RT-N16 and Toastman. Couldn't get ANY of the WDS slaves to connect at all using WPA2. However, the benefits of the Toastman/RT-N16 combo far outweigh that minor inconvenience:)

    I also run a "keepalive" script on all slaves, which has about a 90% success rate. As others have noted, once you have a working WDS environment - if it ain't broke, don't fix it:)
  6. Jedis

    Jedis LI Guru Member

    Successfully tested the script in the link Goggy posted. I rebooted both routers and the slave did not pick up the connection right away. Had to wait for the script to fire and then it sorted itself out.

  1. This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
    By continuing to use this site, you are consenting to our use of cookies.
    Dismiss Notice