How to Configure IPv4: Step-by-Step Setup for Your Network

Step-by-step guide on how to configure IPv4 for network setup and management. An informative image illustrating the step-by-step process of configuring IPv4 for your network.

Configuring IPv4 on your network can feel confusing when devices can’t find each other or the internet connection drops unexpectedly. The good news is that you can set IPv4 addressing step by step in about an hour, even if you’re working from a typical home or small-office router. You’ll just need access to your router or host network settings and a clear plan for the IP address, subnet mask, gateway, and DNS values to enter.

To configure IPv4, choose DHCP for automatic settings or set a static IPv4 address manually by entering the correct IP address, subnet mask, default gateway, and DNS. If you’re unsure, confirm those values from a working device or your router first so you can mirror the LAN configuration safely. This guide walks you through what each field means and exactly where to enter it on Windows, macOS, and Linux.

This is for anyone trying to get a device online (Windows/macOS/Linux) or ensure a predictable address on a LAN. It’s especially useful when DHCP is failing, you’re troubleshooting connectivity, or you need a stable IP for printers, access points, or remote access.

Decide DHCP or Static IPv4

🛒 Buy Best Network Cable Tester Now on Amazon
Comparison of DHCP and Static IPv4 configuration options for network setup

Use DHCP when you want your router to manage addressing automatically; switch to static IPv4 when you need consistent device identity or DHCP is unreliable. In practice, the “right” choice depends on whether your network environment changes frequently—especially in 2026 when many businesses still run mixed equipment and legacy gear on IPv4 LANs.

– If you want “set it and forget it,” use DHCP and let your router/server assign IP settings automatically.

– If you need consistency (or DHCP is unreliable), choose static IPv4 and manually set IP address, subnet mask, default gateway, and DNS.

– Confirm you have the right network values by checking another working device on the same network (or your router’s LAN settings).

🛒 Buy Best Wi-Fi Range Extender Now on Amazon

Before you touch IPv4 settings, lock in three facts about how IPv4 networks behave:

– According to https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml, IPv4 addresses are 32-bit (2^32 total possible addresses), which is why address planning matters on busy LANs.

– According to https://www.rfc-editor.org/rfc/rfc1918, private IPv4 ranges are defined as 10.0.0.0/8, 172.16.0.0/12, and 192.168.0.0/16—these are what most internal networks use.

– According to https://www.rfc-editor.org/rfc/rfc2131, DHCP clients and servers use UDP ports 67 (server) and 68 (client), so firewall or network filtering can break “automatic” IPv4 even when everything else looks correct.

DHCP vs static IPv4—what you gain and what you risk

Use this comparison to choose the most reliable path for IPv4 on your LAN:

🛒 Buy Best Reliable Router Now on Amazon
Feature DHCP (Automatic) Static IPv4 (Manual)
Setup speedFastSlower (manual values)
IP consistencyMay changeGuaranteed (if planned)
DHCP outages impactHigh impactLow impact
Administrative overheadLowHigher (you own mistakes)
Address conflict riskLower (managed by server)Higher (human error)
Change managementCentralized in routerDistributed across devices
Best forGeneral-purpose endpointsPrinters, appliances, fixed services
Typical troubleshooting patternCheck DHCP reachabilityValidate subnet, gateway, DNS
Scaling within a LANEasierNeeds IP plan
Day-to-day reliability (2026 reality)Good—until DHCP breaksGood—if values are correct
Best ForNetworks where IPv4 settings rarely changeDevices that must keep a stable IPv4 identity
📊 DATA

Common IPv4 LAN Subnets and Usable Host Capacity

# Suggested CIDR Subnet mask Usable hosts Address headroom
1/21255.255.248.02,046High
2/22255.255.252.01,022High
3/23255.255.254.0510Medium
4/24255.255.255.0254Medium
5/25255.255.255.128126Low
6/26255.255.255.19262Low
7/27255.255.255.22430Very Low

When you select a subnet mask for IPv4, remember: the mask determines what counts as “local” vs “remote.” That directly affects whether your device can reach the default gateway and other LAN hosts once the static IPv4 values are saved.

Configure IPv4 on Windows

On Windows, you switch the IPv4 settings from DHCP (automatic) to manual (static) and then type the correct IP address, subnet mask, default gateway, and DNS fields. As of 2026, the exact labels vary slightly between Windows versions, but the IPv4 logic and field names remain the same.

🛒 Buy Best Ethernet Switch Hub Now on Amazon

– Open the network adapter settings, then go to IPv4 and switch from Automatic (DHCP) to Manual/Static.

