Menu

Show posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Show posts Menu

Messages - RabidWolf9

#1
IDS / IPS currently are not working with 16.7, must be disabled till new patch.
#2
16.7 Legacy Series / Re: IDS kills WAN DHCP
July 29, 2016, 11:09:50 PM
Ok ever heard the statement "READ before sticking foot in MOUTH"?

In post
Upgrading to 16.7, known issues and workarounds
https://forum.opnsense.org/index.php?topic=3430.0

[1] if IPS is not working, disable it temporarily or switch to IDS mode. we are investigating the root cause

Will keep foot on floor and await the experts :)
#3
16.7 Legacy Series / Re: Upgrade to 16.7 successful
July 29, 2016, 11:03:50 PM
Lost IDS / IPS, other than no more Geo Blocking and rule sets the rest is operational.

https://forum.opnsense.org/index.php?topic=3449.0

#4
16.7 Legacy Series / Re: IDS kills WAN DHCP
July 29, 2016, 11:01:00 PM
Changed "Pattern Matcher" from "Aho-Corasick" to Hyperscan, no luck.
Enabled Hardware CRC, TSC and LRO, no luck.

Enabled and disabled Promiscuous mode, changed nothing.

IDS/IPS is now a DEAD package, will define rules as needed in firewall/rules, although almost any router can do that.

Anyone find a solution please post, Geo Blocking and other Rule Sets was an awesome feature.
#5
16.7 Legacy Series / Re: IDS kills WAN DHCP
July 29, 2016, 10:19:44 PM
Disabled all rule sets both system and user defined, applied IDS, killed WAN.
Disabled IPS mode, rebooted, WAN active again.

IPS states "Enable protection mode (block traffic).
Before enabling, please disable all hardware offloading first in advanced network."

Even though all hardware offloading in advanced network has been disabled still kills WAN.
#6
16.7 Legacy Series / IDS kills WAN DHCP
July 29, 2016, 09:53:38 PM
Upgraded to 16.7, WAN on cable modem would no longer pull DHCP. Rebooted Cable modem and OPNsense multiple times, entered manually, still a no go. Disabled IDS, rebooted and BAM, back up. Worked great before upgrade. Must be a particular rule set. My hardware is overkill so dont ask that question. Any one else seen this issue?