Link to home
Start Free TrialLog in
Avatar of abcam
abcam

asked on

Should a 100.0.0.0 or 100.x.x.x network be used internally? Are there risks?

Is it a good practice to use a 100.x.x.x network internally?  Is the 100.x.x.x network routable?
Avatar of Tolomir
Tolomir
Flag of Germany image

Yes it is routeable so you should use 10.x.x.x instead.

Tolomir
ASKER CERTIFIED SOLUTION
Avatar of Tolomir
Tolomir
Flag of Germany image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of jtdebeer
jtdebeer

For private IP Range always evaluate the amount of nodes / clients you would like to accomodate on each subnet.

Class A would give you maximum nodes per subnet
Private Range 10.0.0.1 - 10.255.255.254

Class B good mixture
Private Range 127.16.0.1 - 172.31.255.254

Class C - 254 hosts with a vast amount of subnets
254 Nodes per subnet ( 255 subnets)
Private Range 192.168.0.0 - 192.168.255.254
Avatar of abcam

ASKER

Thanks
Oddly enough, I have a client who has a 100.0.50.0/24 internal network set up. I just discovered that today. Whoever set them up originally obviously was not the right person to be setting their network up.

It hasn't been a problem yet that I know of for them, but hypothetically if there was a website at each ip address in the 100.0.0.0/8 range, they would not be able to reach them. That's hypothetically 16,777,214 websites they wouldn't be able to reach.
Thanks for sharing. Yes you are right, I get the same issues when "playing" with vmware  server / player. Masking parts of our internal 192.168.x.x. subnet. So I always reconfigure vmware to use 10.  subnets