I agree that this is an excellent approach.The best start is to learn from a good book...
Hey abbasi. I can't recommend any specific books since I learned a lot of what I know from online papers,pc mags,articles,and Q&A forums. Getting a good basic understanding from a book (or pc mags, etc, is a good idea in my opinion). I used to spend many late hours just reading the posted questions on the old Prodigy Bulletin Board which was before the current Web as we know it. Comparing the answers the people posted gave me a sense of weather it was correct or not depending on like answers. So much more updated info on the Web than in a book (depending on it's printed date,but a book is still valuable to get the basics and is a good change of pace from looking at a screen).
There's theory and then there's practice.
Somewhat like the subject of physics (which has some relatively simple mechanics [ f=ma ] as well as complex abstractions [ e=mc^2 ],
networking can be practical ethernet (with various uses like LAN layout & config), or more complex layers like UDP vs TCP vs Layer-2 programming, ....
Personally, I found it beneficial to have a problem to solve and then study the things that contribute to a solution. The teachers of Computer Science (or even more limited certificate programs on Networking) can consume countless hours on minutiae that only 1/1000 students will ever use just once. (but it makes for great tests and a means to produce grades :sigh.
Some Ethernet concepts that will take you a long way might include:
There are other network schemes, like Token Ring which has some advantages over Ethernet, but is limited to small clusters and can't be applied to the Internet.
- OSI seven layers
- Ethernet IPv4 addressing (skip IPv6 for now) which will help you understand the need & use of DHCP, DNS, Routers, Switches and Routing tables
- IP, TCP, UDP
- Need and use of Firewalls and where they are placed for most effectiveness.
- Ethernet can only run about 70-75% of the rated bandwitdh (I'll let you discover why)
- What is a PROTOCOL and how do they get used?
Of course, if you desire to pull cables in the back room and crimp connectors all of the above is totally unnecessary and you need references for pin-outs and info on mapping a physical network.
There's theory and then there's practice.
Somewhat like the subject of physics (which has some relatively simple mechanics [ f=ma ] as well as complex abstractions [ e=mc^2 ],
networking can be practical ethernet (with various uses like LAN layout & config), or more complex layers like UDP vs TCP vs Layer-2 programming, ....
Personally, I found it beneficial to have a problem to solve and then study the things that contribute to a solution. The teachers of Computer Science (or even more limited certificate programs on Networking) can consume countless hours on minutiae that only 1/1000 students will ever use just once. (but it makes for great tests and a means to produce grades :sigh.
Some Ethernet concepts that will take you a long way might include:
There are other network schemes, like Token Ring which has some advantages over Ethernet, but is limited to small clusters and can't be applied to the Internet.
- OSI seven layers
- Ethernet IPv4 addressing (skip IPv6 for now) which will help you understand the need & use of DHCP, DNS, Routers, Switches and Routing tables
- IP, TCP, UDP
- Need and use of Firewalls and where they are placed for most effectiveness.
- Ethernet can only run about 70-75% of the rated bandwitdh (I'll let you discover why)
- What is a PROTOCOL and how do they get used?
Of course, if you desire to pull cables in the back room and crimp connectors all of the above is totally unnecessary and you need references for pin-outs and info on mapping a physical network.