- CheckMates
- :
- Products
- :
- Quantum
- :
- Security Gateways
- :
- Geo Blocking IKE Implied Rules
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Mute
- Printer Friendly Page
Are you a member of CheckMates?
×- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Geo Blocking IKE Implied Rules
Hi all,
(R81.10)
We recently changed over from the legacy way of geo blocking to the recommended use of updatable objects as a rule in the access control policy.
The geo block rule is at the top off our ruleset but I think that the firewall still is allowing any IP to connect to the IKE ports (we use CP VPN) through the implied policy.
I believe with the legacy geo policy it blocked any geo IP connecting to the firewall (this was proved with the recently issue with classifying UK IP's as Russian).
Is there a way to apply the geo rules to the applied policy?
Many thanks
Rich
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
This has just been discussed here. You can disable the implied rule within Global Properties and explicity define it on top of your rulebase in order to be able to specify geo locations for IKE.
