:
: My apologies; You didn't miss anything.
: In my lab all the routers are local but the project I'm working on will
have
: routers in different locations. I've been trying to pick this up from
: technical books but I'm not getting it. I'm hoping if I see it in action
it
: will make sense. So to summarize...
: router1 will look like this...
: > Ex.
: > 192.168.51.0/29 - network (all 0s)
: > 192.168.51.1-6/29 - user
: > 192.168.51.7/29 - broadcast
:
: router2 looks like this...
: > Next subnet:
: > 192.168.51.8/29 - network (all 0s)
: > 192.168.51.9-14/29 - user
: > 192.168.51.15/29 - broadcast
:
: Is that right? If I need say 50 addresses then increase the subnet...?
Yes. Maybe.
If you need 50 usable addresses, not counting the network address and the
broadcast address, then you need a 64 address subnet, IF, all 50 are pointed
to the same location. Otherwise, each locations determines the size of each
subnet.
Your network design is important here and will determine what you actually
need. One important aspect of your design should be to ask yourself this
question: "How will I support my users in this location and in each remote
location?" This assumes you are at one location and you are the
administrator. If not, you're asking for the admin. Ex. You're a contract
consultant.
The most important obvious question is how will the users communicate?
....and others...
Do the WANs connect via private or public routes? This is very important.
Here are two scenarios:
1. You have numerous locations that each have access to the Internet. You
connect across the Internet from one office to another.
What is involved here? Firewall at each location, VPN for remote access,
etc.
The subnet here is not related to the other locations.
What would work best for this location? A NAT router with one-one address
translation if you need to perform remote administration across the
Internet. It should also support VPN.
Are any server services offered here? Yes? Subnet size is determined by how
many devices need to be accessed from the Internet publicly. No? You need
a public address for the router. Everything behind the router will use
private addressing.
2. You have numerous location that each have access to the Internet. You
connect across private WANs from one office to another.
You only need addressing for publicly served services. Everything else
should be private.
3. You have numerous locations but only 1+ have access to the Internet.
Offices that do not have direct access to the Internet route across private
WANs to an office that has direct access to the Internet.
Again, you only need addressing for publicly served services. Everything
else should be private.
Note: You will have to consider that if you need VPN access for scenario 2
or 3, your VPN needs will determine what your public addressing needs are.
So, if host your own web server, mail server, etc. You'll need NAT one-one
addressing for the mail server and the web server will go in the DMZ but you
still need a public address.
Whatever design you come up with, you should always have enough public
addressing that offers you growth. The last thing you want to do is have to
change all your addressing. Been there, done that.
HTH...
--
Roland Hall
/* This information is distributed in the hope that it will be useful, but
without any warranty; without even the implied warranty of merchantability
or fitness for a particular purpose. */
Online Support for IT Professionals -
http://support.microsoft.com/servicedesks/technet/default.asp?fr=0&sd=tech