NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
Routing problem
I'm having a problem routing from my home LAB network to the internet. I can RDP from my home network to my home LAB network without any issues. I can ping and tracert from my LAB router to the internet, but I can't ping or tracert to the internet from any devices on my LAB network. tracert from clients die after 192.168.1.1
Problem solved. Had to turn on NAT on the 2nd router.
thanks for the snarkey comments.
3 Replies
> I'm having a problem routing from my home LAB network to the internet.
> [...]
What does "LAB" mean? "Lab(oratory)"? "Local-Area Blunder"? I
think that I can guess which boxes in the (pretty) diagram are the
routers, but which subnet is "my home network", and which is "my home
LAB network"?
The router with LAN IP address 192.168.1.1 could use a static route
with:
Destination: 192.168.2.0
Subnet: 255.255.255.0
Gateway: 192.168.1.2
Metric: <lowest_allowed>
Without such a route, when the router at 192.168.1.1 sees a message
for 192.168.2.x, it would send it to the ISP, just as it would for any
other foreign (non-192.168.1.*) address. With that route, it should
send such a message to the other router (at 192.168.1.2), which should
pass it to the appropriate destination on its (192.168.2.*) LAN.
Whether you can get Microsoft Remote Desktop (or anything else) to
work through two layers of NAT is a different question.