-
Notifications
You must be signed in to change notification settings - Fork 753
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
rules do not work #8034
Comments
Info |
Thank you for creating an issue. For more information about the policies for this repository, The easiest option to gain traction is to close this ticket and open a new one using one of our templates. |
I dont know how to put this in one of your templates |
We need access to the suricata yaml for editing or We have to continue to manually change $HOME_NET to any in all rulesets |
Thought I might add an easy test |
After much testing, I have found the rules in the suricata rulesets not working
Neither the blocklists, nor regular rules
Quick fast forward
the solution was to change $HOME_NET in all rules to any
Blocklists started working
Regular rules started working
In the last three versions
I first wanted to change the suricata yaml and enter my IP
Not possible because on reboot reverts back
$HOME_NET in suricata is either your IP or IP range
$EXTERNAL_NET in my case does not need to be modified,
because it is assumed to mean any unless written in as something else, ie lan IP or something
protecting a network or such
Both $HOME_NET and $EXTERNAL_NET are to be hard coded into the suricata yaml
When we set up suricata
We have no way to do that
There is no where to enter your IP and have it applied to suricata
When I changed $HOME_NET in the blocklists to any
They start working, thousands of hits, yes legitimate because I am also comparing them to the pcaps
I am attacked every 5 seconds on average at idle, no browser or apps open
All spoofed IPs, many are on the ET blocklists, which were not working
Nothing is supposed to be hitting me but regular router exchange
When I change $HOME_NET to any in the regular rules, not rulesets,
I get a rule hit about every 20 to 30 minutes when I changed $HOME_NET to any
Nothing before the change
And the blocklists I got 2000 hits in 3 hours this morning
Nothing before the change
If you make a user defined rule and go to the file and look at it
It says any -> any any which is depending on direction you specified
$HOME_NET or $EXTERNAL_NET
The user defined rule does not say $HOME_NET or $EXTERNAL_NET
The user defined rule will work
Thank you in advance for opnsense community edition
Thank you for your work
PS
Opnsense allowed me to get on the internet again
One year ago I could not get on the internet for 15 seconds without
Bad guys shutting down my computer and destroying hardware
They destroyed my ISP router
A regular router doesnt stand a chance
You may have seen the news how regular home routers were used to attack cloudflare
Your work is our defense
Much much better and easier than hard coding 100,000 lines of iptables
The bad guys run bots, the global security community knows about them
They constantly attack your computer with thousands of different methods of
getting into your computer, all spoofed IPs, all automated,
Automatically changes IPs, just regular hacker software these days
I hope I have explained enough
Thanks again
The text was updated successfully, but these errors were encountered: