NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
static route pointing to R6250 from a R7000
Hello
I have my main router which is a R7000 on 192.168.1/24 network and I have a R6250 on 10.1.1.0/24 network, I am trying to set up static routes to get to the 10.1.1.0/24 mainly a webserver on 10.1.1.4, if I just use port forwarding then this is fine but I want to try static routes.
In the R7000 I have 10.1.1.0 mask 255.255.255.0 then gateway as 192.168.1.10 which is WAN IP for the R6250. This for some reason doesn’t work, if I do a tracert to 10.1.1.4 then all I get is a response for 192.168.1.1 and the rest are just *'s
I have tried to add a static route in the R6250 back to the 192.168.1.0/24 network but this didn’t help, my IT knowledge is very limited so I'm hoping I am just missing something or this cannot be done with this routers.
Thank you in advance
3 Replies
How is everything connected, especially the WAN/Internet ports of the two routers?
Be aware these are always NAT routers, no full subnet routing for the obvious reasons...so port forwarding might be required instead of routing.
Hi
The WAN port of the R6250 is connected to one of the LAN ports of the R7000 via a basic switch, there is a NAT Filtering on the WAN setup page but I have tried different things on and off on this page and still not helped.
> I have my main router which is a R7000 on 192.168.1/24 network and I
> have a R6250 on 10.1.1.0/24 network, [...]Why? Are you trying to complicate your life, or get educated, or
what?> [...] I am trying to set up static routes to get to the 10.1.1.0/24
> mainly a webserver on 10.1.1.4, if I just use port forwarding then this
> is fine but I want to try static routes.What kind of port forwarding, where, "is fine", as determined how?
> In the R7000 I have 10.1.1.0 mask 255.255.255.0 then gateway as
> 192.168.1.10 which is WAN IP for the R6250. [...]That sounds reasonable to me. Whether having NAT enabled on both
routers would cause problems is beyond my experience/expertise.> I have tried to add a static route in the R6250 back to the
> 192.168.1.0/24 network but this didn't help, [...]
The default route on the R6250 should do that job with no extra
effort on your part. The main/outer router (which needs to know about
the (invisible) subnet of the inner-router LAN) is the one who needs the
help.Around here, I do a few things with static routes, but not with
multiple layers of NAT. For example:D7000 (main router)
LAN: 10.0.0.1/24
static route: Dest = 10.0.4.0/24, Gw = 10.0.0.87 (Mac Pro, "proa")Mac Pro ("proa", routing between interfaces enabled)
en0 ("Ethernet 1"): 10.0.0.87
tap0: 10.0.4.87/24
Emulated VAX (simh, "wisp"): 10.0.4.32/24From another Mac ("minc") on the D7000 LAN (10.0.0.88):
minc% traceroute wisp traceroute to wisp.antinode.info (10.0.4.32), 64 hops max, 52 byte packets 1 gw (10.0.0.1) 1.696 ms 1.006 ms 0.936 ms 2 proa (10.0.0.87) 0.796 ms 1.104 ms 1.047 ms 3 10.0.4.32 (10.0.4.32) 11.578 ms 5.318 ms 10.153 ms
That is, the Mac at 10.0.0.88 ("minc") talks to its default gateway,
the D7000 at 10.0.0.1 ("gw"), which (relying on that static route)
passes the message to the Mac Pro at 10.0.0.87 ("proa"), which talks to
the (local) emulated VAX at 10.0.4.32 ("wisp", but the reverse DNS is
not configured for that subnet).But, the second router in this case is the Mac Pro straddling
10.0.0.87 ("proa") and 10.0.4.87, which is simply routing betwen
10.0.0.0/24 and 10.0.4.0/24, not trying to do NAT.
So, at least on a D7000 (and, I suspect, on an R7000 with your
firmware version), the static route stuff works, but I knew what I
wanted to do with it, and my secondary router was not doing any NAT. I
don't know what you're trying to do, and I don't know how much trouble
will be caused by having NAT enabled on your secondary router. (I also
can't see any other odd-ball stuff which you might have done someplace
which might affect this stuff.)
