Recently, LwIP is used in the project. The application scenarios are complex and the reliability is high. Many strange problems have been encountered, but fortunately, a reasonable explanation has basically been found. As an LwIP beginner, I realize that learning is endless. I plan to spend three months to sort out, and then I will have a deeper understanding of the working principle of the protocol stack. I booked a time node to give myself a sense of urgency. I hope I can stick to it.
I think if you want to learn a protocol, first of all, you need to know what it is, what it can do, and which layer of OSI it is, so I attached Baidu Encyclopedia to each section. I hope that beginners can open the browser to understand At once, it will definitely do more with less.
During the time I made up my mind to write something, I am actually going through a lot of things, so I wo n’t elaborate on them one by one. I hope I can write out LwIP knowledge that is useful to you. To experience pain is a process of growth, and strive to usher in Nirvana.
Why give this column a first look at LwIP as a lightweight network protocol stack, but he is really too powerful, and at the same time he is not something that can be completely digested in days, weeks, and months. Looking back from time to time will pay off. It's the so-called book reading a hundred times, and its intentions appear. There are pits that can't be stepped on in the application process. Even a group of Daniel protocol stacks have bug records. If you encounter problems, you can first look at the Bug List during the iteration process.
At present, the wildfires and atoms on the market have detailed descriptions of LwIP, and there is a little less information about Anfulai. The things I wrote are also based on the thoughts of these predecessors standing on the shoulders of giants,
Thank you for reading this nonsense, and then let ’s get back to the topic and enter the world of LwIP.
