Guest User!

You are not Sophos Staff.

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

3 UTM S2S IPSEC VPN Version 9.403-4 failure after successfull deployment

I have 3 active UTM running 9.403-4 They were deployed in a hub VPN connection last month and one has been stable and the other needed to be rerouted in order to connect.

Primary LAN is 10.57.1.0/24,

Secondary LAN 10.57.3.0/24

Tertiary LAN10.57.5.0/25

External WAN id is hostname and is visible in public DNS

Each Firewal is assigned a public static IP address and NAT-T is off.

Masquerading rules on central translates all remote LAN to Internal 

Masquerading rules on each endpoint translates all Central LAN to Internal 

Firewall rules allow any service to and from each LAN segment.

I can create a VPN tunnel between the central location and the 10.57.3.0 and get green on both sides for the two networks (LAN and SSL VPN) but, I cannot get data to pass through this tunnel.

Ping and nslookup fail from the 10.57.3.0

Connections and firewall rules were working yesterday, today, none of the VPN connections are passing data.

Firewall logs do not show the data being blocked 

Hoping someone can help get these VPN connections stabilized



This thread was automatically locked due to age.
Parents
  • "Masquerading rules on central translates all remote LAN to Internal 

    Masquerading rules on each endpoint translates all Central LAN to Internal"

    If such masq rules were needed to get things working, you have a configuration error.  Check #3 in Rulz.

    Are you configured as in Hub-and-Spoke VPN?

    Cheers - Bob

     
    Sophos UTM Community Moderator
    Sophos Certified Architect - UTM
    Sophos Certified Engineer - XG
    Gold Solution Partner since 2005
    MediaSoft, Inc. USA
Reply
  • "Masquerading rules on central translates all remote LAN to Internal 

    Masquerading rules on each endpoint translates all Central LAN to Internal"

    If such masq rules were needed to get things working, you have a configuration error.  Check #3 in Rulz.

    Are you configured as in Hub-and-Spoke VPN?

    Cheers - Bob

     
    Sophos UTM Community Moderator
    Sophos Certified Architect - UTM
    Sophos Certified Engineer - XG
    Gold Solution Partner since 2005
    MediaSoft, Inc. USA
Children
No Data