Intrusion prevention signatures not updating
For instructions on how to do that, see Using the CLI Editor in Configuration Mode in the CLI User Guide.Attack signatures have been around for long enough that the definition should be universally understood, but that's not the case.The more that you select, the more rules will be enabled.This is in part a repeat of an earlier thread but as I have now found a temporary workaround I want to bring this to more people's attention in case this is a more common problem.It is highly recommended to complete the wizard and use the recommended configuration.Using a custom configuration and enabling too many signatures may negatively impact your network.
The same problem arises in NIS 2009 16.5 but in that case an error condition is reported. This is in part a repeat of an earlier thread but as I have now found a temporary workaround I want to bring this to more people's attention in case this is a more common problem.
This seems like a reasonable goal, but achieving this goal isn't always easy.
What's challenging is the vocabulary used to describe what the product does and how it works.
CLI quick configuration is not available for this example, because manual intervention is required during the configuration.
The following example requires you to navigate various levels in the configuration hierarchy.
I found that by disabling the firewall in the router it resolved the problem, What is more even on a slow machine the LU took between 1 and 7 secs whilst a LU with the firewall installed (all assuming no updates to download) took a minute.