After reading this newest article on two private LANs, it occurred to me that most people in our industry don't have the foggiest clue about subnetting. I think this stems from host-side perspective, rather than understanding what a router uses a subnet for. The other day, I was watching a CCNP outline a address schema, similiar to the one illustrated in the article, for 3 networks that each dealt with fewer than 64 hosts. At the time I thought he was too lazy to bother calculating appropriate subnets, a mistake which will cost him once he goes to set up ACLs, but I am begining to realize that he just didn't understand how to use a subnet.
How many people here understand subnets? If you think you understand subnets; what percent of your fellow employees seem to understand subnets?
--Matt
If I paid as much attention to people as I do computers I would be married.
In my opinion, subnetting is something that's somewhat simple to understand, and nearly impossible to master.
While I understand it (see above), I am certainly thankful that it's not something I have to do on a regular basis. I have yet to meet a person who doesnt cringe at the sound of the word 'subnetting'.
I work directly with 3 other people in my company, we all understand subnetting and supernetting.
Unless you're the company's net admin, you probably don't need to know it. Even then, most companies will hire an outside contactor to do that work and let the net admin think he knows what he's doing.
Its easy to do, but with the next version of ip adressing coming out, ip6, damned if I'll understand it right away.
You are about to answer a thread that has been inactive for more than 6 months. If you still wish to proceed, please ensure that your posting is original and does not duplicate or overlap any prior responses to this thread.