Advisory: Support Portal Maintenance. Login is currently unavailable, more info available here.
We have 5 Sophos UTM devices deployed and 1 of several tunnels seems to connect but not pass any traffic. We have disabled all IPS and temporarily added firewall rules to allow traffic, including checking ICMP settings on the affected firewalls. The settings on the remote gateways, tunnels, etc, are all identical to fully functioning tunnels.
We recently noticed this problem after the second to last firmware update (9.703-2), but we are unsure if it occurred prior to that as one of the problem firewalls was offline for several months prior to seeing this issue. Other ipsec tunnels from the same firewalls do not show the same issues. We have checked the ipsec logs and see no useful information.
Has anyone else seen this behavior or have suggestions?
So unfortunately this issue resurfaced. We are unable to troubleshoot this week as we are sorting out an issue with an ISP uplink, but as soon as that is rectified (soon hopefully) we will resume testing on this. Our first step will probably be to get the latest update package (9.704). Next we will likely run the trouble shooting mentioned in above posts. Hopefully will have more info in less than a week.
Have you tried to change the security ciphers in phase 1 or 2? Is the tunnel running in strict mode? Often in case of trouble Phase 2 could cause problems in key exchange. Is DPD running?
We have not modified the security ciphers in either phase as we use the identical (old) settings on other tunnels on the same OS and comparable hardware. DPD is not something I'm familiar with. Strict mode is not enabled.
DPD recognizes a PEER thats not working and tries to rebuild it. What says the log file ? Is there something to see like "invalidkey esp@XYZ(number of the critical connection)" ? On both sides to be looked at.
Where is the DPD setting located? Nothing useful/pertinent in the logs, still.
DPD can be set in site-to-site "Advanced". Do you use "Nat-Traversal" on both sides and what about compression?
DPD must be set on both sides.
DPD is enabled on both sides. NAT-travs is not enabled on either side, and we've never had it enabled and have other tunnels up. Compression is not being used.
I will have to break out wireshark/packet captures tomorrow and dig a little deeper, it seems to be just this one tunnel that is having the issues.
Again, other tunnels with identical settings work. It's specific to one of these firewalls that's throwing us the issue of not passing traffic despite having an established tunnel. We understand and know how to get a basic IPSec tunnel up.
Are your utms behind a modem or router? Otherwise nat-traversal is bad. Wireshark will not help you. You must activate Log everything on both tunnel sides and analyze the logfile. Site-to-side vpn debug. Let it run for 6 or eight hours. Get the logfile. Look for asynchronos network or invalid key entries on both sides. Or ssh on the utms tcpdump -vv (ipsec interface).
UTM will never be able to do IKEV2 thats very bad.
I wanted to help and did not want to critizies anything.