I've got replies ranging from "great idea, totally understand
what youre trying to do" to "moron just use 1918." So I
guess a bit more about the scenario is in order.
This lab *could* be filled with millions of hosts (real/simulated)
and thousands of networks (real/simulated). This lab is
a sort of add on to an existing lab built out of 1918 address
space---10, 172, 192. Two zones will be created consisting
of 172 & 192 space and the other would be 1 10 100. Firewalls
will separate the two as well as other subzones, etc. I've been
asked to investigate how to make it easy to do the following:
1) create manageable and quickly adaptable firewall rulesets
2) create an IP plan that will lend itself to quick human parsing
both in routing tables and router/firewall logs
3) consider that the lab will likely have machines that require
patching/updates, etc from the real internet.
Imagine you want to create an environment for experiments.
You want to reduce complexity as much as possible and create
a scenario where feedback of a test is quick...doesnt require
much memorization of what is what and that allows you to suddenly
stop and rerun tests. Rapidly. Think of access lists,route tables,
firewall rulesets and logs. If you're running tests do you want too
see results such as 192.168.22.0, 172.16.89.22, 10.129.20.222,
10.12.22.2? Wouldnt it be easier if your test results looked
like this: 1.10.1.1, 10.10.1.1, 100.10.1.1, 1.1.1.1, 10.1.1.1,
100.1.1.1, etc?
Thanks....I really appreciate everyone's feedback on this.
