|
| Recent
Articles |
Different Way To Monitor Your Terminal Server...
In the past I have discussed the Citrix Resource manager and Windows Performance monitor as ways of troubleshooting your environment. There is another tool that's free from Microsoft that might aid you in...
Configuring Standard Access Lists
Access Control Lists (ACLs) allow a router to permit or deny packets based on a variety of criteria. The ACL is configured in global mode, but is applied at the interface level. An ACL does not take effect until it is expressly...
Outsourcing The Grunge Work
Interesting ideas floating around today, the basic premise is that people are earning a lot of money to build and tear down ACL's, manage routers, switches, firewalls, and other general day to day maintenance.
Novell Banks On New Microsoft Customers
The agreement between Novell and Microsoft on marketing SuSE Linux to Microsoft customers seeking a heterogenous environment of Windows and Linux servers has been bolstered by a trio of deals with financial ...
Hardware Load Balancing Lightens Server Load
Load balancing is the even distribution of computer processing and communication activities so that a server is not overwhelmed. Load balancing is especially important for networks where it is difficult to...
Oracle E-Business Suite's New SysAdmin Features
Fear not System Administrators: There are exciting new system administration features in the pipeline for managing e-Business Suite environments. Well, I've made it back home to Charlotte and I'm getting...
|
|
02.09.07
Why Do We Need Private Address Ranges?
 By
Chris Bryant
When you're studying to pass the CCNA, you're introduced to "private addresses", the address ranges formally referred to as RFC 1918 Private Addresses.
(RFC stands for Request For Comment; to see a typical RFC, just put that term in your favorite search engine.)
There are three ranges of 1918 Private Addresses, one in each major network class.
Class A: 10.0.0.0 /8
Class B: 172.16.0.0 /12
Class C: 192.168.0.0 /16
Be careful - these masks are not the classful network masks you're familiar with!
The need for private address ranges arose when we started running out of IP addresses. (A lot of us never thought that would happen, but a lot of us used to think we'd never need storage units bigger than floppy disks, too.)
You can imagine that as networks began to be installed in offices and schools worldwide, the finite number of IP addresses became a restrictive factor.
Many devices that were using these precious IP addresses did not need to communicate with any device outside its own local area network (LAN).
Therefore, these devices could be assigned an IP address that could be used on another device in another LAN - but these devices would not be able to communicate across the Internet.
It was decided to create network address ranges that would be used exclusively for such devices.
That's why when you go from one local area network to another, you'll usually see hosts with IP addresses from the above three ranges.
Of course, as time went on, more and more of these devices did need to reach hosts across the Internet.
That's where NAT - Network Address Translation - comes into play. But that is a subject for another tutorial!
About the Author:
Chris Bryant, CCIE #12933, is the owner of The Bryant Advantage (www.thebryantadvantage.com), home of FREE CCNA and CCNP tutorials and daily exam questions, as well as The Ultimate CCNA and CCNP Study Packages.
For a FREE copy of his latest e-books, "How To Pass The CCNA" or "How To Pass The CCNP", and for free daily exam question, visit the website and download your copies!
|
