HELP WITH MY NEW IP LAYOUT

[TornUp]

We are currently rebuilding our domain(migration from older unwell setup domains has caused problems)

 

 

our original plan was:

 

192.168.25.1 TO 192.168.25.10

FOR ROUTERS,FIREWALL,SMART SWITCHES,ETC..

 

192.168.25.11 TO 192.168.25.25

FOR SERVERS & NAS

 

192.168.25.26 TO 192.168.25.200

MAIN DYNAMIC IP ADDRESS SCOPE

 

192.168.25.201 TO 192.168.25.210

FOR NETWORK PRINTERS

 

192.168.25.211 TO 192.168.25.254

FOR IP PHONES

 

what we want todo now, is have 2 IP address Class C's(i think there called)

 

so our main workstations and VPN users are connected to

 

192.168.26.###

 

and all our static IP address stuff is on

 

192.168.25.###

 

im no good at this kind of networking, so i was wondering, how hard it would be enabling communications across these subnets....

 

any advice, is there a better way of doing this? we are a fast expanding company and if we keep it all on 1 IP range, we will run out of IP address's!!

[budgester]

You could try

 

If you currently use a subnet mask of 255.255.255.0 then you will only get 255 addresses, if you change the subnet to 255.255.252.0 then you will get

 

192.168.0.0 -> 192.168.3.255

 

That'd give you 1022 address'

 

The broadcast address will be 192.168.3.255 with a network address of 192.168.0.0

 

Hope this helps

[TornUp]

You could try

 

If you currently use a subnet mask of 255.255.255.0 then you will only get 255 addresses, if you change the subnet to 255.255.252.0 then you will get

 

192.168.0.0 -> 192.168.3.255

 

That'd give you 1022 address'

 

The broadcast address will be 192.168.3.255 with a network address of 192.168.0.0

 

Hope this helps

 

 

so.. by setting the subnet mask to 255.255.252.0

 

will i then beable to set it:

 

192.168.24.1 TO 192.168.24.255

in DHCP as reserved for static IP

 

and then set:

 

192.168.25.1 TO 192.168.255

for the dynamic IP scope?

 

 

and all of this set up on the DHCP server?

 

thanks loads for your help. think im getting my head around it..

[tomscaper]

While i am not a 100% certain i think that with that subnet you can only have the range 192.168.0.0 - 192.168.3.255

 

That would mean

 

192.168.0.0 - 255

192.168.1.0 - 255

192.168.2.0 - 255

192.168.3.0 - 255

 

Is there a reason you want 192.168.24 and 25

 

Like i said i dont understand it all fully but if anyone can confirm or put me right would appriciate it.

[apeo]

If you want .25 and .26 for whatever reason the subnet 255.255.252.0 (technically not class c but it dont really matter) would give you the following range:

 

192.168.24.0-192.168.27.255

 

So you can have any of that as part of you ip range in dhcp. BTW the ones you wish to have static .24 or .25 you would exclude (not reserve) in dhcp.

[Irazmus]

For IP ranges / subnetting I find this useful.

IP Calculator / IP Subnetting

[TornUp]

So you can have any of that as part of you ip range in dhcp. BTW the ones you wish to have static .24 or .25 you would exclude (not reserve) in dhcp.

 

right ok... so with the infomation mentioned above. this is my plan...

 

setting up a scope from 192.168.24.1 TO 192.168.25.254

 

then excluding everything from 192.168.24.1 TO 192.168.24.255

 

that will act as our static "area"(my own naming lol)

 

then leave the scope open for dynamic allocation from 192.168.25.1 TO 192.168.25.255

 

is that the best way?

 

or shall i just the #####.24.1 TO #####.24.255 out of the scope completely?

 

 

 

how does the nodes know what IP range it can look at and what it can't..

 

EG..

 

if i leave 192.168.24 out of the scope. and then put all our static IP hardware on there. will it all work ok. and beable to talk to hardware on this range(if all workstations(that are dynamic) are on the 192.168.25.# range..)

[maniac]

Well ours is set up like this;

 

the range 192.168.0.1 - 192.168.0.254 is reserved for manually assigned IP numbers, and is divided as follows;

 

192.168.0.1 is the default gateway.

192.168.0.2 - 192.168.0.4 are reserved not used

192.168.0.5 - 192.168.0.24 are reserved for Servers.

192.168.0.25 - 192.168.0.49 are reserved for Workstations requiring a static IP

192.168.0.50 - 192.168.0.99 are reserved for managed swithes and UPS's with management cards etc.

192.168.0.100 - 192.168.0.179 are reserved for network printers

192.168.0.180 - 192.168.0.199 are reserver for 'other' (One LAN box, Telephone Switchboard, Network access for the CCTV etc.)

192.168.0.200 - 192.168.0.254 are reserved for wireless Access Points.

 

We don't have any IP phones at the moment, if we did we may introduce another manualy allocated set just for them, probably the beginning of the next range.

 

192.168.1.1 - 192.168.3.254 is our dynamic range allocated by DHCP. We use a subnet of 255.255.248.0 to enable us to widen this easily if needs be, and we're not too far from needing to!

 

The key is not to restrict yourself too much when reserving addresses for manually allocation to devices, else you'll find yourself having to reserve more addresses, and then things end up all over the place. e.g we have 80 addresses reserved for printers, we only use just over half of these, but who knows what might happen in the future?

 

Cheers,

 

Mike.

[apeo]

is that the best way?

 

or shall i just the #####.24.1 TO #####.24.255 out of the scope completely?

 

how does the nodes know what IP range it can look at and what it can't..

 

EG..

 

if i leave 192.168.24 out of the scope. and then put all our static IP hardware on there. will it all work ok. and beable to talk to hardware on this range(if all workstations(that are dynamic) are on the 192.168.25.# range..)

 

When comes to deciding between the 2 options (to have or not to have static address in the scope) its a judgement call imo. Some admins prefer to have them out the scope all together and some want them in and excluded in the scope. Either way, both works so its entirely up to you. To answer your last question, yes leaving the .24 range out of the scope will still enable your network to talk to each other. What you have to understand is that all dhcp does is dish out ip addresses to network devices and without it you will have to do it all manually so as long as the scope you have specified is on the same subnet as the range of your static address it will work.