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

Shibby 112 - Guest SSID stops working when connecting WAP

Discussion in 'Tomato Firmware' started by GhaladReam, Aug 31, 2013.

  1. GhaladReam

    GhaladReam Network Guru Member

    I have a 2-router setup currently, with the 2nd router acting as a remote WAP:

    Main router - RT-N66U - Tomato Shibby 112 AIO-64K
    2nd Router - E1200v2 - DD-WRT v24-PreSP2 Build 21061

    Main router is broadcasting my main SSID on LAN0, as well as ethernet ports 1-3 are on LAN0
    Main router is also broadcasting a guest SSID on LAN1 and ethernet port 4 is also on LAN1

    2nd router's WAN port has been bridged to the LAN and is attached to Main router's port 4, effectively putting the 2nd router (WAP) on my guest network. 2nd router is set up and running and working perfectly as a WAP, several hundred feet away from the main router.

    My problem is this: The main router's guest SSID stops working when the 2nd router (WAP) is plugged into port 4. It continues to broadcast the guest SSID, but nothing can connect to it. The moment I unplug the 2nd router from port 4 of the main router, I can connect and use my guest SSID.

    I'm at a loss as to what could be causing this issue. If I plug a regular wired client, such as my laptop, to port 4 of the main router, it correctly gets assigned an IP from LAN1 and functions, and my guest SSID also functions. It's ONLY when the secondary router (WAP) is plugged in that the guest SSID stops working.

    I'm thinking there is some kind of service running on the secondary router DD-WRT (WAP) that is causing this, or something I haven't enabled that needs to be, but I can't figure out what it is.

    I would just put Tomato on the 2nd router, but there is a specific script I'm running on the WAP that requires DD-WRT.
  2. Malitiacurt

    Malitiacurt Networkin' Nut Member

    Sounds like incorrect settings on the WAP are overriding br1 settings on your main router.

    What is WAP's IP and gateway settings, and did you enable dhcp. And what's the br1's IP.

    And did you change the MAC for wl0.1 or WAP's WAN/LAN to something than what tomato defaulted to?
  3. GhaladReam

    GhaladReam Network Guru Member

    Thanks for the quick response. Essentially, I followed this guide to a T, using the "Long Version":


    WAP's IP is, main router's br1 IP is
    DHCP is disabled on the WAP. WAN is disabled.
    Gateway and Local DNS set to on WAP.

    I did not change the MACs on wl0.1 or the WAP at all. I know what you're getting at though: Even with port 4 connected to the WAP, wl0.1's BSSID is not mismatched with its hwaddr. (i.e no wl driver errors reporting different MACs on the virtual interfaces page of Tomato). This goes for wl0.1 and wl1.1 (same ssid, one 2.4 ghz the other 5ghz) both of which are bridged to br1.
    Last edited: Aug 31, 2013
  4. GhaladReam

    GhaladReam Network Guru Member

    Ok, so I found a solution to the problem, but it's more of a workaround.

    It appears that there's an issue when using the "Assign WAN Port to Switch" option on the DD-WRT WAP, and then using the WAN port. If I leave that option disabled, and use a LAN port instead, everything works 100%, even my guest SSID on the main router.

    I noticed that if I do use the WAN port, DD-WRT assigns it as 'vlan2'. Wheras the 4 LAN ports get 'vlan0'.

    If I leave "Assign WAN Port to Switch" disabled and use a LAN port, DD-WRT still assigns the wan port 'vlan2' but it does not appear in the list of interfaces bridged to br0. Instead, the LAN ports designated vlan1 instead of vlan0, and everything works.

    I think this may just be a bug in DD-WRT doing something odd to cause this problem when using the WAN port as a LAN port, I'm just not able to explain why it doesn't work when using the WAN port like this. Anyone have any ideas why?

Share This Page