How to switch between network profiles on Mac
Use this when the bigger problem is recurring setup management rather than one single visit.
macOS field checklist
Mac network setup checklist for client sites
Before changing a Mac network setup at a client site, collect the target IPv4 mode, subnet mask, gateway, DNS and any local alias requirements. The fastest way to lose time on customer visits is to start clicking before you know which values belong to that environment. IPChange helps once those recurring setups are saved as named templates.
The five things to confirm before you touch the adapter
- Should this Mac stay on DHCP, use a local static IP or a full static profile?
- What subnet mask belongs to that environment?
- Do you need a gateway, or is the work only local to a router or device?
- Are custom DNS servers required?
- Do you need a secondary local alias, or is one primary address enough?
If you cannot answer those five questions quickly, the setup is not ready yet. Guessing is what creates most on-site network mistakes.
Typical client-site scenarios
| Scenario | What usually matters | Common mistake |
|---|---|---|
| Router maintenance | Known local IP range, mask and sometimes no internet gateway. | Using office DNS or gateway values that do not belong to the device subnet. |
| Customer office onboarding | Stable DHCP or one specific static configuration. | Leaving old customer values on the Mac after the visit. |
| Lab or demo setup | Repeatable static values and fast rollback. | Ad-hoc manual edits with no saved baseline. |
| Mixed local device plus internet access | Main setup plus possible secondary alias. | Replacing the whole main profile when only one extra local address was needed. |
What to save after the first successful visit
Once the setup works, capture the exact values while they are still fresh. That turns one successful visit into a reusable future shortcut.
- Label the setup by client, site or device group.
- Save whether it is DHCP, local static or full static.
- Store the mask, gateway and DNS values that actually worked.
- Note if the setup belongs to Wi-Fi, Ethernet or a specific USB adapter.
- Record any local alias that was required for side access.
Where IPChange helps on repeat visits
- Named templates remove the need to remember which values belonged to which client.
- DHCP fallback remains one click away after customer work is done.
- Gateway and DNS changes stay attached to the right profile instead of drifting between visits.
- Aliases can be kept alongside the setup instead of living in ad-hoc notes.
FAQ
Do I always need a gateway when working at a client site?
No. If the work is only local to one router or device network, a gateway may be unnecessary. That is why it should be confirmed before the change.
What is the best fallback after a customer visit?
A clean DHCP profile. It gives you a fast return path to a normal office or home network state.
Should I save client setups even if I visit only occasionally?
Yes. The whole value of a checklist is that the next visit starts from a known good baseline instead of memory.
Related pages
Static IP vs DHCP on Mac
Choose the right addressing mode before you save a customer environment as a reusable template.