WDS drops Wireless Laptops

Discussion in 'Tomato Firmware' started by jlobee, Aug 4, 2008.

  1. jlobee

    jlobee Addicted to LI Member

    I have 2 WRT54GL boxes flashed with Tomato 1.20 firmware. The first router is connected to my Cable Modem, and the second is used as a WDS repeater.

    I have setup the WDS using this guide: http://www.polarcloud.com/tomatofaq#how_do_i_use_wds

    Everything works fine for a day or two, but my notebooks start dropping the wireless connection, and refuse to connect. I disconnect the 2nd WDS repeater router, and everything is back to normal, but once it's connected, wireless gets dropped again.

    I have NVRAM reset both routers and reconfigured them to no avail,
    any suggestions?
  2. TexasFlood

    TexasFlood Network Guru Member

    As a band-aid, you could schedule a reboot of your routers ever night. Nothing like a good reboot. Whenever I have stability issues, that's one of the first things I try. And when I'm gonie traveling, I like to do that to make sure my family doesn't run into issues and that I can access my computers from the road. When I'm on the road, I even have my primary router reboot my cablemodem right before it reboots itself.

    That aside, I've found that they encryption makes a big difference with WDS and mine has been pretty stable since going to WPA PSK + AES. But if you followed the example in the official Tomato FAQ, you probably used that encryption already.
  3. jlobee

    jlobee Addicted to LI Member

    Do you have the Wireless set in mixed mode? Or does that many any difference?

    Also, can you post the reboot script you're using?
  4. TexasFlood

    TexasFlood Network Guru Member

    I am currently using mixed mode. I have used G only in the past. While quicker when it's working correctly, I've have better luck with mixed mode in terms of overall stability.

    As far as scripts, you can do it all under the adminstration -> scheduler page if you prefer the GUI or with your own script under the administratin -> scripts init tab. I have mine under the init scirpt tab. Let me add that I don't always schedule the reboots. Having said that, when the reboots are scheduled, both routers have the following:

    cru a RebootRouter "1 0 * * * /sbin/reboot >/dev/null 2>&1"
    And the primary router also has the following which reboots my Motorola Surfboard cable modem. YMMV with other hardware.

    cru a RebootCableModem "0 0 * * * /usr/bin/wget >/dev/null 2>&1"
    So the primary router reboots my cable modem at midnight every day and the two routers both reboot a minute later. I've played around with different schedules etc but that's what I have right now

    I also did a "keepalive" script for the init tab to reboot a router if it can't see the router on the other side of the wds link but I find Tomato stable enough so I'm not using it now. But FYI, below is that script if you're interested. You have to set the $remotewdsip variable to the IP of the router on the other side of the wds link form the router the script is run on. As written this writes a script to /temp/keepalive.sh and schedules cron to run it every 5 minutes. keepalive.sh pings the other router and reboots if 3 pings in a row all fail without even 1 successful ping. You can adjust the number of pings and frequency of running the script to suit your preferences.

    cat <<END > /tmp/keepalive.sh
    # Set the following to the static IP address of the server on the -other- side of the WDS link
    while ( ( /bin/ping -c 1 $remotewdsip | /bin/grep -q '100% packet loss' ) && \
     [ \$ping_attempt -lt '3' ] )
     ping_attempt=\`expr \$ping_attempt + 1\`
     /bin/sleep 1
     if [ \$ping_attempt = 3 ] ; then
    chmod 755 /tmp/keepalive.sh
    cru a KeepAliveScript "*/5 * * * * /tmp/keepalive.sh >/dev/null 2>&1"
  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