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

Should this work? WDS - RT-N16 & WRT54G

Discussion in 'Tomato Firmware' started by sixsicsix, Nov 11, 2010.

  1. sixsicsix

    sixsicsix Network Guru Member

    Hey gang, so i put the latest builds each of tomato on my RT-N16 and WRT54G. I've followed the tutorials but i cant seem to make them talk together. Should i be able to link these two together? how can i troubleshoot what i have wrong if it should work?
     
  2. damwill

    damwill Network Guru Member

    I'm using the same two routers running WDS. What are you trying to do?
     
  3. sixsicsix

    sixsicsix Network Guru Member

    oK, i'm just trying to hook up some wired only devices to the WRT, and have it talk wirelessly to my main router (RT-N16).

    On The RT-N16 i have:
    WAN:
    setup for my ISP PPPoE

    LAN:
    Router IP: 192.168.0.1
    Mask: 255.255.255.0
    DNS: nothing
    DHCP: enabled, range 192.168.0.10-192.168.0.50
    Lease: 1440
    WINS: none

    Wireless:
    Enabled
    Wireless Mode: Access Point + WDS
    Wireless Network Mode: Auto
    SSID: wireless networkname
    Broadcast Enabled
    Channel: set
    Security: WPA Personal, TKIP/AES

    WDS: Link with: MAC from WRT54G


    on the WRT54G
    WAN: Disabled
    LAN: Router IP: 192.168.0.100
    Mask: 255.255.255.0
    DNS: nothing (tried putting my ISP dns in though)
    DHCP: tried enabled and disabled. currently set for 192.168.0.50-192.168.0.60
    Lease: 1440
    WINS: None

    Wireless:
    Enabled
    Wireless Mode: Access Point + WDS
    Wireless Network Mode: Auto
    SSID: wireless networkname from my RT-N16
    Broadcast Enabled
    Channel: set to same as RT-N16
    Security: WPA Personal, TKIP/AES
    Shared Key: same as RT-N16

    WDS: Link with: MAC from RT-N16
     
  4. damwill

    damwill Network Guru Member

  5. sixsicsix

    sixsicsix Network Guru Member

    after looking at this, i dont think it's the wireless WDS communication at fault, seems like it's not accepting my IP config and assigning. Each router shows up in the oposites device list when i check under status. i attached some pics of my config... i feel like i'm missing the obvious.
     

    Attached Files:

  6. TexasFlood

    TexasFlood Network Guru Member

    I agree the primary router should be receiving the ISP DNS. Are you setting DNS manually on your devices? If not then I don't see how you will get to the Internet without DNS resolution. I'm assuming you are getting or setting a WAN address.

    Are you sure that you are using the wireless MACs for the WDS links? Just double checking to be sure as there are different MACs for LAN, WAN and wireless.
     
  7. sixsicsix

    sixsicsix Network Guru Member

    I'm gonna check the DNS settings, i actually route through a different router for internet (whole diff ip range). I did try just normal stuff like getting assigned an IP which does not work.

    Initially when i was troubleshooting i added all 3 mac addresses of each router to each others allow list... just to make sure.

    I have another WRT i could try... i think i'll do that.
     
  8. TexasFlood

    TexasFlood Network Guru Member

    Oh and are the SSIDs the same as in the Tomato FAQ example? I think they have to be the same.
     
  9. sixsicsix

    sixsicsix Network Guru Member

    yep, 100% the same, i checked that soo many times today hah.
     
  10. damwill

    damwill Network Guru Member

    On the RT-N16 I have my Channel Width set at 20 MHz.

    Edit: I believe the WRT54G only supports 20 MHz.
     
  11. TexasFlood

    TexasFlood Network Guru Member

    I had problems with WDS as well after upgrading some of my routers.

    Since I as only supporting wireless clients on my WAN router, only using the "secondary" routers to add wired ports where I didn't have them, I turned off WDS and switch the "remote" routers to "Wireless Ethernet Bridge" which has been stable for me.

    At the time I assumed it was as a result of different wireless drivers due to the great difference in the vintage of the routers. When my routers were all old of about the same age WDS was rock solid.

    I might try it again soon to see if anything has changed with the upgrades in firmware I've been through since.

    At the time the only way I could assure keeping WDS working was scripts where the routers pinged each other and all rebooted if not, with the WAN router rebooting last and WDS would come back. In my case if the WAN router wasn't last some of the remote routers, and I had several, would not reconnect.
     
  12. sixsicsix

    sixsicsix Network Guru Member

    "Since I as only supporting wireless clients on my WAN router, only using the "secondary" routers to add wired ports where I didn't have them, I turned off WDS and switch the "remote" routers to "Wireless Ethernet Bridge" which has been stable for me."

    yeah, i'm gonna try that. that's pretty much exactly what i want to do.
     
  13. TexasFlood

    TexasFlood Network Guru Member

    Good luck. Back in the day after I went to Tomato WDS with WPA Personal (PSK) + AES, when all my routers were corerev 7, it was rock solid for YEARS. Since I started mixing it up with newer hardware and Tomato builds, WDS has been problematic for me. Not that it didn't work, it just wasn't rock solid for me any more. Teddy Bear tried to help me out resolving my WDS issues but never got it completely resolved. It was also Teddy Bear who, after I explained what I was trying to do, suggested using "Wireless Ethernet Bridge" which has been as solid as WDS had been before.
     

Share This Page