![]() ![]() If you have existing policy based VPN's then open the current encryption domain group, inside that group add a new network object: network address: 0.0.0.0, net mask: 0.0.0.0.if you have no other VPN's and don't expect to ever need a policy based VPN, then add grp.empty as your encryption domain.Open the centre gateway, Click network management, Select VPN Domain, now you have two options: On topology tab, set manually defined topology, create a new simple group, with NO OBJECTS in it (ie an empty group).Create a new interoperable device, choose a unique name and give it the Public IP of Azure.The Checkpoint can be participating in other Policy Based / Domain based VPN's without impacting them In this config all traffic from Azure will be tunnelled to the Checkpoint. Steps for Checkpoint cluster to Azure Route based vpn (based on R80.20) Sk101275 will give you about 20% of what you need, so I am writing this up in case it helps others. I had a bit of struggle to get this working initially, as Azure don't provide configs for Checkpoint and they operate a bit different to AWS route based VPN's. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |