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

Setting up WDS with 2 Shibby VLAN-build routers

Discussion in 'Tomato Firmware' started by brainz, Feb 9, 2012.

  1. brainz

    brainz Networkin' Nut Member

    I just loaded tomato-K26-1.28.RT5x-MIPSR2-083V-Mini onto my WNR3500v2 and tomato-E2000-NVRAM60K-1.28.RT5x-MIPSR2-083V-IPv6-VPN onto my E2000.
    Most settings are still at their defaults. I don't want 2 seperate LANs.

    I set up WDS as per usual: wan&dhcp off on router 2 & mode "router" instead of "gateway" on router 2, STP enabled.

    They synched up nicely via WDS, but could not ping eachother.
    I managed to fix this by following http://www.linksysinfo.org/index.ph...dging-setup-help-requested.35669/#post-173905

    I wonder if/why this rule is not accessible through the web interface?

    Also I had to switch back the mode of router 2 to "gateway", otherwise I could not get a DHCP assign from router 1 when connecting wirelessly to router 2. On non-VLAN builds this is not an issue. Why?

    The only problem that remains is that I can't access router 1 when connecting a device to router 2's LAN port.
    Have I done something wrong in this setup or did I forget anything?
  2. jsmiddleton4

    jsmiddleton4 Network Guru Member

    First turn off any security until you get them connected and solid and stable. My WDS slave is set to router, not gateway. Do you have the master IP in the gateway and dns fields of the slave? Also with 2 routers I'm not certain you need STP enabled. Do not enable DHCP routes.

    I discovered an oddity which is if I cut n paste the MAC's of the slave and master into the proper WDS fields I can't connect between the 2 routers. I have to manually enter the mac information and let the firmware put in the ":".

    After you configure the 2 routers boot the slave, make sure it comes all the way up. Then boot the master and let it "find" the slave.

    Once both are up and connected then you can go back and add security. I use WPA Personal AES and WPA2 Personal AES and either work fine.
  3. jsmiddleton4

    jsmiddleton4 Network Guru Member

    By the way there's several threads with WDS information already on this forum.
  4. brainz

    brainz Networkin' Nut Member

    Well, it's working as expected instead of the problem noted at the end of my original post.
    It's been stable for 7 days straight now with Shibby 083V (VLAN) master and Toastman 1.28.7495.3 (STD) slave.

    As you said, there is an oddity where the slave must be running before the master for them to connect.
    And once either of the routers crashes, the other one needs to be rebooted as well for WDS to reconnect. I believe Toastman <=7487 does not have this problem, but I'm not sure.
  5. jsmiddleton4

    jsmiddleton4 Network Guru Member

    That is not odd. That is normal behavior for WDS with these routers. If you have to use VLAN then stay with the current firmware. If you just need to do WDS than an older version 7483.2 is the most reliable for WDS. The WDS stuff needs to negotiate the connection so the slave has to be up and running first. If anything drops, you have to reconnect.

    Wireless ethernet bridge is easier but due to design limitations you can't do MAC wireless filtering, etc.
  6. mvsgeek

    mvsgeek Addicted to LI Member

    I recently reverted from 7495 to 7483.2 for reliability reasons. So far, so good, but am now lacking inbound QoS and other features. I run a script on all slaves every 5 minutes to test connectivity, and reboot if main doesn't respond. Very occasionally a slave reboot won't reconnect, so a main reboot is required. When that happens, inevitably one or more slaves will fail to reconnect:-( No pattern that I can see, it's random, and signal strength isn't an issue. The number of reconnect failures is drastically less with 7483.2 than it was with 7495.

    I also found by trial & error that WPA2 on main would never connect, so everything is now WPA + AES.
  7. Toastman

    Toastman Super Moderator Staff Member Member

    Try 7483.3
  8. brainz

    brainz Networkin' Nut Member

    If only it had a build for my newly acquired F7D3302...
  9. jsmiddleton4

    jsmiddleton4 Network Guru Member

    .3 adds additional QOS stuff yes?
  10. Mercjoe

    Mercjoe Network Guru Member

    Not to confuse anyone, but I have NEVER had a problem with a router reconnecting in a WDS if either the master or the slaves goes down.

    I can boot them in any order or at the same time and the WDS is up and running within a minute of the routers being fully up. I am using two different kernels on two different routers. You would think that would make it really strange.

    I wonder what I am doing differently than everyone else.

    Seriously.. If we can figure that out, them maybe it will help everybody.
  11. Toastman

    Toastman Super Moderator Staff Member Member

    Yes, Jim. I thought I'd just add this so that anyone who liked that build has the better QOS. Hopefully it won't impact anything else.

    4 shared site is working correctly now, I believe. Works here, anyhow.
  12. jsmiddleton4

    jsmiddleton4 Network Guru Member


    As far as I know you are the exception, not the rule. Would be nice to know if you are doing anything differently then the rest of us and our setups in WDS.

    4 Share still not working right for me. Isn't showing any files.
  13. mvsgeek

    mvsgeek Addicted to LI Member

    I wonder if WDS reliability is inversely proportional to number of slaves...currently I have 7 slaves, and 4 "slave-slaves" (or tertiary) routers. I'm pretty sure I had fewer dropouts when there were 5 or less.
  14. jsmiddleton4

    jsmiddleton4 Network Guru Member

    Once my connections are established and passwords have been decoded, etc., I can boot a slave or the master and not lose connections. I'm not sure why. What we have been talking about is getting the WDS connection setup in the first place.

Share This Page