Skip to content
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

Variant of "shield-trigger-iptables" script to cope with ipset #2

Open
arnaudf92 opened this issue Apr 21, 2024 · 3 comments
Open

Variant of "shield-trigger-iptables" script to cope with ipset #2

arnaudf92 opened this issue Apr 21, 2024 · 3 comments

Comments

@arnaudf92
Copy link

arnaudf92 commented Apr 21, 2024

Hello,

I use pam_shield since few months now.
I've noticed that as iptables rules are added (reached 440 in my case), the download bandwidth reduces progressively.
For example I lose around 400MB on speed tests, Curl download, ...

For those interested in I modified the "shield-trigger-iptables" script so it can cope with "ipset" netfilter extension if installed.
With ipset there is no more bandwidth penalty as only one rule is needed and all blacklisted ip are stored in an indexed manner (https://ipset.netfilter.org/index.html)

The modified script is attached : shield-trigger-iptables-mod.zip

Regards.

@h0tw1r3
Copy link
Owner

h0tw1r3 commented Apr 22, 2024

Using an ipset sounds like a nice performance improvement.
Please open a pull request with your changes.

@arnaudf92
Copy link
Author

Hello,

Ok. I will do that.
For the moment, test period is ok :)

@arnaudf92
Copy link
Author

Hello Jeffrey,
When you have time, could you pls check/answer the discussion in the pull request ?

Thanks.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants