3 ms·
No OP but I think there’s three parts to really getting TCP/IP: - Read the spec(s) - Learn the OS APIs deeply - Look at a bunch of real network data in e.g.
by coddle-hark 3y ago
No OP but I think there’s three parts to really getting TCP/IP:
- Read the spec(s)
- Learn the OS APIs deeply
- Look at a bunch of real network data in e.g. Wireguard
- OJFord 3y ago> Look at a bunch of real network data in e.g. Wireguard I think you probably meant data in e.g. Wireshark? But another good suggestion (or maybe what you meant) might be to look at 'real' (production) networking code in e.g. Wireguard, I imagine.