In yesterday’s article I covered the basics of Ethernet cabling, hubs and switches.

In today’s article I’ll cover the essential Ethernet basics of IP Addressing, including Host IDs, Subnet Masks, Default Gateways, and Reserved Addresses.

Ethernet IPv4 Address and Subnet Mask Basics:

Those familiar with bits and bytes will have an advantage in this discussion as the standard IPv4 Address and Subnet Mask are each made up of four bytes (also known as octets.)

And while it’s true the networking industry is moving to IPv6 (represented by Eight groups of Four hexadecimal digits, aka Eight 16 bit groups) IPv4 is still the most commonly used scheme for home, office, and controls networks.

MicroLogix-1400-LCD-ENETcfg-Menu-IP-Static-SN-Entry-1The first thing to understand about IPv4 Addresses is that each address contains two pieces of information, which are identified using a Subnet Mask.

In simple terms, the high bits represent the “Subnet” aka (“NetID” or network number) and the remaining low bits represent the “Host ID” (aka “host identifier” or device address.)

To separate the Host ID from the Subnet, we simply perform a “Bitwise AND” between the IP Address and Subnet Mask.

If, for example, you had an IP Address of and Subnet Mask of, the result of a “Bitwise AND” of the two reveals the Subnet is 192.168.1, and the Host ID is 5.

How do I know that?

For those unfamiliar with Bit Masking, I like to compare it “Painting Masks” you see road crews use, or the “Stencils” used to make signs.

Each insure only a certain area is painted, which is similar to a Bit Mask which insures only certain bits are passed through while others are filtered out.

For clarity’s sake, let me show how a “Bitwise AND” works by laying out an IP Address and Subnet Mask bit by bit.

Below, you’ll see I’ve converted our above example addresses (IP Address of, Subnet Mask of into binary format:

Our IP Address in binary equals:    11000000-10101000-00000001-00000101
Our Subnet Mask in binary equals: 11111111-11111111-11111111-00000000

When we Mask (aka “Bitwise AND”) our IP Address using our Subnet Mask, we only pass through the bits of the IP Address for which the Subnet Mask has a 1:

11000000 10101000 000000000000101 = = IP Address
11111111 11111111  11111111 00000000 = = Subnet Mask
11000000 10101000 000000000000000 = = Subnet

And whatever bits the Subnet Mask does not pass is our Host ID

11000000 10101000 000000000000101 = = IP Address
11111111 11111111  11111111 00000000 = =  Subnet Mask
00000000-00000000-00000000-00000101 = =  Host ID

So as seen above, an IP Address of and Subnet Mask of results in a Subnet of 192.168.1, and a Host ID of 5.

For more about Bitwise ANDing see this article HERE.

You’ll probably notice that with a Subnet Mask of, also known as a Class C mask, the Subnet takes up the first three bytes (or octets) of the IP Address.

This only leaves one byte for the Host ID, which in turn limits our Host ID to a range of 0 to 255, for a total of 256 available Host IDs (before considering the reserved addresses we’ll cover later.)

Only having 256 Host IDs available for network devices is typically not a problem in a home or small office, but it’s obviously not enough for large facilities or networks.

To address this, we could simply use Subnet Mask of (Class B,) which would leave us potentially more than 65,000 (256×256) Host IDs.

If you’d like to learn more about Subnet Masks and Classes, check out this article HERE.

Why Subnets are Important

Most of us know that each device on our Ethernet network needs a unique IP Addess.

But many don’t understand that Ethernet devices can only communicate with other Ethernet devices on the same Subnet (unless there is a Router bridging Subnets – more on that later.)

Put another way, if you have a Switch and two wired Ethernet devices, for the two devices to communicate they (1) not only need to be wired to the Switch, they (2) also need to logically be on the same Subnet.

For example, let’s say we have two devices wired to a single Switch, and give one an IP Address of, and the other an IP Address of And we give both of them a Subnet Mask of

In that example, the two devices would be able to communicate with each other because they both sit on the same 192.168.1 Subnet, as shown below:

IP Address AND Subnet Mask    = Subnet AND   = 192.168.1 AND   = 192.168.1

That said, if I changed the second device’s IP Address to, it would no longer be able to communicate with the first device (and vice versa) because, even while they are physically connected to the same switch, logically they are now on two different Subnets (192.168.1 vs. 192.168.2) as shown below:

IP Address AND Subnet Mask    = Subnet AND   = 192.168.1 AND   = 192.168.2

But, if I then changed both their Subnet Masks to, they would be able to communicate again as they would again be on Subnet again, as shown below:

IP Address AND Subnet Mask  = Subnet AND    = 192.168 AND    = 192.168

What if my devices are on different Subnets?

If you have devices on different Subnets that need communicate with each other, you’re going to need to add a Router (aka Bridge, Gateway) to your system.

Simply put, a Router “routes” traffic between different Subnets.

But even with a Router correctly setup AND configured to bridge two (or more) networks, there is still one more thing you must do to insure your two devices can communicate with each other!

That is that both devices also need to have the Router’s address set as their Default Gateway address.

This basically tells the device where to send messages to when the message’s address is not on the same Subnet.

Put another way, in the example where I had one device set to /, and the other device set to /, each Device knew it could not directly message the other because they were logically on different Subnets.

But if I had installed and configured a Router to be connected to each Subnet, and I set each devices Default Gateway as the Router’s local address, then a message sent from one device to the other should be bridged between the two subnets by the Router.

However, without a correctly setup and configured Router to bridge those two Subnets, or without correctly inputting the Router’s address in each device’s “Default Gateway” setting, the two devices would not be able to communicate.

For more about Routers, check out this article HERE.

Reserved Subnets and Host IDs

Now that we’ve covered IP Addresses, Subnet Masks, and Default Gateways, I want to wrap up this article by talking about reserved Subnets and Addresses.

With IPv4 there are three ranges of IP Addresses that have been reserved for private use.

Private Use means that no devices directly connected to the Internet will ever use these address ranges, thus making them available for use in internal private networks (aka Intranets) in homes and businesses.

These ranges are:       –       (1 Class A network)   –     (16 Class B networks) –  (256 Class C networks)

Some other reserved ranges also include:  –

This range is used when no server is available to Boot-P or DHCP clients requesting an address.

When no address is received, client devices supporting auto-assigned addresses will randomly pick an IP Address from this range so it can communicate with other devices in the same situation.     –

This range is reserved for local hosts, aka loopback addresses, and you can typically ping your own computer using an address of

For more information about Private Networks, check out this article HERE.

Reserved Host IDs

As far as reserved Host IDs, the below list can be used as rule of thumb (especially with Class C networks)

x.x.x.0     The network address/represents the network. Should Not be assigned to devices
x.x.x.1     Typically used for the Subnets Router / Bridge / Gateway device
x.x.x.254 Many reserve this address for Routers or Switches which need their own Host ID
x.x.x.255 The network broadcast address. Should Not be assigned to devices

Well, those are what I see as the most important Ethernet Addressing Basics everyone should know.

If you think I should have added something else, or have any questions, comments, or suggestions, please feel free to post the by clicking on the “Click here to post a comment or question” link below.

You can also check out our other Ethernet articles using the links below my signature (coming soon.)

Until next time, Peace ✌️ 

Shawn M Tierney
Technology Enthusiast & Content Creator

Have a question? Join my community of automation professionals and take part in the discussion! You'll also find my PLC, HMI, and SCADA courses at

If you found this content helpful, consider buying me a coffee here.

Shawn Tierney



Please enter your comment!
Please enter your name here