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

Can't open web UI for Tomato access point remotely

Discussion in 'Tomato Firmware' started by ilovejedd, Oct 15, 2010.

  1. ilovejedd

    ilovejedd Addicted to LI Member

    Help, just added an Asus RT-N16 to the network last night and I'm banging my head on the wall (well my desk actually) because of some issues. :wall:

    I've got two Tomato routers:
    1. Linksys WRT54GL Tomato Firmware v1.25.8025.2-RAF STD
    2. Asus RT-N16 Tomato Firmware v1.28.9048 MIPSR2-beta18 K26 USB Ext

    The Linksys is connected to the cable modem and acts as gateway. The Linksys' LAN IP is and wifi is disabled. The Asus is located in a more centrally-located area for better coverage and is connected to a gigabit switch. It's used purely as an access point. Below are the settings used for the Asus:

    Basic -> Network
    WAN / Internet
    Type                     Disabled
    Use WAN port for LAN     (checked)
    Router IP Address
    Subnet Mask    
    Default Gateway
    Static DNS     
    DHCP Server              (unchecked)
    Advanced -> Routing
    Mode                     Router
    RIPv1 & v2               Disabled
    DHCP Routes              (checked)
    Spanning-Tree Protocol   (unchecked)
    Administration -> Admin Access
    Web Admin
    Local Access             HTTP & HTTPS
    HTTP Port                80
    HTTPS Port               443
    Remote Access            HTTPS
    Port                     8080
    Allow Wireless Access    (checked)
    I can connect to the Asus just fine on the LAN. Internet is working fine and I can open the web UI when on the LAN. My issue is I can't open the web UI from the internet. I've tried two port forwards on the Linksys router:

    On  Proto  Ext Ports  Int Port  Int Address     Description
    On  Both   1234       443    APui-local
    On  Both   12345      8080    APui-remote
    However, neither https://<WAN-IP>:1234/ nor https://<WAN-IP>:12345/ seem to work. Help please?
  2. Toastman

    Toastman Super Moderator Staff Member Member

    I just had a quick read and not too sure what you're doing. Assuming you set port 8081 as your port to access the AP, then you need to forward to port 80 on the internal LAN, which is the Web GUI. The AP must have a route back to the router, so set the gateway to That should be all that is needed.

    Proto TCP Ext 8081 Int 80 APUI
  3. ilovejedd

    ilovejedd Addicted to LI Member

    Thanks for the suggestion. For some reason though, after around 30 minutes or so, it suddenly started working without me having to change anything. Weird...

    I can use https://<WAN-IP>:1234/ to connect now.

Share This Page