Create a Post
cancel
Showing results for 
Search instead for 
Did you mean: 
Mk_83
Contributor

Methods to Reset Site-to-Site IPSec VPN tunnel

Hello everyone,

Appliance: 9100 - Standalone - R81.20

I am having VPN tunnel DOWN and have to reboot the device to resolve the VPN tunnel to UP. So, I just want to ask if there is a way to reset VPN tunnel instead of using SmartView Monitor, vpn tu?
Cause my GW don't have SmartEvent/Monitoring Licenses so I can't reset VPN tunnel in SmartView Monitor; and when using vpn tu to delete IPSec SAs/IKE, it didn't recover.

Thanks & Best Regards.

0 Kudos
16 Replies
Tal_Paz-Fridman
Employee
Employee

Consider using Permanent Tunnels to improve the reliability of the tunnels:

https://sc1.checkpoint.com/documents/R82/WebAdminGuides/EN/CP_R82_SitetoSiteVPN_AdminGuide/Content/T... 

"As companies have become more dependent on VPNs for communication to other sites, uninterrupted connectivity has become more crucial than ever before. Therefore it is essential to make sure that the VPN tunnels are kept up and running. Permanent Tunnels are constantly kept active and as a result, make it easier to recognize malfunctions and connectivity problems. Administrators can monitor the two sides of a VPN tunnel and identify problems without delay."

0 Kudos
AlekzNet
Contributor

> https://sc1.checkpoint.com/documents/R82/WebAdminGuides/EN/CP_R82_SitetoSiteVPN_AdminGuide/Content/T... 

> Standalone - R81.20

😉

> Consider using Permanent Tunnels to improve the reliability of the tunnels:

Allowing DPD will not help if the tunnel does not establish correctly to begin with (provided there is some traffic between the enc domains).

0 Kudos
the_rock
Legend
Legend

Best way I know of to truly reset vpn tunnel is remove cp gw from vpn community, push policy, add it back, push policy again.

Andy

0 Kudos
AlekzNet
Contributor

.. just make sure you still know the correct PSK, because you will have to enter it again ..

0 Kudos
the_rock
Legend
Legend

I dont believe thats needed if you remove cp object, ONLY interoperable one.

0 Kudos
AlekzNet
Contributor

Try this in the lab 😉 And how do you know, that "the other side" is a CheckPoint?

0 Kudos
the_rock
Legend
Legend

I tried it at least 50 times lol

0 Kudos
AlekzNet
Contributor

#metoo  and every time the PSK disappeared. In any case, I would first make sure the correct PSK is known.

0 Kudos
the_rock
Legend
Legend

Im positive you would have deleted interoperable object, as there is nowhere you can put PSK on CP object in the community.

But, I agree, always good idea to know PSK.

Andy

0 Kudos
AlekzNet
Contributor

You mean if both CP FWs are managed by the same Mgmt station, right? And if it's a 3d party company?

 

0 Kudos
the_rock
Legend
Legend

I mean one CP and other one 3rd party. In such case, other object has to be presented as interoperable object.

Andy

0 Kudos
AlekzNet
Contributor

Exactly! That's why you need to know the PSK 😊

From the the original post it's not clear what "the other side" is and who controls it. So, in this case, the PSK *must* be mentioned.

0 Kudos
the_rock
Legend
Legend

But what Im saying is if you delete cp object and add it back, you dont need to know psk 🙂

You only need to know it if you delete interoperable object and put it back in the community.

Hope thats clear now?

Andy

0 Kudos
AlekzNet
Contributor

In this case yes, indeed. I interpreted it a bit wider and "looser" - the object is a CP device managed by a 3d party. So, a misunderstanding on my part 😊

the_rock
Legend
Legend

Glad we are in agreement 🙂

0 Kudos
AlekzNet
Contributor

>  when using vpn tu to delete IPSec SAs/IKE, it didn't recover.

Then there is a problem with the VPN configuration. To troubleshoot further , additional information is needed.

E.g. which Phase is failing?

what does "vpn tu list peer_ipsec <peer_IP>" show?

What do you see in tcpdump on the external interface of the firewall? tcpdump -nnni <ext_iface> host <peer_IP>

What do you see in the FW logs for the <peer_IP>?

What does "the other side" see in their logs?

Next step is to allow IKE debugging. Keep in mind, in R81.20 iked is multithreaded, so the IKE debug info can go into any of the /etc/fw/log/iked?.* file, and there is no corresponding ikeview utility anymore to conveniently "decipher" these files.

0 Kudos

Leaderboard

Epsum factorial non deposit quid pro quo hic escorol.

Upcoming Events

    CheckMates Events