– Enter IP address, Subnet mask, Default gateway, and DNS server values exactly as required for your LAN.

– After saving, reconnect the network and test connectivity (e.g., confirm you can reach the gateway, then external sites).

Optional (Windows quick sanity checks)

– If the page shows an “Alternate configuration” or conflicting addresses, remove/clear old entries before re-saving.

– If you still can’t connect, verify that your static IP is in the same subnet as your gateway.

🛒 Buy Best USB to Ethernet Adapter Now on Amazon

Where to find the exact IPv4 fields

In most Windows builds, the fastest path to IPv4 settings is to open Network Connections (often via ncpa.cpl) and then open Properties for your active adapter (Wi‑Fi or Ethernet). In the adapter’s IPv4 dialog, look specifically for “Internet Protocol Version 4 (TCP/IPv4)” and set it to Use the following IP address (manual) rather than Obtain an IP address automatically (DHCP). If you’re on the newer Settings UI, the IPv4 configuration section still provides the same four essentials: IP address, subnet mask, default gateway, and DNS servers.

A practical ordering for validation (IPv4)

When IPv4 changes don’t work, I usually recommend validating in this order:

1) Confirm the device can ping or otherwise reach the default gateway (routing sanity).

2) Confirm it can resolve names using the configured DNS (DNS sanity).

3) Only then test external IP connectivity and websites (routing + DNS).

Configure IPv4 on macOS and Linux

On macOS and Linux, the key step for IPv4 is the same: set the active interface to manual IPv4 (instead of DHCP) and enter IP address, subnet mask, default gateway, and DNS consistently. In 2026, the main difference is where the interface profile lives—GUI panels on macOS, and connection profiles/config files on Linux.

– On macOS: set your connection to Manually (instead of DHCP) for IPv4, then fill in the same four essentials (IP, mask, gateway, DNS).

– On Linux: update the network settings for your active interface—commonly by editing the relevant connection profile or network config files.

– Restart or reapply the connection, then test basic routing (gateway reachability) before assuming a DNS issue.

Common gotchas by OS

– Interfaces can differ (Wi‑Fi vs Ethernet), so make sure you’re editing the correct network adapter.

– If you’re using NetworkManager (common on many distros), ensure the change applies to the active connection profile.

macOS: manual IPv4 without guesswork

On macOS, open System Settings → Network, select the active interface (Wi‑Fi or Ethernet), and change Configure IPv4 to Manually. You’ll then enter the IPv4 IP address, Subnet Mask, Router (Gateway), and DNS values. If you also set IPv4 DNS manually, confirm you’re not mixing a public resolver (like a public DNS) with an internal-only resolver used by your organization (common in corporate networks).

Linux: apply to the correct interface/profile

On Linux, “active interface” matters as much as the numbers. If you’re using NetworkManager, you typically update the settings for the active connection profile associated with Wi‑Fi or Ethernet. After saving, reapply the connection or restart the network service so the IPv4 configuration actually takes effect. If you’re using a distribution with a different network stack (for example, systems using different configuration formats), follow your distro’s recommended method for setting static IPv4 to avoid partial updates.

Test routing before DNS for IPv4

A common troubleshooting mistake is going straight to websites. If your static IPv4 subnet mask or default gateway is wrong, you might never get routing working; websites will then appear “down” even though the real issue is IPv4 routing. Testing gateway reachability first isolates whether the problem is local routing or name resolution.

What can go wrong

IPv4 misconfiguration typically breaks either local reachability (LAN scope) or remote reachability (routing and DNS). If you treat IPv4 as four independent fields, you’ll usually find the fault faster—subnet mask, gateway, address conflicts, or DNS issues.

– Wrong subnet mask: you may get an IP address assigned but still fail to reach the gateway or local devices.

– Default gateway mismatch: static IPs often fail when the gateway IP doesn’t belong to the same LAN.

– Conflicting IP addresses: if another device already uses the static IP, connectivity will be unstable or fail entirely.

– DNS confusion: you can reach local devices but not websites if DNS is incorrect (or if the gateway/DNS are internal-only).

Additional IPv4 failure modes to watch

One subtle problem is “looks right, still fails” behavior: the IP address and gateway may seem correct, but the subnet mask (or CIDR) doesn’t match what the router expects. Another frequent cause is editing IPv4 on the wrong adapter (Wi‑Fi vs Ethernet), which makes the changes correct—but irrelevant—because the system is still connected through a different interface.

Verdict / Tip

