How to switch between network profiles on Mac
Use this when your whole environment changes and an extra address is not enough.
macOS network guide
How to add a secondary IP alias on macOS
Use a secondary IP alias on macOS when you need one extra local IPv4 address without replacing the main address on the adapter. This is useful for routers, test devices and mixed local environments where the Mac must stay reachable on more than one subnet or address. IPChange helps when you do this repeatedly and do not want to manage aliases by hand every time.
When an alias is better than changing the main IP
Replacing the primary IPv4 setting is not always the right move. In many support and lab situations, you want to keep the normal office or DHCP address and add one more local address for a device that lives on another known range.
- You need access to a router on a local fixed subnet but still want normal connectivity on the same Mac.
- You are testing a device that expects a specific neighboring IP range.
- You want to reach multiple local services without constantly reconfiguring the main adapter.
- You need a lightweight local address for a short-lived task, not a full profile replacement.
What a secondary alias actually changes
A local IPv4 alias adds another address to the same network interface. Your primary IPv4 configuration stays in place, but the Mac can also answer on the extra address. That makes aliases useful for narrow local tasks where a second address is enough.
If the entire environment changes, including gateway and DNS, a full network profile is usually the better fit. If you only need one more local address, an alias is often the cleaner option.
Typical alias use cases
| Need | Alias fit | Why |
|---|---|---|
| Reach a router on a local maintenance subnet | Good | You keep the main address and add a temporary one for the router's range. |
| Keep working internet access while talking to a local device | Good | You avoid replacing the main DHCP or office setup. |
| Switch to a completely different customer profile | Poor | You usually need gateway and DNS changes too, not only one extra address. |
| Repeat the same local test setup every week | Good | An alias can be kept as a reusable action instead of a one-off manual change. |
What often goes wrong
- Picking an alias that conflicts with an address already in use on that subnet.
- Using an alias when the real need is a full profile with different gateway and DNS.
- Forgetting which adapter the alias belongs to after changing docks, Ethernet adapters or Wi-Fi state.
- Leaving too many ad-hoc addresses on the Mac without a clear label or purpose.
Where IPChange helps
IPChange is useful when alias work is part of a repeatable workflow rather than a rare command-line task.
- Turn local aliases on and off from the same app that manages primary IPv4 templates.
- Keep aliases grouped with the setups they belong to.
- Reduce mistakes when switching between router work, lab devices and office networks.
- Combine saved primary IPv4 profiles with alias actions instead of rebuilding them manually.
FAQ
Do I need to replace DHCP to use a local alias?
No. That is one of the main reasons to use an alias. You keep the main address and add another one for a specific local task.
Is an alias the same as a full network profile?
No. An alias only solves the extra address part. If you need a different gateway, DNS or complete client environment, use a full profile instead.
Who benefits most from aliases?
Consultants, support engineers, lab users and anyone who regularly connects to devices on known local subnets.
Related pages
How to change IP address on macOS
Direct steps for DHCP and manual primary IPv4 changes in macOS.