[dead]
Entire Linux Network stack diagram (2024)
21–30 of 61 posts
Re: Entire Linux Network stack diagram (2024)
#22For containers you will also have own TCP/IP stack similarly to what is shown for VM on the diagram, this is done when a container uses slirp4netns to provide networking. An alternative is to use kernel TCP/IP stack, this is done when pasta is used for networking, diagram on this page shows the details:https://passt.top/passt/about/.
Re: Entire Linux Network stack diagram (2024)
#23For 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!
The Disk I/O diagram is excellent, thank you for sharing.
Re: Entire Linux Network stack diagram (2024)
#24Fools admire complexity.
There’s complication, and there’s complexity. Fools admire complication, engineers design solutions to complex problems. This is a diagram explaining the latter.
Re: Entire Linux Network stack diagram (2024)
#25Is it possible we see the diagram as an svg? I am seeing it only as embedded in the pdf, and really difficult to read .
Click on "Download" below the embedded PDF viewer and you'll get the PDF.
Re: Entire Linux Network stack diagram (2024)
#26Earlier quoted context omitted.
Can you share the diagram? Would love to become iptables-enlightened.
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.
Re: Entire Linux Network stack diagram (2024)
#27Any recommendations for a map of Linux user-space network management options?
Re: Entire Linux Network stack diagram (2024)
#28qdisc is too small in this diagram and to easy to miss.
Re: Entire Linux Network stack diagram (2024)
#29Fools admire complexity.
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 at some point actually needing to serve a lot of concurrent requests at any given time.
Re: Entire Linux Network stack diagram (2024)
#30I'm not sure if this takes into account para-virtualized networks on VMs, ie. VMware vm's with "virtual" hardware access It's been a few years for me tho, so perhaps it's covered with the VM section. Lovely diagram, thanks for sharing it!
These usually attach in the bridge or NAT flow.