|
Memo on
Subnet Allocation
December 2, 2004
(see addendum below)
This document defines our official class C
subnet allocation scheme. It was carefully designed to provide optimal
manageability, efficiency and simplicity. It's been
refined and proven
over a decade in small businesses & branch offices environment. All
sites must adhere to it to minimize unanticipated conflicts and
limitations in various scenarios.
Bravo Class C (/24)Subnet Address Allocation
1 ( 1) primary gateway
DHCP scopes are universal across clients sites and BTC
2-50 (49) primary DHCP
scope
51-99 (49) auxiliary DHCP scope
100-199 (10) static
range, clt use
100 ( 1) primary server
101-109 ( 9) additional servers and key stations
110-119 (10) print servers
120-159 (40) workstations
160-189 (30) reserved (auxi gw, alt-site/HSBS/hm scopes, etc.)
190-199 (10) auxi gateways
200-254 (55) static
range, btc internal use
200 ( 1) BTC primary server
201-209 ( 9) additional servers & Key stations
210-219 (10) printers
220-239 (20) workstations
240-254 (15) reserved (auxi gw, etc.)
Reserved DHCP by MAC in
static range, or start at top-of-scope
NOTE: (Number in
Paraphrases) indicates how many addresses
|
Private Blocks |
10.0.0.0 -
10.255.255.255
172.16.0.0 - 172.31.255.255
192.168.0.0 - 192.168.255.255 |
| |
Hosts |
Netmask |
Amount of a Class C |
| /30 |
4 |
255.255.255.252 |
1/64 |
| /29 |
8 |
255.255.255.248 |
1/32 |
| /28 |
16 |
255.255.255.240 |
1/16 |
| /27 |
32 |
255.255.255.224 |
1/8 |
| /26 |
64 |
255.255.255.192 |
1/4 |
| /24 |
256 |
255.255.255.0 |
1 |
| /23 |
512 |
255.255.254.0 |
2 |
| /22 |
1024 |
255.255.252.0 |
4 |
| /21 |
2048 |
255.255.248.0 |
8 |
| /20 |
4096 |
255.255.240.0 |
16 |
| /19 |
8192 |
255.255.224.0 |
32 |
| /18 |
16384 |
255.255.192.0 |
64 |
| /17 |
32768 |
255.255.128.0 |
128 |
| /16 |
65536 |
255.255.0.0 |
256 |
|
Key
IP Addresses
Feli 64.246.40.35
NS1 64.246.41.200
NS2 64.246.41.201
google 216.239.57.99
DNS:
Front1 66.133.170.2
Front2 67.50.135.146 Front3 170.215.255.114
ELI CA: 207.173.225.3
EV1 207.218.245.135
EV2 207.218.247.135
EL1 207.69.188.185
EL2 207.69.188.186
TW1 24.92.226.13
TW2 24.92.226.174
Localnet1 207.251.201.12
Localnet2 207.251.201.11
email
pop.frontiernet.net
smtp.frontiernet.net
pop-server.rochester.rr.com
smtp-server.rochester.rr.com
mail.localnet.com
NTP
tock.usno.navy.mil |
60101-60109 lpr
|
February 28, 2008
In addition to address allocation within a subnet, we now
officially publish and adopt a global subnet allocation scheme. That
is, all client sites are centrally coordinated and registered, in a
systematic, non-overlapping manner, for the purpose of establishing
conflict-free fully/partly-meshed gateway-gateway VPNs.
This enables Bravo to establish VPNs with any subnet within our
jurisdiction without any disruptions to existing networks, either on a
permanent basis for actual operations, or temporarily for diagnostics
purposes. In other words, we now raise VPN-readiness pre-planning to the
next level, in keeping with our decade-long philosophy and policy of
treating and managing all client sites as branch offices.
Multi-location clients sites setup per our new policy will benefit as
this advanced infrastructural foresight eliminates costly and stressful
subnet retrofitting, prompted by cross-site VPN deployment.
Bravo HQ uses the following subnets in-house:
- Red: 74.34.x.x/30 (3x addresses, privately disclosed, not published)
- Green: 192.168.100.0/24
- Orange: 192.168.0.0/24 (also utilized by legacy single-location
sites)
- Purple: 10.0.0.0/24
- Black: 192.168.111.0/24
- White: 192.168.222.0/24
All client site subnets are maintained at our internal registry and not
publicly disclosed.
|
