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

Issue with WAN port as LAN on ASUS RT-N16

Discussion in 'Tomato Firmware' started by Rehan, May 10, 2012.

  1. Rehan

    Rehan Serious Server Member

    Hi guys,

    I have a slightly complicated setup so please bear with me and if I leave anything unclear, please ask me to clarify anything that I have missed.

    I have five ASUS RT-N16 routers running Tomato Firmware v1.28.9054 MIPSR2-beta K26 USB vpn3.6.

    One of these RT-N16s serves as the gateway and is connected to my cable modem. The IP address for this device is The remaining 4 RT-N16s serve as access points throughout my home and they have static IP addresses - All four RT-N16s that are serving as APs are wired from their WAN ports to a dumb/unmanaged gigabit switch in my central closet and then the switch connects to one of the LAN ports on the gateway. The reason they are connected from their WAN ports is because I turned on the option of "Use WAN port for LAN" in Basic -> Network -> WAN/Internet in Tomato firmware.

    The gateway ( provides DHCP services to all clients in the network. I do have one other device however, a remote power switch (RPS), which is connected directly to one of the gateway's LAN ports. The RPS does not have DHCP functionality so it has a static IP address of The RPS has no Wi-Fi capability.

    Now the issue is this:

    I cannot reach the web interface of my RPS from any of my devices in my home UNLESS I do the following:

    1) Change the connection on my AP points so that the cable coming from the gateway goes to a regular LAN port rather than the "WAN acting as a LAN" port.


    2) Disable the ethernet card on my desktop computer and access the AP in the area via Wi-Fi. Once I am connecting to my local AP with my wi-fi rather than via an ethernet cable, I can once again access the RPS.

    This leaves me confused as to why this is happening. I have power cycled everything in my setup but it hasn't changed anything.

    On both interfaces (ethernet cable OR Wi-Fi) I am able to ping and traceroute to the RPS successfully. However for some reason on an ethernet connection, the web interface simply won't load.

    Am I doing something wrong? Is there any alternative besides not using the WAN port as a LAN port? Is the bridging between WAN and LAN ports not 100% transparent?

    Let me know if I can provide any additional information. Thank you!
  2. Rehan

    Rehan Serious Server Member

    Moderators, please close this thread. After some hair pulling I realized the issue wasn't the router but outdated Realtek Ethernet GbE PCI-E card drivers for Win7. Win7 was saying I had the latest driver installed already but that was from 2009. Google'd a bit and found a new driver from March 2012. Problem solved!

Share This Page