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

S2S VPN goes down after 24hrs

All,

I am currently on Firmware version 9.403-4 and I am experiencing a weird issue with my IPSEC site to site. after being up for 24hrs or a little more the connection drops. No changes, no nothing to the firewall policy or anything.

If fails with the following error : initial Main Mode message received on x.x.x.x:500 but no connection has been authorized with policy=PSK

Now that error is weird because it was connected and working with no problems the entire day.

Also, so far the only way for me to resolve the issue is to REBOOT the sophos firewall.

Any assistance would be greatly appreciated.

This thread was automatically locked due to age.

Parents

0 rsenio over 8 years ago

Dont really have much to go on

Whats the device on the other side of the VPN? Is the ISP on the other side changing your IP? Is the UTM behind a NAT Router?

https://www.google.ca/search?q=but+no+connection+has+been+authorized+with+policy%3DPSK&oq=but+no+connection+has+been+authorized+with+policy%3DPSK&aqs=chrome..69i57&sourceid=chrome&ie=UTF-8#q=but+no+connection+has+been+authorized+with+policy%3DPSK+sophos
Cancel
Vote Up 0 Vote Down

Cancel
0 BobbyDigital over 8 years ago in reply to rsenio

The device on the remote side is a PFsense appliance. The IP address is not changing and the UTM is not behind a NAT router.

Do you need any additional information. from logs or pcaps?
Cancel
Vote Up 0 Vote Down

Cancel
0 rsenio over 8 years ago in reply to BobbyDigital

Doesn't quite add up. This just started occurring out of the blue?

Or this hasn't worked since you set it up

Id confirm EVERYTHING on the pfsense side https://doc.pfsense.org/index.php/VPN_Capability_IPsec
Cancel
Vote Up 0 Vote Down

Cancel
0 BobbyDigital over 8 years ago in reply to rsenio

Yes it works. Traffic is traversing the tunnel and it stays up for about a day or so.

Then the tunnel drops and the logs on the sohpos box gives that error message.

as far as started out of the blue i'd have to say no. But we were able to easily reconnect after several attempts.

Now the only way to bring back up the tunnel is to reboot the sophos box.

if any additional information is needed i will be glad to provide.
Cancel
Vote Up 0 Vote Down

Cancel
0 itsNeil over 8 years ago in reply to BobbyDigital

What are the phase 1 and 2 SA lifetimes set to? This guy had a similar issue, and ended up setting the SA lifetimes to 86400 (24 hours) on both ends which seemed to resolve a similar problem:

https://community.sophos.com/products/unified-threat-management/f/58/t/55782
Cancel
Vote Up 0 Vote Down

Cancel

Reply

0 itsNeil over 8 years ago in reply to BobbyDigital

What are the phase 1 and 2 SA lifetimes set to? This guy had a similar issue, and ended up setting the SA lifetimes to 86400 (24 hours) on both ends which seemed to resolve a similar problem:

https://community.sophos.com/products/unified-threat-management/f/58/t/55782
Cancel
Vote Up 0 Vote Down

Cancel

Children

No Data