From charlesreid1

IP Schema

First principle: keep schema easy to change

What types of machines are you providing addresses to? Servers/workstations/printers, but now also phones, conference systems, tablets. many devices also have multiple network interfaces. a default network of 24 bits, 254 usable ip addresses, is not large enough for many situations.

multiple subnets would help to create individual networks for groups of devices (types of services). example: have servers on one subnet, printers on antoher, workstations on yet another.

the broadcast domain should also be limited. With a one-size-fits-all 24 bit network, you have a single subnet, and a single broadcast domain. Every device can communicate with every other device, with no need for routing. However, on large networks, breaking down the broadcast domain can help ensure performance. Organizing sub domains for different services keep those services from being overwhelmed.

To plan IP schema, use the ipcalc utility. This can help you understand the number of IP addresses that will be available for a given schema.

$ apt-get install ipcalc

You give it arguments of the network you are thinking about using:

$ ipcalc

ipcalc shows Hosts/Net, which is the number of allowable IP addresses that this network would give us.

The utility also shows the subnet mask that would be required, which is

ipv4 vs ipv6

insert obligatory reference to number of IP addresses running out...

ipv6 needs to be ushered in.

HOWEVER, for small, internal networks, there is absolutely no need to complicate your life with ipv6. The namespace for ipv4 running out will only affect the wider internet, and not local nor private network IP spaces.

Unless you are a networking company. Or studying for a certification.


See Template:LinuxNetworkingFlag for details.