Nexon or Bob, was there ever a solution for this... I am trying to do the same thing...
I want to route the traffic for the specific Internet destination over an IPSEC connection to a remote site to process...
Both my Main and Remote sophos devices can communicate with no problems, but now I am just lost on getting the Main network segment to redirect over to the remote network for the one specific Network that I need to source from my Remote site...
Main Sohpos
eth0: 10.0.25.1/24
IPSEC Respond only
Remote Gateway Remote Networks: 10.0.1.0/24, 8.8.8.0/24
IPSEC Connection Local Networks: 10.0.25.0/24
Remote Sophos
eth0: 10.0.1.1/24
IPSEC Initiate only
Remote Gateway Remote Networks: 10.0.25.0/24
IPSEC Connection Local Networks: 10.0.1.0/24, 8.8.8.0/24
Thanks...
This would route 8.8.8.0/24 from Main Sophos through IPSec tunnel to Remote Sophos.
However, to make sure this traffic gets translated to the internet, you will need to create a masquerading rule at Remote sophos where you masquerade 10.0.251.0/24 to the internet.
When I set it up like this, mind you not with the masquerading rule just yet, I get the following..:
tracert 8.8.8.8
Tracing route to google-public-dns-a.google.com [8.8.8.8]
over a maximum of 30 hops:
1 1 ms <1 ms <1 ms gateway [10.0.25.1]
2 gateway [10.0.25.1] reports: Destination host unreachable.
Trace complete.
So and I really making it over to the remote router, otherwise, I would expect that router to reply...?
When I set it up like this, mind you not with the masquerading rule just yet, I get the following..:
tracert 8.8.8.8
Tracing route to google-public-dns-a.google.com [8.8.8.8]
over a maximum of 30 hops:
1 1 ms <1 ms <1 ms gateway [10.0.25.1]
2 gateway [10.0.25.1] reports: Destination host unreachable.
Trace complete.
So and I really making it over to the remote router, otherwise, I would expect that router to reply...?