NetPractice
by bhagenlo
written for version 2
This document is a System Administration related exercise.
Hm. Okay. That is definitely right. But, to be more specific:
This project is an exercise only about how to set up subnets of Computer Networks.
While not exactly being unhelpful, this does not give one a much bigger understanding of the Internet, either.
Let's go for that instead, shall we?
Let's turn this project learning-wise into the project it could (or should?) have been.
We'll try to learn about the following:
- The general history/ideas of the Internet
- The OSI Model
- What an RFC is
- TCP/IP
- HTTP
- And, finally, how subnetting works.
Okay.#Prerequisites
Well, understand what each box means. The key terms here are IP, destination and next hop. When trying to do the exercises, I'd advise you to: If you're doing it like that, it should be relatively easy to set up the respective nets on their own correctly. In case you're still encountering issues, it is quite probable that either: That being said, I encourage you to ask a peer for 5 minutes of their time to help you when you're stuck. It'll be worth it. In addition to that, don't hesitate to take a look at tblaases solutions.#During
1.1.1.1
is simple, 192.168.12.1
is not.)/30
.
You did it, and are ready to practice for the eval? Well, most skills require some drill. And this one definitely does. This way, you'll probably be well under 15 minutes, and might have some time left to explaing to your peer what the heck you've been doing there (in case they don't know already). Have fun :)#Cleaning Up
Start the project in practice mode, and practice until you've solved every level (at least) 3 times correctly. Then, you should be fast enough to do it in under 15 minutes.
This one's easy. No more networks. Watch some other episode of Crash Course Computer Science.#Aftercare
Alternatively, may I interest you in reading a fun RFC? Or ... a relevant one?
I hope I've fulfilled my promise, and you now not only know more about subnetting, but also about the Internet as a whole.
See you :)
And may your IP ranges never clash.
#Pointers