- CheckMates
- :
- Products
- :
- Quantum
- :
- Threat Prevention
- :
- Re: IPS not working - "Threat prevention requires ...
- 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
IPS not working - "Threat prevention requires topology to be defined"
We have 2 x virtual AWS gateways, with IPS blade, but IPS does not seem to block anything although the policy does install. We are on R80.30
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
R80.30 is End of Support this month…recommend upgrading to a supported release.
Have you configured the topology in your gateway object(s)?
Specifically have you assigned interfaces as Internal or External?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Looking at your second screenshot, your Access Control Policy is installing, but it looks like your IPS policy is not due to an issue with your topology. What does the output of ips stat show? Does it show an active profile?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I believe @AaronCP is correct. Warning clearly indicated topology issue. Also, make sure that under ips setting on gateway properties, it shows "according to policy" and NOT detect only.