This page is an introduction to Networks. We don’t need to know everything about it, but often face it in our work. In this guide I will give you a basic understanding of networks, IP addresses, VLANs, Segmenting etcetera. Basically everything you need to understand the process, and hopefully even more than that.


Table of Contents

📖 Estimated read time: 7 minutes

🔄 Page last updated on: November 19, 2025

Requirements

  • Some basic networking knowledge
  • Some basic subnetting knowledge
  • Around 20 minutes of your time

Introduction to Networking

Networking is the process of connecting devices to share data and resources. It allows communication between users over local or global distances. Networks can range from small home setups to large corporate infrastructures. Key components include routers, switches, and protocols that manage data traffic. Effective networking ensures reliable, secure, and efficient information exchange. As technology advances, networking plays a critical role in enabling digital communication worldwide.

Logically this means that every device will have an IP address and this can be used to communicate with other devices. This can look like the diagram below:

This shows a simple network with 8 devices, all connected to each other. In practice, the circle will represent the infrastructure; the Routers and Switches.


Routers

In every network, we have a device that plays the “Router” role. This is basically connecting different networks to each other. In most bigger networks, this can be the firewall.

On Azure, the routing and switching part is done with creating a virtual network. This means that this is all managed and you only select the network you want to connect with.

Switches

Switches are the distribution part of a network. These are literally like power strips but then for networks. One cable goes in (called the “Uplink)”, and all other cables are going out of the switch (called “Downlinks)”. Connecting a device to a downlink of a switch gives access to the network.

Routers and Switches can seem the same as terms but they are different in a particular way. Routers connects our devices to different networks, and Switches redistribute those networks.


IP addressing

IP addresses are needed on a network for every device to know where to deliver a package. You can compare this like in a real world city, where every street has a name and every house has a house number. IP addressing works kind of the same way, but translated in a way so computers can also work with it.

We have two types/versions of IP addresses:

IP address are built in this way:

The first part represents the “Network ID”, which is a static part and will remain till configured different. The last part represents the “Host ID” which is a number that is different for every host. The Network ID can be compared to a real life Street and the Host ID is the house number.

Class A, Class B and Class C networks

Now this is a basic explaination of a Class C address, where we only use the last number. We have 3 classes that we use in networking:

  • Class A (255.0.0.0 to 255.254.0.0)
  • Class B (255.255.0.0 to 255.255.254.0)
  • Class C (255.255.255.0 to 255.255.255.255)

Now this tells us how many devices we can use in our network:

  • In Class A, we can connect millions of devices because there are many available addresses
  • In Class B, we can connect up to 65.000 devices
  • In Class C, we can connect up to 254 devices

The most important here is the Subnet mask which tells devices on what part of the IP addressing scheme they are.

Introduction to Subnet masks

You must have seen them in your daily life of being an IT guy, Subnet masks. This is a number like:

  • 255.255.255.0 or /24
  • 255.255.0.0 or /16

This number decides how many hosts we can use in our network. The more zeros in the subnet mask, the more host addresses are available. For example, /24 (255.255.255.0) allows 254 usable hosts, while /16 (255.255.0.0) allows 65.534 usable hosts. Subnet masks help divide networks into smaller parts, making management and security easier. A best practice is always to have your subnets as small as possible for networks or VLANs, but the bottom line is mostly /24.

A smaller subnet is basically a higher performance. Because some requests, like broadcasts are sent to every address. This process is faster to 254 addresses than to 65.000 addresses.

Tip: use my Subnet calculator to calculate your networks: https://subnet.justinverstijnen.nl/

Deep dive into IP addresses

IPv4 addresses, like 172.16.254.1, are decimal representations of four 8-bit binary blocks, known as octets. Each octet ranges from 0 to 255, making every IPv4 address 32 bits in total.

The IP address 172.16.254.1 can be represented in binary format like shown in the picture below:

So an IP address is basically a human readable way of how the devices work under the hood. All based on 0’s and 1’s.


Subnets, Segmentation and VLANs

Subnetting is a technique used in networking to divide a larger IP network into smaller, more manageable subnetworks (subnets). It helps optimize IP address allocation, improve network performance, and enhance security by segmenting traffic.

Each subnet operates as an independent network while still being part of the larger network. By using subnetting, organizations can efficiently manage IP address space, reduce network congestion, and implement better access control.

Subnetting is achieved by modifying the subnet mask, which determines how many bits are used for the network and how many for the host portion of an IP address. Understanding subnetting is essential for network engineers and administrators to design scalable and efficient network infrastructures.

In Azure, we do this by creating a virtual network which has an address space (for example: 10.0.0.0/16) and we can build our subnets in that space (10.0.0.0/24, 10.0.1.0/24, 10.0.2.0/24 etc.). I have done this for demonstration in the picture below:

When using routers and switches, we can segment our network in different, Virtual networks which are called VLANs. This can help us by dividing devices into different isolated networks without the need of having seperate physical networks.

For designing VLANs you have to calculate the subnet sizes and ip address schemes. I have a tool available for doing this:

Tips for understandable network addressing

So when designing networks, you will never know how long you are gonna use it. My advice is to always have a good networking plan and document your plan for future use and expansion.

I have some tips for designing networks that work well:

  • Always use as small as possible networks, with /24 as bottom line
  • Segment devices with good logic (Servers to servers, Guest to guest etc.)
  • Link your VLAN IDs to your Network IDs
    • For example;
      • VLAN ID 10 to 10.0.10.0/24
      • VLAN ID 20 to 10.0.20.0/24
      • VLAN ID 99 to 10.0.99.0/24

Complete overview of Subnet masks and usable addresses

To have a cheat sheet of subnet masks, I have created a complete table of all usable Subnet masks including how much addresses you can assign in those networks:

PrefixSubnet maskUsable addresses
Supernets (ISPs)
/00.0.0.0Used as wildcard
/1128.0.0.02,147,483,646
/2192.0.0.01,073,741,822
/3224.0.0.0536,870,910
/4240.0.0.0268,435,454
/5248.0.0.0134,217,726
/6252.0.0.067,108,862
/7254.0.0.033,554,430
Class A networks
/8255.0.0.016,777,214
/9255.128.0.08,388,606
/10255.192.0.04,194,302
/11255.224.0.02,097,150
/12255.240.0.01,048,574
/13255.248.0.0524,286
/14255.252.0.0262,142
/15255.254.0.0131,070
Class B networks
/16255.255.0.065,534
/17255.255.128.032,766
/18255.255.192.016,382
/19255.255.224.08,190
/20255.255.240.04,094
/21255.255.248.02,046
/22255.255.252.01,022
/23255.255.254.0510
Class C networks
/24255.255.255.0254
/25255.255.255.128126
/26255.255.255.19262
/27255.255.255.22430
/28255.255.255.24014
/29255.255.255.2486
/30255.255.255.2522
/31255.255.255.2540
/32255.255.255.2550

Comma’s used in Usable addresses to not be confused with IP addresses 😉


Summary

I hope I gave you a great basic understanding of how networks work and the fundamentals to use networking in Azure. Its part of our jobs and not very easy to start out with.

Thank you for reading my guide and i hope it was helpful.



End of the page 🎉

You have reached the end of the page. You can select a category, share this post on X, LinkedIn and Reddit or return to the blog posts collection page. Thank you for visiting this post.

If you think something is wrong with this post or you want to know more, you can send me a message to one of my social profiles at: https://justinverstijnen.nl/about/

Go back to Blog

The terms and conditions apply to this post.

Page visitors: No page-counter data available yet.
Categories: Networking