iptables compliance #1
Loading…
Reference in New Issue
There is no content yet.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may exist for a short time before cleaning up, in most cases it CANNOT be undone. Continue?
hi there,
Great initiative. Quick question tho : why leave iptables out of the project scope? Is it a planned feature or a design choice?
(based on
Hi theonlydoo,
Thanks for your interest in this software.
The reason for leaving out iptables in favour of nftables is twofold:
That said, there are several ways for including iptables support in Pyruse; here are a few:
Either way would probably be rather easy to implement, and I’d be willing to implement the first method, if you think it is useful.
Cheers,
It is the third solution after all, as this solution benefits from automatic timeouts, the same way nftables does.
Since I do not use iptables/ipset myself, I’d be grateful if someone could report back to me if the module works or not!