Commandline commands for WDS

Discussion in 'Tomato Firmware' started by tunasashimi, May 25, 2007.

  1. tunasashimi

    tunasashimi LI Guru Member

    Hi All

    I was wondering if anyone could post whatever they can find on setting up and bringing down a WDS connection via the commandline.

    I have a WDS link between two tomato's that just dies for no reason, and only comes back up when I reboot the one router. I'm hoping to find a quicker way to reset the WDS link. Only one WDS link dies, clients and other WDS links stay up on both routers.

    Will simply removing the mac from WDS, and re-adding it possibly have the same effect as rebooting?

    Anybody know these commands?

    Thanks :confused:
  2. ntest7

    ntest7 Network Guru Member

    Don't know if this will help, but maybe turning the radio off and back on will reset your connection.

    wl out # turn radio off
    sleep 10 # wait a little bit
    wl up # turn radio on
  3. digitalgeek

    digitalgeek Network Guru Member

    what encryption are you using for you WDS link?
  4. GeeTek

    GeeTek Guest

    That might be a bit tricky across a wireless link. Can linux run batch files ?
  5. tunasashimi

    tunasashimi LI Guru Member

    Using 64-bit WEP. How do you think it could affect it?

    I'm pretty sure the dropping of just this one specific WDS link is cause by poor signal strength. And a bug probably.

    Here is the scenario:

    I have a rather large WDS "backbone" consisting of 4 main WDS-linked nodes, each with about 4 WDS clients (leaf-nodes).

    The funny thing is that none of the other WDS links are affected. Only this one specific one. Meaning, on each of the two WDS linked routers, they still maintain connectivity to their other WDS peers.

    Rebooting the one WDS router fixes the problem. Rebooting the other has no effect. Dropping the other's MAC from either WDS list has no effect:

    wds 22:22:22:22:22:22 33:33:33:33:33:33

    ... wait a minute or two

    wds 11:11:11:11:11:11 22:22:22:22:22:22 33:33:33:33:33:33

    ..wait a minute or two...

    11:11... nowhere in sight.



    Cool. Tried it, but didnt work. Im sure I saw a "reset chipset" command somewhere... will play with that and report back.

    Lol, most of linux IS batch files! ;D They're called "shell scripts" or "bash scripts". As a matter of fact, you can run script files in any language very simply. If you would like to execute a perl script, for example, you add"#!/wherever/bin/perl" as the first line of the script, and your shell will call that binary and feed it the script. Just make sure you dont use DOS "CR LF" line endings or you'll get really untracable and nonsensical errors... :flabbergasted:
  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