Just started working for two months, in addition to some transactional things, it is actually learning network knowledge. Today, I suddenly want to organize what I have learned, or you can play a guiding role in future learning.
In fact, the network knowledge has always been learning, but always feels only a collection of fragments, fragmented knowledge, always feels there is no learning direction, that is, not to grasp the network in the whole!
Through this study, I feel that this has a certain strengthen, although there is still a considerable gap (written by BLOG, it is really terrible).
For the current work, I summed up several aspects as my thinking:
1 Network learning, first is a network level, model learning. The network model is an outline of network learning, truly understands the model, which has its own opinion to a certain extent, and has the feeling of learning. Learning the network model, not only every level of the memory OSI model, I feel that the real understanding is to understand what problems do every layer, how to provide meaningful service primitives and how to isolate the lower layer Services; Different protocols have different focuses, there are different trial ranges; these are the focus of the truly understanding of the network model and the place where it is necessary.
2 The understanding of the specific agreement, the understanding of the specific agreement is also better to understand what the problem-oriented domain and what the agreement is to solve these problems; only a few bytes in the memory protocol, the consequence of the implicit meaning is to set foot on the New Agreement Not returning, there is always no way to have a more profound understanding.
Written two, I feel that the style is wrong, huh, huh, I always don't adapt to the blog writing style, I feel the work report;
In fact, I want to write my personal learning requirements; except for the two, there is also a related knowledge of network performance analysis; the end is the use of the tester;
Feeling that the Cisco's network model is always focused on the application of the network layer. You want to understand OSI in his architecture, you don't live in the edge of the fish, and the instructions on other levels are actually resolved on the network layer. However, after all, Cisco is not a teaching institution. His model is to solve the problem, not to prove the greatness of the OSI model, so the Cisco device is blurred to a part of the transport layer below to a certain extent, and considering the factors of some application layers This will have a market;
Suddenly, in the operating system structure, the pure layers and complete integrated structures have no market, and the successful system is not a hybrid, huh, huh, not just politics, technology is also a balanced product.
The switch technology is essentially just a bridge concept. It has now replaced the router, and the highest-end GSR also puts S in front of R. When you read the book, I only know TCP / IP. I thought the network is the host plus router, but the actual network is then complicated; now it is only the truly great great greatness of the TCP / IP protocol cluster, can connect different types, different protocol subnets .
