What Is an IP Address? A Guide for Business Networks

A shared printer stops responding after a reboot. It is powered on and connected, but print jobs go nowhere. Open the client list in the controller, and the reason is in the number beside it. The printer came back with a different address, and computers set up to print to the old address are still sending jobs there.

That number is the printer's IP address. So what is an IP address? An Internet Protocol (IP) address is a numerical identifier assigned to a device's network interface. It tells other devices and services where to send data, so a laptop, printer, or access point can be found and reached on a local network or across the internet.

This guide explains how to read an IP address, what each part means, which business devices benefit from consistent addresses, and when IPv6 matters.

Key Takeaways

• An IP address is a numerical identifier the network assigns to a device's interface, so other devices and services know where to send its traffic.
• Each IPv4 address is 32 bits written as 4 octets from 0 to 255, and a /24 suffix marks where the network portion ends.
• Devices inside an office use private addresses from reserved ranges, while the gateway translates their traffic to a shared public address.
• Gateways, controllers, access points, cameras, and printers need consistent addresses through reservations or static settings, while laptops and phones can stay dynamic.
• As a network grows, giving staff, guest, and camera devices their own subnets keeps addressing organized, and traffic rules control what crosses between them.

What Is an IP Address?

An IP address is a numerical identifier assigned to a device's network interface on a network that uses the Internet Protocol (IP), the standard rules for addressing and delivering data. It makes the device findable, so other devices and services know where to send traffic meant for it, whether they are on the same local network or across the internet.

Every IP packet carries a source address and a destination address. The addresses identify where traffic came from and where it is going, while routing determines the path it takes to get there.

On a small business network, laptops, phones, access points, managed switches, IP cameras, point-of-sale (POS) terminals, printers, and controllers commonly use IP addresses. A device without a usable IP configuration cannot communicate normally with other IP networks or reach services such as file shares, cloud applications, or the internet. Infrastructure devices like access points and controllers also benefit from consistent addresses for management, which is where static and reserved addresses come in. When a device appears in a client list with no address, or with an unexpected one, that is often the first clue to a configuration or connectivity problem.

In an IP address vs. MAC address comparison, the MAC (media access control) address identifies a network interface at the local network level and is typically assigned by the manufacturer, although it can be changed or randomized. The IP address is assigned by the network, either manually by an administrator or automatically, and it can change when the device joins a different network or receives a new assignment.

How Do IP Addresses Work?

IP addresses work by giving every device a known destination, so traffic can be delivered on the local network or routed to other networks, including the internet. For most client devices, the process starts automatically the moment the device connects.

The device requests its settings using the Dynamic Host Configuration Protocol (DHCP). A DHCP server, often running on the gateway, assigns an address from a configured pool along with a lease that sets how long the assignment is valid. The device attempts to renew its lease before it expires, and DHCP servers generally try to give a returning device the same address.

A DHCP assignment typically includes four important settings:

• IP address: Identifies the device's network interface, such as 192.168.10.112
• Subnet mask: Defines which addresses are on the same subnet, such as 255.255.255.0
• Default gateway: The address of the device, usually the gateway, that forwards traffic bound for other networks, such as 192.168.10.1
• DNS server: Uses the Domain Name System (DNS) to resolve domain names and hostnames to IP addresses

With those settings in place, the device checks whether the destination is on the same subnet. If it is, the device sends traffic directly; if not, it sends traffic to the default gateway, which routes it toward the destination. For internet-bound IPv4 traffic, the gateway typically uses Network Address Translation (NAT) to translate the device's private source address to a public address. It then uses that translation to return responses to the correct internal device.

This is why "the network is down" is not always a network-wide problem. A device can show an active Wi-Fi or Ethernet connection but fail to obtain or renew its expected IP configuration. Many operating systems then automatically assign the device an IPv4 link-local address in 169.254.0.0/16, a range intended only for communication on the local link, not for routed internet access. Seeing a 169.254 address usually means the device did not get its expected configuration, often because DHCP was unavailable or failed.

IP Address Format: How to Read the Four Octets

An IPv4 address is 32 bits long, written as four numbers from 0 to 255 separated by periods, a format called dotted-decimal notation. Each of the four numbers is an octet, meaning it represents 8 bits of the address. Eight bits can hold 256 values, which is why an octet ranges from 0 to 255.

So how many bits long is an IP address? An IPv4 address, still widely used on business local networks, is 32 bits. An IPv6 address is 128 bits, which is covered in its own section below. For IPv4, every IP address type follows the same four-octet format, whether the address is public or private, static or dynamic.

