I checked the firewalls logs can see UDP4500 being sent but the controller doesn’t get that far when I check the controllers logs.ĭoes anyone know if there’s something different you need to do when the controller is behind a firewall with NAT? Is this checkpoint being funny? (I enabled any port on the rule to see and it still has same behaviour). You can connect your Untangle NG Firewall networks to your Microsoft Azure networks using. It negotiates UDP500 the next part of this VPN should then be UDP 4500 but the controller never sees that phase. ![]() I reloaded the firewall and the tunnel was established again. After some time of no use the tunnel was dropped but it didn't start again with interesting traffic. I have configured the vpn and it was established the first time. I can see traffic coming through but when the controller starts to negotiate the traffic through UDP 4500 it fails and does not progress to this stage. I'm trying to get a Site to Site VPN tunnel with a Checkpoint Firewall. The checkpoint firewall is set to allow UDP&TCP 500/4500 - so should be all the IKE ports. ![]() This is having traffic hit the public IP Checkpoint NATs this to an internal address which the controller has. ![]() Setting up a remote VPN solution using a 7210 controller (working to Clearpass).įor security reasons, I have placed the controller behind a firewall. 0 Kudos Reply 1 ACCEPTED SOLUTION AshC73 Getting noticed 04-05-2018 08:36 AM Sorry for the delay on an update, its been pretty hectic.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |