Re: Increase Addresses
- From: Stonecold316 <Stonecold316@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Tue, 16 Aug 2005 11:00:03 -0700
Thank you very much one last thing to make sure i have it, you state
255.255.255.252 mask but in next section stated 255.255.252.0. Which is
correct
> What should the subnet mask be?
> 255.255.255.252
>
> Our network ID is 192.168.0.0
> Subnet Mask is 255.255.252.0
> Number of hosts is 1022
> Our host range is 192.168.0.1 to 192.168.3.254
"Neteng" wrote:
> Sure. All your devices (including the router) fall in your subnet range of
> valid address. Your valid host range is 192.168.0.1-192.168.1.254, this is
> one subnet. What your doing is commonly referred to as supernetting. Let's
> look at an example:
>
> 192.168.0.1 255.255.255.0
> 192.168.1.1 255.255.255.0
>
> These two subnets are each a class C. For one to talk to the other a router
> would need to be in between. But we don't have a router and I need more than
> 254 addresses on my network. What are my options? Use a Class B address with
> a default or adjusted mask or we can supernet the two class C networks
> together. Instead of the subnet mask of /24 we move the bit to the left.
> This increases the number of host available on that subnet.
>
> Our network ID is 192.168.0.0
> Subnet Mask is 255.255.254.0
> Number of hosts is 510
> Our host range is 192.168.0.1 to 192.168.1.254
>
> Basically we 'merged' the two Class C networks together and formed a bigger
> one (by changing the subnet mask).
>
> Now I want to converge the following subnets:
>
> 192.168.0.0
> 192.168.1.0
> 192.168.2.0
> 192.168.3.0
>
> What should the subnet mask be?
> 255.255.255.252
>
> Our network ID is 192.168.0.0
> Subnet Mask is 255.255.252.0
> Number of hosts is 1022
> Our host range is 192.168.0.1 to 192.168.3.254
>
> Again this one large network that encompasses four Class C networks.
>
> To answer your questions; even though you have multiple "networks" they are
> all encompassed by the subnet mask. You don't need a router on each
> "network" because the subnet mask has changed it into one large network.
>
>
>
> "Stonecold316" <Stonecold316@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
> news:F29D97C8-AE71-4ECA-B701-E4C3051CFEF1@xxxxxxxxxxxxxxxx
> > OK I can deal with that but can you answer how the curretn scope
> > works(192.168.0.1-192.168.1.254/23 when there is only one interface on the
> > router(192.168.1.254) and no .0 routers?
> >
> > "Neteng" wrote:
> >
> > > No, You need a router that has four LAN interfaces, each one having a
> > > different subnet. For example eth0 is 192.168.0.0, eth1 is 192.168.1.0,
> etc.
> > > For devices on one subnet to talk to devices on another subnet, it has
> to go
> > > through the router.
> > >
> > >
> > > "Stonecold316" <Stonecold316@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
> > > news:DD06EC6B-D599-49CB-9955-8E3A9E1FEC21@xxxxxxxxxxxxxxxx
> > > > -----Router 192.168.1.254 255.255.254.0-------
> > > > -----------switch----------
> > > > ^
> > > > ----192.168.0.x-----------------192.168.1.x
> > > > ^
> > > > DHCP Server 192.168.0.100 255.255.254.0 Default gateway
> > > > 192.168.1.254
> > > > Current Scope 192.168.0.1-192.168.1.254
> > > > So you are saying 4 seperate scopes
> > > > 192.168.0.x 255.255.255.0
> > > > 192.168.1.x 255.255.255.0
> > > > 192.168.2.x 255.255.255.0
> > > > 192.168.3.x 255.255.255.0
> > > > And change the router to 192.168.1.254 255.255.255.0 ?
> > > >
> > > >
> > > > "Phillip Windell" wrote:
> > > >
> > > > > I didn't post earlier,..but the whole thing is a bad idea from the
> > > > > beginning. You should keep the number of Hosts per segment down
> below
> > > 300.
> > > > > A straight 24bit mask does this fine. You should divide the system
> up
> > > into
> > > > > 254-host subnets (24bit mask) and use a LAN Router or Layer3 Switch
> > > between
> > > > > the segments.
> > > > >
> > > > > --
> > > > > Phillip Windell [MCP, MVP, CCNA]
> > > > > www.wandtv.com
> > > > > -----------------------------------------------------
> > > > > Understanding the ISA 2004 Access Rule Processing
> > > > > http://www.isaserver.org/articles/ISA2004_AccessRules.html
> > > > >
> > > > > Microsoft Internet Security & Acceleration Server: Guidance
> > > > > http://www.microsoft.com/isaserver/techinfo/Guidance/2004.asp
> > > > > http://www.microsoft.com/isaserver/techinfo/Guidance/2000.asp
> > > > >
> > > > > Microsoft Internet Security & Acceleration Server: Partners
> > > > > http://www.microsoft.com/isaserver/partners/default.asp
> > > > > -----------------------------------------------------
> > > > >
> > > > >
> > > > >
> > > > > "Stonecold316" <Stonecold316@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in
> message
> > > > > news:81F6A2FA-DD21-4229-8E9D-B87EA7A3DA14@xxxxxxxxxxxxxxxx
> > > > > > Slight config error in original post we currently have
> > > > > > 192.168.0.1-192.168.1.254 with a mask of 255.255.254.0 DHCP server
> is
> > > > > > 192.168.0.100. We have a router configured with 192.168.1.254 and
> also
> > > our
> > > > > > default gateway. Do we need an addition router to perform this
> task.
> > > scope
> > > > > > changes.
> > > > > >
> > > > > > "Neteng" wrote:
> > > > > >
> > > > > > > Network Subnet Mask #Hosts Host Range
> > > > > > > Broadcast
> > > > > > > 510 Hosts
> > > > > > > 192.168.0.0 255.255.254.0 510 192.168.0.1 to
> > > 192.168.1.254
> > > > > > > 192.168.1.255
> > > > > > >
> > > > > > > 1022 Hosts
> > > > > > > 192.168.0.0 255.255.252.0 1022 192.168.0.1 to
> > > 192.168.3.254
> > > > > > > 192.168.3.255
> > > > > > >
> > > > > > > I would highly suggest using multiple Class C's and separate
> with a
> > > > > router.
> > > > > > > Any more than 250 devices on a segment and performance blows.
> > > > > > >
> > > > > > >
> > > > > > > "Stonecold316" <Stonecold316@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in
> > > message
> > > > > > > news:48D3C37B-E7EB-4DFA-BF67-381E102A8D22@xxxxxxxxxxxxxxxx
> > > > > > > > What should the mask be. I plan on removing the curretn scope
> and
> > > > > > > recreating
> > > > > > > > as 192.168.0.x-192.168.3.x What should the mask be
> > > > > > > >
> > > > > > > > "Neteng" wrote:
> > > > > > > >
> > > > > > > > > Check your subnet masks.
> > > > > > > > >
> > > > > > > > >
> > > > > > > > > "Stonecold316" <Stonecold316@xxxxxxxxxxxxxxxxxxxxxxxxx>
> wrote in
> > > > > message
> > > > > > > > > news:C4920C77-B123-4D2B-9318-AD58D39F31C2@xxxxxxxxxxxxxxxx
> > > > > > > > > > We currently have a scope of 192.168.1.x-192.168.2.254
> with a
> > > mask
> > > > > of
> > > > > > > > > > 255.255.254.0 .DHCP server is on .0 and our router is on
> ..1 We
> > > > > want to
> > > > > > > > > > increase our address due to more devices being added to
> the
> > > > > network By
> > > > > > > > > adding
> > > > > > > > > > a .2 and .3 to the scope. I tried to delete the current
> scope
> > > and
> > > > > > > recreate
> > > > > > > > > it
> > > > > > > > > > 192.168.1.x-192.168.3.254 with a mask of 255.255.254.0. .
> We
> > > were
> > > > > able
> > > > > > > to
> > > > > > > > > > obtain and IP from the .2 but could not ping or resolve
> and
> > > > > address
> > > > > > > on
> > > > > > > > > the
> > > > > > > > > > network. I reverted back to the original config for now.
> Any
> > > help
> > > > > > > would be
> > > > > > > > > > greatly welcomed
> > > > > > > > >
> > > > > > > > >
> > > > > > > > >
> > > > > > >
> > > > > > >
> > > > > > >
> > > > >
> > > > >
> > > > >
> > >
> > >
> > >
>
>
>
.
- Follow-Ups:
- Re: Increase Addresses
- From: Neteng
- Re: Increase Addresses
- References:
- Increase Addresses
- From: Stonecold316
- Re: Increase Addresses
- From: Neteng
- Re: Increase Addresses
- From: Stonecold316
- Re: Increase Addresses
- From: Neteng
- Re: Increase Addresses
- From: Stonecold316
- Re: Increase Addresses
- From: Stonecold316
- Re: Increase Addresses
- From: Neteng
- Re: Increase Addresses
- From: Stonecold316
- Re: Increase Addresses
- From: Neteng
- Increase Addresses
- Prev by Date: Re: Time Sync Monitoring Tool
- Next by Date: Re: DHCP Client question
- Previous by thread: Re: Increase Addresses
- Next by thread: Re: Increase Addresses
- Index(es):
Relevant Pages
|