Reading an IPv4 address in practice starts with the first one or two octets. An address in 10.x.x.x, 192.168.x.x, or 172.16.x.x through 172.31.x.x is private, meaning it is intended for use within private networks rather than as a publicly routed address.

Addresses are often written with a suffix, as in 192.168.10.42/24, which is Classless Inter-Domain Routing (CIDR) notation: /24 means the first 24 bits identify the network.

Network Portion vs. Host Portion

Every IPv4 address has a network portion and a host portion, and the subnet mask or CIDR suffix determines where one ends and the other begins. With a /24, the first 24 bits, or the first three octets, form the network portion, and the remaining 8 bits form the host portion. The equivalent subnet mask is 255.255.255.0.

That is why 192.168.10.42 and 192.168.10.99 are on the same subnet: their first three octets match, so the devices can normally communicate directly. 192.168.20.42 has a different third octet, which places it on a different subnet, so traffic between them must pass through a Layer 3 device such as a gateway or Layer 3 switch. A /24 subnet contains 256 addresses, and 254 are usable for devices because the first is reserved as the network address and the last as the broadcast address.

IP Address Examples: What One Actually Looks Like

A typical IP address example on a small business network is 192.168.10.20, assigned here to an access point, where 192.168.10 is the network portion and 20 is the host portion. In practice, what an IP address looks like matters less than what it is assigned to and how it got there.

The table below shows how addresses might be laid out on a single-site business network using the 192.168.10.0/24 range. The last row shows an example of the public address an internet service provider (ISP) assigns.

In this example, infrastructure sits at the low end of the range, reserved devices occupy a defined block, and everyday client devices draw from a DHCP pool higher up. Grouping addresses this way makes a client list readable at a glance, because the address itself hints at what the device is. The last row is the exception: the public address belongs to the gateway's internet-facing interface and is shared by every device in the office, which the next section explains.

Public vs. Private IP Addresses

A public IP address is globally unique and routable across the internet, while a private IP address is used only within a private network. In a typical IPv4 business network using NAT, the gateway holds one or more public addresses, and devices on the internal network use private addresses.

Private addresses come from three ranges reserved for internal use and defined in RFC 1918, a Request for Comments (RFC) document from the Internet Engineering Task Force (IETF):

• 10.0.0.0 to 10.255.255.255 (10.0.0.0/8)
• 172.16.0.0 to 172.31.255.255 (172.16.0.0/12)
• 192.168.0.0 to 192.168.255.255 (192.168.0.0/16)

Any organization can use these ranges without registering them, which is why the same private addresses, such as 192.168.1.10, appear on countless separate networks. NAT connects the two sides. When a device with a private address sends traffic to the internet, the gateway replaces its private source address with the public address, typically changing the source port as well. It tracks each translation so replies return to the correct device.

This also answers a common question: does everyone in my house have the same IP address? With a typical IPv4 setup, yes, because websites see the one public address shared at the gateway. Inside the network, no, because each device has its own private IPv4 address. The business version of the question is why a whole office appears as one address in a website's logs or a vendor's allowlist, and NAT is the reason.

Static vs. Dynamic IP Addresses

A static IP address stays the same until an administrator changes it, while a dynamic IP address is assigned automatically by DHCP and can change over time. Dynamic addressing is the default for most devices because it requires no manual setup and lets the DHCP server reuse addresses when leases end.

The difference matters most when something needs to be found. A laptop that browses the web does not care whether its address changes overnight. A printer that 30 staff members reach by IP address, or a camera that a recorder connects to by IP address, becomes unreachable at that address if its IP changes.

Which Devices Need a Static Address?

Any device that other systems or users must reliably reach at a predictable IP address should have a consistent address. Common examples include:

• Gateway
• Controller
• Access points
• IP cameras
• Printers
• Network-attached storage (NAS)
• POS terminals
• Any device that is the target of port forwarding or is accessed directly by IP address

This consistency can come from a DHCP reservation or a manually configured static address, depending on the deployment. Leave staff laptops, phones, tablets, and guest devices on regular DHCP when nothing depends on finding them at a fixed address.

DHCP Reservations vs. Setting It on the Device

A DHCP reservation tells the DHCP server to give a specific device the same address every time, typically matched to the device's MAC address. The device still uses DHCP, but the result is predictable, and every assignment stays recorded in one place: the DHCP server's configuration.

The alternative is to set a static IP address on the device itself by entering the IP address, subnet mask, default gateway, and DNS server in its network settings. That works, but it creates a second list of addresses that lives outside the DHCP server. The address should also be excluded from the DHCP pool so the server cannot assign it to another device later.

