Route to public range through VPN?

[CTS-Tech1]

Have an RV042 with an IPSEC tunnel to a site with a public IP range for their internal network (192.20.20.x).  Our network is a 192.168.1.x subnet.

The tunnel shows as connected but when we do a tracert from our network to the 192.20.20.x network - it looks like the traffic is going out the WAN interface, not through the VPN.

How can we resolve this?

[Tom Watts]

Hi CTS, that is your problem, the 192.20.20.x is a public range. The router couldn't know any better. The expected behavior in turn would be out of the WAN interface.

The way to fix this is by using private IP ranges.

-Tom
Please mark answered for helpful posts

[michal.witkowski]

Hi

Yes, router knows better what user wants.

It's like network 10.XX.XX.0 with VPN, the router knows better, you must readress all your local network....

Why is that ? Router should take every config we give it.

If someone wants to use public IP's then why not ?

In this case, the router sees public IP range and pushes it through the WAN even if it has this IP range on the VPN tunnel ?

That's ridiculous !