Force public ip down VPN

[jshailes]

We have a setup site1–site2--site3 all done with ip sec where:
site1: 10.44.35.0
site2: 10.221.2.0
site3: 171.28.18.0

Since site3 is using a public address for some weird reason I think the traffic is avoiding the VPN, would this assumption be correct? If so how can I rectify the issue, e.g. force 171.28.18.* addresses down the tunnel?

Thanks,

James

[jimp]

If the subnet is specified as the remote subnet for the IPsec tunnel, it should already be using the tunnel.

That said, IPsec doesn't route in the traditional sense. If traffic matches the tunnel definition, it's just grabbed and put on the tunnel.