3 ms·
Brilliant write up. Lots of this topic is so much easier to understand when it’s presented from first principles, without any of the LXC or Docker helpfulness
by gorgoiler 6y ago
Brilliant write up. Lots of this topic is so much easier to understand when it’s presented from first principles, without any of the LXC or Docker helpfulness hiding the details.
(If the author is reading, thank you! I’ll likely use this material for the pupils in my computer club.)
Managing an IPv6 stack alongside IPv4 is also very informative. IPv6 is still not widely deployed — SMTP is likely tied to v4 for all eternity — but it’s incredibly useful for managing multiple sites of inventory over the internet. Seeing RFC1918 style 10.x.y.z private addresses and IPAM in use by internal ops and IT in 2021 brings tears to my eyes.
Adding a section on using conntrack to watch the way in which the kernel handles MASQUERADE and DNAT would be illustrative as well.
I really like the diagrams too.
- iximiuz 6y agoThank you very much for your feedback! I appreciate it a lot because at the end of the day that's what keeps me motivated!
- gorgoiler 6y agoThe ip tool chain is a worthy thing to promote. I especially like all of the replace verbs, which I wish I’d known about sooner. They make idempotency much simpler to express without any if ! ip thing get <long list of route args>; then ip add <same list of args> ; fi stuff.
- john-tells-all 6y agoThat's cool! Here's a synopsis of `ip replace`: "replace will either modify an existing address or create a new one if the specified address does not exist" https://serverfault.com/questions/476926/understanding-ip-addr-change-and-ip-addr-replace-commands/666521#666521 https://serverfault.com/questions/476926/understanding-ip-ad...