-
Notifications
You must be signed in to change notification settings - Fork 76
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
You may just need to add a default logging rule #52
Comments
Yes get those mails to "[psad-status] firewall setup warning on domain.tld!" rules are in the INPUT and FORWARD |
@HelioB - you should really have a default deny policy on the @mrash - I get a similar message:
For the last rule in the
|
Regarding #50; the latest version of PSAD has finally landed in Fedora. Now I also get this warning:
I do have drop rules for INPUT and FORWARD in both iptables and ip6tables.
Yet, PSAD does not detect the chains:
I do not use firewalld, I use the native ip[6]tables.
What am I missing here? |
... Should be enough what version you using? package/installed with the install.pl |
On an Arch Linux
I also set in
I also use a
|
I don't think a default drop policy is required, my last rule for input and forward drops all. When I start PSAD with
My config is as follows:
|
My issue was resolved with psad-2.4.6-1.fc29.x86_64 |
On my Ubuntu 20.04 have the same problem with INPUT, even iptables has LOG rules. |
In my case the problem with Debian 11 was the fact, that rules added manually are gone after a reboot. And since I use ipv6 too, I got the message 2 times in the email. My solution was to add the following script to the folder Note: the script must not have an .sh extension otherwise it will not be executed. You can test if it will be loaded by running the command
As an alternative you can use the package https://serverfault.com/questions/904938/iptables-didnt-restore-the-new-rules-after-reboot |
I'm faced with this erro
But this is my iptables rules:
there is som problem?
The text was updated successfully, but these errors were encountered: