IPv4 Network Design

DESIGNING A SCALABLE IPV4 ADDRESSING SCHEME

IPv4 Overview
• 32 bit address field 00000000.00000000.00000000.00000000
• 4 octets |--8 bits--|
|--------------------32 bits--------------------|

• Comprised of a network identifier and host identifier

• Definition of host and network portion defined by mask

11111111.11111111.11111111.00000000
|---------24 bits---------|
|---------network--------||--hosts--|
Subnet Masks
• Can be expressed in dotted decimal or CIDR 11111111.11111111.11111111.00000000
• Often referred to as a prefix length |---------24 bits---------|
|---------network--------||--hosts--|

172.16.10.5/21

10101100.00010000.00001010.00000101
11111111.11111111.11111000.00000000 11111111.11111111.11111000.00000000
|--------21 bits-------|
10101100.00010000.00001000.00000000 |------- network------||---- hosts----|

172.16.8.0/21
Private vs. Public Addressing
• Private addresses are not routable on the internet
• They do not uniquely identify a device on the internet
• 3 private address spaces

Class A: 10.0.0.0 - One /8 network

Class B: 172.16.0.0 – 172.31.255.255 - Sixteen /12 networks

Class C: 192.168.0.0 – 192.168.255.255 - Two hundred fifty six /24 networks

Network Address Translation
• 3 Primary flavors:
• Stateless - Static NAT
• Stateful - Dynamic NAT
• Stateful - PAT/NAT Overload
Stateful
• Router keeps a state table
• Firewalls allow return traffic
• PAT assigns ports to clients in the table
• Dynamic NAT assigns a client to a public IP
• Terminology
• Inside local – host’s IP
• Inside Global – Router’s public IP
• Outside local* – remote server’s IP
• Outside Global - remote server’s public IP
*As seen by inside network
Stateless
• No state table
• Same translation each time
IPv4 Design
Best practice to separate data and VOIP networks
• Use overlay networks to give more address space
10.1.1.0/24 - Building 1 floor 1 Data
10.1.2.0/24 - Building 1 floor 2 Data • Come up with a repeatable addressing standard.
10.2.1.0/24 - Building 2 floor 2 Data • Design with summarization in mind
. • Use contiguous networks
.
.
172.16.1.0/24 - Building 1 floor 1 VOIP
172.16.2.0/24 - Building 1 floor 2 VOIP
172.17.1.0/24 - Building 2 floor 1 VOIP
IPv4 Design Cont.
• The primary goal of a well planned address design is to allow for summarization

Images courtesy of Ciscopress.com

IPv4 Design Cont.
• Summarization also allows for easier identification
• Comes more naturally with adherence to an addressing plan

Images courtesy of Ciscopress.com

Big Picture Planning: Campus
Simple Addressing: Role-based addressing

10.x.y.0/24
• x = wiring closet
• y = function of VLAN

Not-so-simple addressing: Bit splitting

172.0001xxxx.xxxxxxxx.xxhhhhhh

• x = subnet
• h = host ID for 62 host subnet

Images courtesy of Ciscopress.com

Case Study
• Sample VLANs/subnets for a retail store network

VLAN 10 – 10.0.1.0/24 (Data)

VLAN 20 – 10.1.1.0/24 (Voice)
VLAN 30 – 10.2.1.0/24 (Internal Wifi)
VLAN 40 – 10.3.1.0/24 (Servers/printers)
VLAN 50 – 172.17.0.0/29 (Exit)
VLAN 60 – 172.16.0.0/22 (Public Wifi)
VLAN 70 – 10.70.1.0/24 (management)

Images courtesy of theverge.com

Q&A
For a VLAN that requires 60 hosts, which subnet is most efficient?

A. 10.10.10.0/26
B. 192.168.15.0/24
C. 10.0.0.0/20
D. 172.31.17.0/27
Q&A
Which IPv4 addressing technique can be used with proper address planning to reduce the
Number of entries in a routing table?

A. Translation
B. Filtering
C. Summarization
D. Tunneling