OK, progress to understanding!
The only manually setup port forwarding you should need is for Samba or NetBios file
sharing which are typically WAN ingress blocked by the router. Normally on
Modem->Router setup this is what you want as every thing on the WAN side is Internet
but in this case you want to forward (I assume) those kinds of traffic between
SubnetB & SubnetA.
All other functions: DNS, DHCP, & Gateway should already work fine since SubnetB
clients make requests of the subnet's router. There should be no custom tweaking to
get this much too work since at a micro level all clients rely on the local router
without a care that the next hop is more Intranet rather than Internet. At the macro
level NAT from SubnetB takes care of getting onto SubnetA and ultimately a second NAT
across RouterA get's RouterB's clients to the internet. Hence the term "Double NAT'd"
from earlier.
I don't know how old or what model/rev linky's you got but I assume the oldest WRT54
series is going to do DD-Wrt giving you more control. You may have to resort to using
telnet to setup iptables firewall rules if port forward GUI won't do what you want.
For that matter they are just linux boxes and you can configure a lot like what's
bridged at the router.
On 4/26/2010 10:26 AM, Winterlight wrote:
At 02:44 AM 4/26/2010, you wrote:
Well then all resources are localized per subnet, thus should not be
an issue. This assuming you have linked downstream routers via their
WAN ports to LAN ports on the upstream router
I am using the WAN ports to LAN ports,
and are relaxing downstream routers' firewall rules to allow traffic
in/out their WAN ports to the "main" SubnetA which in turn serves as
gateway to the Internet.
but I have no setting for adjusting the Firewalls in these older
routers, other then on with DHCP or off, and of course port forwarding
which is probably my next thing to try.
thanks
w
