On Tue, 1 Aug 2000, Swart, Douwe wrote:
> These are internal addresses only, and don't need access to the Internet.
> Just need the addresses for new machines.
Your scenario indicated "running out" of addresses, indicating that
the present pool was exhausted. NAT with overload is a way to get around
this.
Your idea of a secondary interface on the same wire will also work, but
can get messy with WINS, split horizon,traffic being routed to the same
physical wire causing congestion and burning router CPU, etc.
Or, you can change the netmask to a larger one if space is available
on either side.
For example if you now use 192.168.1.x 255.255.255.0 you could
go to 192.168.<0-7>.x 255.255.248.0 and increase the network by
a factor of eight.
As with many scenarios, there are multiple solutions. If the whole
thing is using private addresses, I'd change the netmask to something
larger. If this is a design lab or exam question, there may be some
constraints that steer you to a specific solution.
DHCP is something else that may be thrown in just to make things interesting
if the scenario states that no more than x% of the machines will be on at
any time.
--
Jay Hennigan - Network Administration - [EMAIL PROTECTED]
NetLojix Communications, Inc. NASDAQ: NETX - http://www.netlojix.com/
WestNet: Connecting you to the planet. 805 884-6323
___________________________________
UPDATED Posting Guidelines: http://www.groupstudy.com/list/guide.html
FAQ, list archives, and subscription info: http://www.groupstudy.com
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
