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

Asus rt-n12b1 AP+WDS linking problem

Discussion in 'Tomato Firmware' started by Steven Chou, Mar 31, 2012.

  1. Steven Chou

    Steven Chou Serious Server Member

    I recently bought 2 asus rt-n12b1 routers, which want to replace the old rt-n11(no custom firmware can load) and a wl-500gx(lower speed, now with k26 USB 1.28.9054 lite beta), used to link by AP+WDS way of 2 buldings of 10M length, no problem just slower.but...
    I have tried all Toastman builds for rt-n12b1, RAF's 079, Shibby's, Oleg's and dd-wrt's builds but all fail to have a stable wireless link at both rt-n12b1 routers, seems not more than 30 minutes, the clint router of rt-n12b1 will become only have tx but no rx flow, set to 20 MHz will last longer than 40 MHz, Shibby's build after setup to be an AP+WDS will brick after reboot, need to be restore firmware, but if I use 1 of rt-n12b1 as a server AP+WDS to link with n-11(hybrid mode) or wl-500gx as clint AP+WDS and they both work fine, except the n12b1 linking each other, any advice?
     
  2. bestcow

    bestcow Serious Server Member

    Hi Steven,I got the same router with yours and flahsed the latest version of Shibby's.
    After setup WDS as secondary router linked with my primary router ASUS RT-N16(with latest Tomato DualWan),it became unusable after a while(unable to get IP address on mobile devices or login into RT-N12). So I am wondering is this WDS problem just related to some mods(not try any other mods yet) and considering to change to AP mode with wire to my primary router but that is inconvenience for me.:confused:
    Appreciate if any advice here.:)
     
  3. mvsgeek

    mvsgeek Addicted to LI Member

    The following environment has been extremely stable for me :

    Main router : Asus RT-N16, Tomato Firmware v1.28.0501.3 MIPSR2Toastman-RT-N K26 USB Ext
    Secondary router : Asus RT-N12B1, Tomato Firmware v1.28.0501.3 MIPSR2Toastman-RT-N K26 Std

    By "extremely stable" I mean no unscheduled reboots or dropped connections in almost 2 months.
    Main is set to AP+WDS, N only, 40MHz, Channel 1, WPA+AES.
    Secondary is Auto, 40MHz, Channel 1, WPA+AES.
    I've tested with secondary set to both AP+WDS and Wireless Ethernet Bridge mode, with equal success.

    After some head-scratching, I figured out that if secondary is set to WEB mode, then its MAC address MUST NOT appear in main's WDS link list - if it does, secondary simply won't connect.
     
  4. bestcow

    bestcow Serious Server Member

    Hi MvsGeek.
    Thanks for your useful information.I used the WPA as the WiFi encryption as tested WPA2 didn't work.
    Is your Tomato version the latest Toastman mod?
     
  5. Steven Chou

    Steven Chou Serious Server Member

    Hi Bestcow, finally I got one way for me which is very stable and can run full speed of routers, but you will not able to have any wi fi encryption, I use mac address locking for each router: AP+WDS, and use wi fi filter for accepting the client's mac address to allow to join my own network. This is so far I can try and sucess for a stable linking and no loosing speed. Recently if I have more time, I will try the latest Toastman and dulawan firmwares for testing, hope this can help you.
     
  6. bestcow

    bestcow Serious Server Member

    Hi Steven,thanks for your advice.Actually I have now enabled the MAC address filtering what you mentioned before or after I setup WDS.
    Anyway,I will try the Toastman mod to test if this issue can fix.
    Thanks again for your advice.:)
     
  7. mvsgeek

    mvsgeek Addicted to LI Member

    Yes, the versions I mentioned are Toastman's latest as of this posting. The RT-N16 will accept either the RT or RT-N version, but the RT-N12 requires the RT-N version.
     
  8. bestcow

    bestcow Serious Server Member

    Thanks for your info mvsgeek...I will flash to Toastman version to try...:)
     
  9. bestcow

    bestcow Serious Server Member

    Seems the RT-N12 version of Toastman is older than the version of RT-N16,right?
    BTW,is there any net limiter feature integrated with RT-N16 version of Toastman?


    Sent from my iPod touch using Tapatalk 2
     
  10. Monk E. Boy

    Monk E. Boy Network Guru Member

    The version numbers for RT and RT-N are very different to keep people from talking about RT when they mean RT-N and vice versa. They're normally both equally new, when Toastman updates one branch he updates the others in a matter of hours.

    Oh, he did recently update the drivers for the RT-N branch, he might not have rev'd the RT branch at the same time...

    Edit: Nope. 1.28.0501.3 is the latest RT-N build and 1.28.7501.3 is the latest RT build. They're in sync.
     
  11. bestcow

    bestcow Serious Server Member

    Thanks for the information,now I have the version you mentioned for RT-N12,but is there net limiter integrated for RT-N or RT build?
    BTW, just wondering as what I saw in Toastman's document,he said people were very difficult to compile the new wireless driver for new router models as no source codes were opened for that,so new router support is hard to move on.Does the situation now better than before?


    Sent from my iPod touch using Tapatalk 2
     
  12. Monk E. Boy

    Monk E. Boy Network Guru Member

    Sorry, I just jumped in here since I have experience with RT-N12s.

    Is it an RT-N12 or an RT-N12B1?

    The RT-N12 has 4MB of flash and the RT-N12B1 has 8MB of flash. The larger the flash the more features a firmware can have.

    All wireless drivers, whether RT-N, RT, or even ND, are statically linked. That means they're compiled by Broadcom and no documentation is available on them whatsoever. When Tomato moves to a new driver version there's a bit of a pucker moment since there's no way to determine if wireless is going to work properly until you actually flash the firmware onto the router(s) and verify whether they work or not. Toastman recently moved to newer Broadcom drivers in RT-N, but other Tomato builds (notably Shibby's builds) have been running them for a while so I believe the hope is that it won't be a a headache.

    Net limiter? Do you mean bandwidth limiter?
     
  13. bestcow

    bestcow Serious Server Member

    My version is RT-N12 B1 and yes I mean bandwidth limiter


    Sent from my iPod touch using Tapatalk 2
     
  14. bestcow

    bestcow Serious Server Member

    Hi mvsgeek,I flashed Toastman build with tomato-K26USB-1.28.0501.3MIPSR2Toastman-RT-N-VPN-NOCAT but found that there's no channel 1(only channels 5-13) in WiFi setting by default country Singapore,which country did you select?
     
  15. kthaddock

    kthaddock Network Guru Member

    There is CH:1 use Control Sideband "LOWER" then you get CH: 1 - 9 :)
     
  16. bestcow

    bestcow Serious Server Member

    Oh yes,I saw it after followed your instrunction!
    Thanks! But BTW,what's the meaning of control sideband?
     
  17. kthaddock

    kthaddock Network Guru Member

  18. bestcow

    bestcow Serious Server Member

  19. bestcow

    bestcow Serious Server Member

    After flashed Toastman build both on N16 and N12,it was still unable to use it,cannot obtain the IP address from main router via this WDS and as well as unable to login the secondary router via wireless(login via wired is ok).
    Any idea?


    Sent from my iPod touch using Tapatalk 2
     
  20. mvsgeek

    mvsgeek Addicted to LI Member

    Probably dumb questions, but I'll ask them anyway...
    1. If you've set network type = 'N', is your wireless card N-capable?
    2. Did you assign your client static IP addresses for both wired and wireless adapters?
    3. Are you using WPA2 encryption?

    I've found that the combination of WDS and WPA2 is very unpredictable, which is why I use WPA.
    If you still can't get WDS to connect, try setting the N12 to Wireless Ethernet Bridge, and make sure you remove its MAC address from N16's link list. Of course then you won't be able to access the N12 wirelessly unless you create a separate VLAN.
     
  21. bestcow

    bestcow Serious Server Member

     
  22. mvsgeek

    mvsgeek Addicted to LI Member

    In order to set up a VLAN, you'd have to flash the RT-N12 with the Toastman VLAN version. Before you do that, I suggest you try the Wireless Ethernet Bridge option, and see if a wired client can access the RT-N16 from the RT-N12. If that works, then WDS is the problem.
     
  23. Monk E. Boy

    Monk E. Boy Network Guru Member

    Um. Stupid question here, but can you even do WDS with 40Mhz channels? 40Mhz channels only allows you to have a single 2.4Ghz access point, since there are only 3 non-overlapping channels (1, 6, 11) and you're using two of them in 40Mhz mode.
     
  24. bestcow

    bestcow Serious Server Member

    Sorry that I don't totally understand your meaning,but I have tried 40Mhz channels both in two routers but still failed and now set to 20Mhz is the same result. I got success before for a while but now is totally failed to do that.
    There're 2 cordless phones using 2.4Ghz channels in my home, so I do not have idea whether it caused the interference there.
    Anyway,thanks for your advice here.


    Sent from my iPod touch using Tapatalk 2
     
  25. bestcow

    bestcow Serious Server Member

    Ok I will try this to see it first,thanks for your advice again.


    Sent from my iPod touch using Tapatalk 2
     
  26. mvsgeek

    mvsgeek Addicted to LI Member

    In my blissful ignorance I never even considered that :D I can only report that I'm using WDS, channel 1, 40Mhz - with apparent success. InSSIDer shows the SSID on Channel 1 + 5 with a max rate of 300. The device list page on the RT-N12 shows connected wireless clients with a TX/RX rate ranging from 162/108 to 300/300.
     
  27. bestcow

    bestcow Serious Server Member

    Is that mean your two routers actually now working in channel 1 & 5 respectively for WDS?


    Sent from my iPod touch using Tapatalk 2
     
  28. mvsgeek

    mvsgeek Addicted to LI Member

    It just means that specifying channel 1, lower control sideband, 40MHz, type N on both routers causes InSSIDer to display the SSID as using Channel 1 + 5. When I figure out how to post screenshots maybe I'll do so.
     

Share This Page