Physical path
Redacted ISP-to-client sketch with device names, ports, and cables.
Use this flow when the network path is unclear or multiple boxes appear to be doing the same job. The first goal is a redacted topology, not a reset or configuration change.
The modem, gateway, router, firewall, switch, mesh node, or access point roles are unclear. One all-in-one box may provide several roles, while a second router can accidentally create duplicate DHCP or NAT.
Redacted ISP-to-client sketch with device names, ports, and cables.
Default gateway, DHCP server, and Wi-Fi owner from one client.
Model and intended role for each modem, gateway, router, switch, AP, or mesh node.
One ISP gateway may already combine modem, router, switch, firewall, and Wi-Fi.
A second router or mesh node may be assigning addresses or performing NAT.
A switch or access point may be connected to the wrong gateway side or missing its uplink.
The network may work, but the system map is stale or undocumented.
Create a redacted ISP-to-client path sketch and label each physical cable.
Confirm the client default gateway, DHCP server, and Wi-Fi owner.
Compare observed roles with the intended design and note duplicate DHCP/NAT evidence.
Document one reversible change or hand off managed-network role changes.
Which device connects to the ISP handoff, and which device provides the client default gateway and DHCP?
Escalate before changing DHCP, NAT, VLAN, firewall, cabling, or managed access-point roles without a preserved baseline and rollback.
This vendor-neutral flow uses Cisco guidance that distinguishes routers, switches, access points, and wireless routers while recognizing that modern devices can combine roles.
Record the gateway, switch, access points, clients, and relationships privately.
Open private discoveryThe support assistant can ask for a redacted topology without accepting credentials.
Open support chat