If the server does assign it, the result is an IP address conflict, which can prevent one or both devices from communicating reliably. Centralized address planning helps prevent these conflicts. When an Omada gateway is the network's DHCP server, reservations can be configured from the Omada controller, which keeps those assignments visible alongside the rest of the network's configuration.

IPv4 vs. IPv6

IPv4 uses 32-bit addresses written as four decimal numbers, while IPv6 uses 128-bit addresses written as eight groups of hexadecimal digits. This gives IPv6 a vastly larger address space. The IETF's IPv6 specification defines it as the successor to IPv4, designed to support far more addressable devices.

IPv6 exists because IPv4's 32-bit address space holds about 4.3 billion possible addresses, not enough to give every internet-connected device a unique public IPv4 address. The global pool of unallocated IPv4 addresses was fully depleted in February 2011. That day, the Internet Assigned Numbers Authority (IANA) allocated its final blocks to the five regional registries that distribute addresses worldwide. Private addressing and NAT have extended IPv4's life inside business networks, but they do not create new public addresses.

For most small businesses, IPv6 can be planned alongside existing IPv4 rather than treated as an immediate replacement. Confirm whether your gateway and ISP support IPv6, then determine whether a dual-stack configuration, which runs IPv4 and IPv6 side by side, is appropriate. If you enable IPv6, review your gateway's firewall rules to confirm which inbound traffic they allow, since devices may receive globally routable addresses.

Managing IP Addresses on a Growing Business Network

IP address management on a growing network means dividing addresses into planned segments, so each group of devices gets its own address range, traffic rules, and, where needed, a DHCP scope. The flat network that served six devices starts to strain as the business adds staff, guest Wi-Fi, cameras, and POS terminals.

On a flat network, every device shares one address range and one broadcast domain. Guest phones, security cameras, and payment terminals all sit in the same space, which makes troubleshooting slower and limits how precisely you can control traffic between them.

Virtual local area networks (VLANs) create separate Layer 2 segments, while subnets provide the IP addressing for those segments. Staff devices might use 192.168.10.0/24, guest Wi-Fi 192.168.20.0/24, and cameras 192.168.30.0/24, each on its own VLAN. A separate DHCP scope for each client VLAN keeps address assignment organized, because a device's address immediately tells you which segment it belongs to. The Omada VLAN configuration guide includes instructions for setting this up step by step.

Separating segments does not, by itself, control what crosses between them. Traffic between subnets has to be routed, and switch access control lists (ACLs) or gateway firewall rules then decide which of that traffic is allowed. For example, rules can let staff reach a printer VLAN while blocking guests entirely. Where that routing happens, on the gateway or on a switch that supports routing, is a design choice covered in this comparison of Layer 2+ and Layer 3 switches.

Infrastructure devices follow the same planning logic. Omada access points can use DHCP reservations to maintain consistent management addresses as the network expands. Select Omada managed switches support DHCP snooping, which can block unauthorized DHCP servers from handing out addresses. With the controller showing clients alongside their assigned IP addresses, the address plan stays visible as the device count climbs.

Frequently Asked Questions

How can I find my IP address?

On Windows, open Command Prompt and type ipconfig. On a Mac, open System Settings, select Network, and view the details for your active connection. On a phone, check the details for the connected Wi-Fi network. These usually show a private IP address. To see your public address, visit any "what is my IP" site. On a business network, the controller's client list can show connected devices and their IP addresses.

Is your IP address just your Wi-Fi?

No. Your IP address belongs to your device on the network, not to the Wi-Fi itself. Wi-Fi is simply how the device connects. A device gets a new address when it moves between networks, such as from the office to a coffee shop. On a single managed network, it can keep the same address while roaming between access points on the same network segment.

Does everyone in my office have the same IP address?

Yes and no. To websites and online services, everyone in your office usually appears to share one public IP address, because the gateway uses NAT to translate traffic. Inside the office, each device has its own private IP address. That is why vendor allowlists and website logs often show a single address for your entire site.

Can someone find you through your IP address?

Not your exact location. A public IP address can reveal your ISP and an approximate location, but geolocation can't pinpoint a street address. Your ISP can generally link a public address to a subscriber at a given time, usually in response to a legal request. On a typical NAT network, outside devices generally can't start connections to internal devices without a rule such as port forwarding.

Planning Your Network's Address Scheme

An IP address is how every device on your network gets found. The decision that matters most is which devices need a consistent address, and making that call early keeps printers, cameras, and access points reachable as the network grows.

Once addressing makes sense, putting VLAN segmentation into practice is the natural next step, since it builds directly on subnets and DHCP scopes. To see how switching fits into a segmented network, explore Omada managed switches and compare which models support the VLAN, ACL, and DHCP features a multi-segment network needs.