31–40 of 61 posts
Earlier quoted context omitted.
It is time to be nftables enlightened instead.
It's more of a netfilter (the thing behind iptables and nftables) diagram rather than just iptables. If you know how iptables maps to that diagram you are very likely to be able to quickly understand how nftables does too.
Earlier quoted context omitted.
There’s complication, and there’s complexity. Fools admire complication, engineers design solutions to complex problems. This is a diagram explaining the latter.
I think it was put pretty well by describing things as accidental complexity (of which you want as little as possible) and essential complexity, which is inherent to the problem domain that you're working with and which there is no way around for. The same thing could sometimes fall into different categories as well - like going for a microservices architecture when you need to serve about 10'000 clients in total vs…
I'd phrase it to reasonable taken trade-offs for customer/user support and/or selling products.
> going for a microservices architecture when you need to serve about 10'000 clients
So far I am only aware of the use case to ship/release fast at cost of technical debt (non-synchronized master) of microservices. As I understand it, this is to a large degree due to git shortcomings and no more efficient/scalable replacement solution being in sight. Or can you explain further use cases with technical necessity?
That's pretty cool! If someone could program a visualization tool that would generate such diagrams automatically, that would be even cooler (but likely a mission impossible).
This place needs more of this kind of documentation. I failed to use IP tables for years. I bought books. I copied recipes from blog posts. Nothing made sense, everything I did was brittle. Until I finally found a schematic showing the flowchart of a packet through the kernel, which gives the exact order that each rule chain is applied, and where some of the sysctl values are enforced. All of a sudden, I could write…
Was it this one? https://en.wikipedia.org/wiki/File%3aNetfilter-packet-flow.s...
For anyone who is interested, the author of this diagram also made a Linux disk I/O diagram ( https://zenodo.org/records/15234151 ). These diagrams are from his book Operativni sustavi i računalne mreže - Linux u primjeni ( https://zenodo.org/records/17371946 ) Shout out to the brilliant and generous work of the author!
Do you know if there is a English version of the book?
Earlier quoted context omitted.
Do you know if there is a English version of the book?
If the author agrees, I could try to learn Serbo-Croatian (I'm Polish, good with languages) and translate it to English. I'm kinda a burnout Linux geek, who cannot look at computers much more. Translating a book would be fun, but I would need some sponsoring. Amadeusz at [the old name of icloud].com
you could try do a first pass in an AI model to translate and then proof-read it for quicker translation. good luck, it would be fun and potentially impactful ;)
Doesn't even go into iptables/nftables
This place needs more of this kind of documentation. I failed to use IP tables for years. I bought books. I copied recipes from blog posts. Nothing made sense, everything I did was brittle. Until I finally found a schematic showing the flowchart of a packet through the kernel, which gives the exact order that each rule chain is applied, and where some of the sysctl values are enforced. All of a sudden, I could write…