- These Sony headphones deliver premium sound and comfort - without the premium price
- The LG soundbar I prefer for my home theater slaps with immersive audio - and it's not the newest model
- Samsung's new flagship laptop rivals the MacBook Pro, and it's not just because of the display
- Email marketing is back and big social is panicking - everything you need to know
- Revisiting Docker Hub Policies: Prioritizing Developer Experience | Docker
Subnetting: Brushing up on the fundamentals

In the IT world, specifically in networking, there aren’t many aspects that are as much of an enigma as subnetting—the act of creating subnetworks.
Subnets are logical divisions of an existing network that are defined by both class of IP address and the subnet mask. Often, consultants provide network design services to budding businesses to help establish a network that fits their needs at the time. But as the business grows or its needs change there may come a time when the initial network structure no longer works.
I’m currently working on a project that fits that description to a tee. The network was conceived by consultants when there were not as many devices and users to accommodate. As the needs of the business grew, it became painfully obvious that a single /24 subnet that accommodates up to 254 hosts wasn’t enough anymore. So I’m building out a new network structure that can accommodate all of the devices we currently have, separated by types of devices, and with room for growth.