کانال انجمن کلاد و دوآپس تبریز

این لینک ها باشه اینجا https://wiki.nftables.org/wiki-nftables/index.php/Netfilter_hooks https://wiki.nftables.org/wiki-nftables/index.php/Quick_reference-nftables_in_10_minutes https://organicprogrammer.com/2022/06/08/how-to-write-a-netfilter-firewall-part3/ https://docs.redhat.com/en/documentation/red_hat_enterprise_linux/8/html/configuring_and_managing_networking/getting-started-with-nftables_configuring-and-managing-networking https://www.usenix.org/system/files/login/articles/892-neira.pdf https://thermalcircle.de/doku.php?id=blog:linux:nftables_packet_flow_netfilter_hooks_detail #nft #nftables

So here are a rough set of rules I have decided on for myself, so I hopefully don't fall into the same trap again: Stay away from immutable distros Only use deployment tools if they make things easier (Like setting up multiple machines at once) And only use them for the parts that they actually make easier. I don't need purity here. Ditch CI/CD pipelines (I want to go back to the simplicity of a shell script in a cronjob) Stuff gets installed in the easiest way possible, preferable a container on a single host with Containerfiles neatly organized in a directory, otherwise throw it into a VM Not everything needs to be fully declarative. Just doing a backup of state is fine! Purity is a sin. Accept compromise if it makes something work better for me.