@ceejaybassist 

You don’t need any static route for it. The 10.0.0.x network is a remote network for the 192.168.10.x network. Therefore, the default route in the 192.168.10.x network already takes care of routing to it.

Can you access Internet? Is 10.0.0.1 accessible when you connect directly to the ISP modem? If yes, maybe you have a firewall rule on ER605 blocking the private space addresses on WAN.

Hi @ceejaybassist 

Thanks for posting in our business forum.

NAT does not block outbound traffic unless you set something.

So 10.0.0.1 is open to the 192.168.10.0/24. It's on the WAN side and it can automatically route it to 10.0.0.1 if you access it.

Routing is more like a thing inside your LAN. So this does not pose a question.

  @ceejaybassist 

I don't know if what's been said above is true in your case.  Because you are in 'bridge mode' you most likely have a public IP assigned to the WAN i/f of the router.  Because 10.0.0.1 is a private IP address, it is not routable on the internet by definition, which means your router should not forward it via the WAN i/f (that would break some pretty big rules).

However, you can force a static route which should do what you need.  This is the method I used ot use to access the Starlink router interface.  So go ahead and add the Static Route for 10.0.0.1 via your WAN port, it certainly won't hurt anything.

Dest Subnet: 10.0.0.1/32

Route Type:  Interface

Interface:  WAN

Next Hop: 10.0.0.1

Metric: 10

I don’t think the ER605’s NATting itself cares if the destination address is private or public. It will do the routing and the default gateway should be good enough for it. But yes, 10.0.0.1 as a private address and the ISP most likely blocks it when the modem in the bridge mode is connected to their network.

Accessing the modem’s statistics/diagnostic interface, usually at 192.168.100.1, follows the same routing rules and the default gateway should be good enough for it as long as 192.168.100.x is not on the local network. It certainly worked for me. The only time I had to create an extra static rule for it is when I already had another static route that routed the whole 192.168.0.0/16 subnet to my routing switch (LAN).