1. In order to use network knowledge to understand the network architecture of the server, troubleshoot, and solve problems. There is really no need to memorize it. The wireshark tool can analyze it for you and cannot be more detailed. Whether there is retransmission, whether there is out-of-order, the time when the data packet is received, the size of the sending window, whether the data is congested, etc.... and the analysis of the protocol, even the additional options of TCP are analyzed for you, and you can find it at any time Look at the previous packets or capture packets, if you really want to memorize them, how embarrassing will you be to write wireshark.
2. If you don’t read the TCP/IP protocol stack code, don’t engage in low-level network programming, there is really no need to read all the detailed explanations of TCP/IP. It will be very painful to read the ones you are not interested in or the ones you don’t usually use. Any book has them . "Must read", "should read", "repeated reading", "chapters that can be skipped", these are decided according to each person's own situation.
3. A person who encounters a problem and will dig deep into the essence of the problem. For example, if there is a hijacking now, it is also possible to use traceroute to look at it or google it. Therefore, it is recommended to look at 1, 2, 3, 4, 5, 7, and 17 first . , 18, 19, 20, the bold ones are the key points, I won’t say why, you must read
Combined with Tao Hui's soft article: High-performance network programming (1)----accept to establish a connection- Tao Hui's column- Blog Channel- CSDN.NET