Remote Access IPSEC - tunnel connects but unable to access any devices

Hello,

Thank you for sharing the detailed information.

Please check whether the route added to the windows or not by running below command from windows CLI.

C:\>route print

If you can point that the route of 19.168.0.X added, follow below KBA:

community.sophos.com/.../sophos-firewall-how-to-identify-the-communication-issue-with-up-and-running-ipsec-tunnel

Hey Mayur Makvana 

This is my route print from the Windows client machine running Sophos connect:

Hmm strange, I don't recognise gateway: 169.254.128.128
(Remote client gateway is 192.168.5.1) (Sophos XG is the gateway at the other end which is 192.168.0.253)

Hey Mayur Makvana 

This is my route print from the Windows client machine running Sophos connect:

Hmm strange, I don't recognise gateway: 169.254.128.128
(Remote client gateway is 192.168.5.1) (Sophos XG is the gateway at the other end which is 192.168.0.253)

Hello,

This looks fine, can you please collect the tcpdump and drops simultaneously while pinging to the local LAN?

console> tcpdump ' host internalIP and proto ICMP

console>drop-packet-capture ' host internalIP and proto ICMP

From CLI I ran: tcpdump ' host internalIP and proto ICMP

And get this:

However, when I run: drop-packet-capture 'host internalIP and proto ICMP'

I get command not found

Hello,

I could see that the traffic reached to the firewall. It may have dropped or forwarded. 

Can you please DM with the Sophos Access ID?

Hello Aaron,

Thank you for your time over chat.

We found that the traffic was getting dropped under the IP Spoof. While reviewing, we could see that the SSL VPN is also having the same lease range configured. We suggested changing the lease range for the SSL VPN or an IPSec to get the things working.