ADSL + Tomato Router + Managed Switch: Config & Access across LAN/WAN Boundary: How?

[crashnburn]

ADSL + Tomato Router + Managed Switch: Config & Access across LAN/WAN Boundary: How?

HP ProCurve 1800-24G [GigE]
- 24 Port Managed GigE Switch:
- (I bought after some great recommendations here)

- Also have a GigE NAS and few GigE clients attached to Switch.

ASUS RT-N16 Wireless N Router w 4 port GigE: [AsusWiFi]
- Firmware: Tomato USB - VPN Build - Possibly go upto Toastman/ Shibby build later on.
- New.. just bought & installed Tomato..
- Currently testing as a client on LAN - It creates its own NAT/LAN2 as a DHCP Server)
- Future/ Target: Primary Router/ Firewall / Network Bandwidth / QoS Manager?

ISPs - ADSL Modem + Wireless N Router + Not GigE : [ADSLWiFi]
- Shanghai DareGlobal Technologies Co. Ltd (As per inSSIDer recognition)
- Model 450TC1 (as per web Admin console & also branded for ISP)



Original Config (Current):

ADSLWiFi (WAN: ISP Assigned IP | LAN: 192.168.1.1 | DHCP Server + Few Static Assignments)
>
GigE (192.168.1.10)
.................................... LAN1 = 192.168.1.x
>
AsusWiFi (WAN: DHCP Client IP/ Static IP | LAN: 192.168.100.1 | DHCP Server)
.....................................LAN 2 = 192.168.100.x


In this configuration, at times I connect to LAN1 DHCP or LAN 2 DHCP.

The issue I am facing and trying to figure out is:

- When I am on LAN 1, I cant access AsusWiFi Web Admin Panel: Even with Remote Access & HTTPS enabled etc?

Under LAN1 scenario, AsusWiFi is just a client on LAN1, so.. ?

- When I am on LAN 2, I cant access ADSLWiFi Web Admin Panel

Under LAN2 scenario, LAN 1 is an outside WAN in some ways..

If I remember my Networking classes correctly in NAT & Subnet masks etc I am missing something here. How would I, could I access them across the LAN/WAN?

PLEASE REFRESH ME ON THE ABOVE SCENARIO.. I am forgetting some networking fundamental here? Some kind of LAN IP > WAN IP Tables Addressing / Forwarding?

Even though, I am not going to keep this config long term, I am wondering how to access the ADMIN panels for both because of what I might do in the NEAR future configs

Future Config Ideas:

PREFERRED GATEWAY Config:

ADSLWiFi
>
...................Stop Gap LAN [ADSLWiFi LAN & ASUS WiFi WAN Only)
ASUSWiFi (WAN: & LAN: | DHCP Server)
(ISP Gateway & Network Management?)
>
GigE
.................. Main LAN ... GiG E ONLY

-Isolate ADSLWifi , the ISPs stuff totally from the internal network and let ASUS WiFi be the Gateway.
-I will end up disabling the Wireless on ADSLWiFi as ASUS Wifi would be the primary WiFi provider without interference from ADSL WiFi.
- Also, Since ADSLWiFi is not GigE & it is isolated out, it does not slow down the GigE protocol within the Main LAN
- Also, takes the LOAD of LOCAL DATA & transfers away from ADSLWiFi (as I'd rather not let it bear DATA LOAD if local transfers are happening. I think ASUSWiFi & HPGigE are more RELIABLE thorough load handlers). This also ensures I experience less hiccups & fewer restarts for ADSLWiFi & few internet disconnects with the ISP

In this scenario, I am wondering how I could access ADSL WiFi Web Admin Page via the main LAN ? Am I not addressing it correctly in the browser?

Is there some kind of mapping I can make inside TOMATO Firmware to be able to access that configuration?

SINGLE LAN CLIENTS Modified Original Config:

ADSLWiFi (WAN: ISP Assigned IP | LAN: 192.168.1.1 [100/10] | DHCP Server + Few Static Assignments for HPGigE S/W, NAS, AsusWiFi etc. )
>
GigE (192.168.1.10)
>
AsusWiFi (WAN: Static IP | LAN: 192.168.1.2 | No DHCP - Takes Assignment from ADSL WiFi)

..................................... Main LAN .. GigE + 100/10 = 192.168.100.x

In this scenario, its simple as I can access all Wed Admin panels through simple IP on the only Main LAN that exists.

But a few disadvantages occur (correct me if I am wrong):
- Due to the 10/100 client - Local transfers could get slowed down to 100 from GigE (Unless the new managed switches can do some magic here? )
- Network, IP, Bandwidth/QoS management for Local Network may not be managed by ASUSWiFi (Tomato... great management tools, logging & dashboard)
- DHCP and other local data loads end up affecting the ISP's ADSLWiFi.