For most teams and most devices, DHCP is the pragmatic default for IPv4 because it reduces human error and centralizes changes in your router. Switch to static IPv4 when the device must be stable (printers, network appliances, access points) or when DHCP is failing and you need immediate control in 2026.

Static configuration is straightforward, but the downside is you’re responsible for correctness—especially subnet details and avoiding IP conflicts. Skip static IPv4 if you don’t know your LAN ranges yet, or if your network uses frequent readdressing where static settings become stale.

If you do need static IPv4, make it operational: document the chosen IP, mask, gateway, and DNS for each device and verify them against a working host on the same LAN before saving.

IPv4 Setup checklist (scan/save)

Use this quick list when entering IPv4 settings:

Setting What to enter Common symptom if wrong
IP address An unused IP in your LAN range “No network” / can’t reach router
Subnet mask The LAN’s subnet mask (matches gateway) Can’t reach local devices/gateway
Default gateway Router/LAN gateway IP Local works but no internet
DNS server(s) Correct DNS (often router or internal DNS) Websites don’t resolve

– [ ] Confirm IP/Subnet/ Gateway belong to the same LAN

– [ ] Ensure the chosen static IP isn’t used by another device

– [ ] Save changes, reconnect, then test gateway access first

Frequently Asked Questions

How do I configure IPv4 on Windows 10 or Windows 11?

Open Settings → Network & internet → Status → Change adapter options. Right-click your active network adapter, select Properties, then choose Internet Protocol Version 4 (TCP/IPv4) and click Properties. To set a static IPv4 configuration, select “Use the following IP address,” enter the IP address, subnet mask, and default gateway, then provide DNS server addresses if needed. Click OK to save, then run `ipconfig /all` to confirm the IPv4 settings applied correctly.

How can I configure IPv4 with a static IP on Linux?

The process depends on your Linux distribution and network manager, but the most common approach is editing network configuration files or using Netplan (Ubuntu). For Netplan, open the YAML file in `/etc/netplan/`, set `addresses`, `gateway4`, and `nameservers`, then apply changes with `sudo netplan apply`. On other distros, you may configure IPv4 in `/etc/network/interfaces` or via NetworkManager connection settings. After applying, verify with `ip addr show` and test name resolution with `ping` or `dig`.

Which IPv4 settings do I need to configure—IP address, subnet mask, default gateway, and DNS?

To configure IPv4 properly, you typically need an IP address, a subnet mask, a default gateway, and at least one DNS server. The IP address identifies the device on the local network, while the subnet mask determines which other devices are on the same network segment. The default gateway is the router IP used for reaching external networks, and DNS servers translate domain names into IP addresses. If any of these are incorrect, you may experience “no internet,” limited connectivity, or failed name resolution.

What are the best practices for setting a static IPv4 address to avoid network conflicts?

Choose an IP address that is within your router’s LAN range and outside the DHCP pool to minimize conflicts with dynamically assigned addresses. Keep subnet mask and gateway values consistent with the network you’re joining, and use reliable DNS servers (either your router or public resolvers). After configuring IPv4, test connectivity by pinging the gateway and then pinging an external IP, followed by checking domain lookups. If you see intermittent connectivity, re-check for duplicate IPs and confirm ARP tables or router logs for conflicts.

Why might my IPv4 configuration work on one network but fail on another?

Different networks often use different subnet ranges, gateways, or DNS settings, so a static IPv4 setup can break when you move to a new environment. If the subnet mask doesn’t match the local network, your device may not be able to reach the gateway, causing “network unreachable” errors. DNS settings may also be incorrect for the new network, leading to name resolution failures even when IP connectivity works. To troubleshoot, compare settings with the working network (or switch to DHCP) and verify IP/subnet/gateway alignment using `ipconfig /all` or `ip route`.

📅 Last Updated: November 17, 2026 | Topic: How to Configure IPv4 | Content verified for accuracy and freshness.


References

  1. IPv4
  2. RFC 791: Internet Protocol | RFC Editor
  3. RFC 2131: Dynamic Host Configuration Protocol | RFC Editor
  4. RFC 2132: DHCP Options and BOOTP Vendor Extensions | RFC Editor
  5. ip(8) – Linux manual page
  6. Netplan documentation
  7. https://scholar.google.com/scholar?q=configure+IPv4+static+address  Google Scholar
  8. https://scholar.google.com/scholar?q=netplan+IPv4+configuration  Google Scholar
  9. https://scholar.google.com/scholar?q=DHCPv4+configuration+options  Google Scholar

Leave a Reply

Your email address will not be published. Required fields are marked *