This discussion has been locked.

You can no longer post new replies to this discussion. If you have a question you can start a new discussion

IPSEC VPN Tunnel up, but no route to host

Hi all,

we have a problem with a vpn tunnel to a data center, the tunnel itself is up and running, however the VPN log shows the error messsage "No route to Host".
The network we're trying to reach is public, ie. there's no private network behind the datacenter's gateway, tunnel status shows SA: 10.43.1.0/24=82.123.73.11 61.244.224.254=61.244.224.0/24. I suspect our astaro is routing all requests from the dc through our internet gateway instead of the VPN.

Correct me if I'm wrong, if not what do i need to configure for proper routing?

thnks
Marco

This thread was automatically locked due to age.

Parents

0 BAlfson over 12 years ago

62.245.225.254 is in 61.244.224.0/24, so I wonder, like GMF, if that's a problem. Best Guess is that they are NATting on the other side to a VPN server on a different IP - that would cause the VPN ID to be wrong, and you would need to change your Remote Gateway definition.

Can you get more detail from the data center?

Cheers - Bob

Sophos UTM Community Moderator
Sophos Certified Architect - UTM
Sophos Certified Engineer - XG
Gold Solution Partner since 2005

MediaSoft, Inc. USA
Cancel
Vote Up 0 Vote Down

Cancel

Reply

0 BAlfson over 12 years ago

62.245.225.254 is in 61.244.224.0/24, so I wonder, like GMF, if that's a problem. Best Guess is that they are NATting on the other side to a VPN server on a different IP - that would cause the VPN ID to be wrong, and you would need to change your Remote Gateway definition.

Can you get more detail from the data center?

Cheers - Bob

Sophos UTM Community Moderator
Sophos Certified Architect - UTM
Sophos Certified Engineer - XG
Gold Solution Partner since 2005

MediaSoft, Inc. USA
Cancel
Vote Up 0 Vote Down

Cancel

Children

No Data

IPSEC VPN Tunnel up, but no route to host

Submitted a Tech Support Case lately from the Support Portal?