I'm trying to set up a static route but for some reason I can't get it to work.
My current network looks like this:
The static route I added:
Set it as private since it only needs to work on lan (tried Active and both of them also). The metric I think should 1 instead of 2 if I can believe all the things I read about static routes ... but it won't let me set it less then 2.
The server has domain controller, dns, dhcp (distributing ip's 10.*.*.*), routing (nat between the 2 interfaces so that clients can access the internet). The clients (10.*...) can ping machine on the 192.168.2.* network.
But when I connect to the wifi of the r7000, I can't ping a client.
Can someone tell me what I'm missing here?
ps: don't want to disable dhcp on the r7000 since I don't want the server directly on the internet, I have a isp modem (not a router).
Re: static routes
> The static route I added:
Looks plausible to me. But...
> Set it as private since it only needs to work on lan (tried Active and
> both of them also).
"Active" sounds as if it ought to be set, doesn't it? Help Center on
my D7000 says:
4. Select Active to make this route effective.
I'd vote for that as the big problem.
I don't know what "Select Private if you want to limit access to the
LAN only" means. I've never set it. (Something to do with RIP (which
is disabled here?))
> The metric I think should [be] 1 instead of 2 [...]
Same here, but 2 works.
> [...] routing (nat between the 2 interfaces so that clients can access
> the internet). [...]
That's a little scary. Routing is one thing; NAT is something else.
You want (unspecified) "Server" to route between 192.168.2.x and
10.*.*.*. I suppose that NAT by "Server" could make sense. (Unless I
had a zillion "Clients", I'd probably have picked 10.0.0.*
(255.255.255.0) for that internal subnet, but no matter.)
> But when I connect to the wifi of the r7000, I can't ping a client.
What do you get for IP address, gateway, and so on on a typical
wireless device? Have you tried anything other than "ping"? Telnet?