Symptoms
Devices alternate between working and no internet when a second router is connected.
Use the following observations to establish that this is the specific failure described here, rather than an unrelated outage or different account:
- Failing behavior: Devices alternate between working and no internet when a second router is connected.
- Comparison to run: Compare DHCP lease default gateway on two affected clients and identify both DHCP servers.
- Pass condition: All test clients obtain the same intended gateway with stable internet access.
Why It Happens
A local Wi-Fi icon and a registered optical link are different observations. First determine whether the interruption begins at optical registration, the Ethernet handoff, routing or the application using the connection.
Treat these as competing hypotheses, not confirmed diagnoses. Their implications are different:
- ISP gateway and personal router both serve DHCP — investigate this first only if the local state or controlled comparison supports it.
- Access point left in router mode — a second layer that may survive a simple restart and requires a targeted check.
- Old extender advertises invalid gateway — investigate when the first two paths do not account for the observed behavior.
Before Making Changes
Keep management access before changing router mode and save prior configuration. Fiber access is a chain: the optical terminal, WAN negotiation, routing and DNS can fail independently. A green Wi-Fi light proves only the local radio is active, not that the provider link is usable. Write down the working configuration and, if available, export settings or create a test-only copy before changing account permissions, routes or file locations.
Make one change at a time, note the original value, and repeat the exact same test after each change. If the new outcome is worse, restore that single setting; a full reset would erase evidence and can create additional problems.
Problem-Specific Diagnosis
Begin with this controlled observation: Compare DHCP lease default gateway on two affected clients and identify both DHCP servers. Record the result and time; a vague report such as “sometimes fails” cannot distinguish the three hypotheses.
| Check | What to do | What the result tells you |
|---|---|---|
| Compare a working path | Compare DHCP lease default gateway on two affected clients and identify both DHCP servers. | If one controlled route works, the failed route is probably specific to a setting, permission, device, or service rather than a total outage. |
| Check the local state | Identify the intended router and its LAN address. | This can expose or rule out isp gateway and personal router both serve dhcp without changing several settings together. |
| Inspect the deeper layer | Inspect DHCP offers in a controlled capture and map VLAN boundaries. | Use the evidence to separate access point left in router mode from old extender advertises invalid gateway; do not assume either is proven. |
If the local comparison is inconclusive, keep the current system unchanged while checking whether access point left in router mode is consistent with the evidence. If not, investigate old extender advertises invalid gateway rather than applying every possible fix.
Use Beginner for reversible checks; use Advanced only when the comparison indicates a deeper fault. Devices alternate between working and no internet when a second router is connected. Run a harmless test and write down the time, device/account, current status indicators and the exact difference from normal behavior. Compare DHCP lease default gateway on two affected clients and identify both DHCP servers. Do not erase logs or reset the device yet. Identify the intended router and its LAN address. Confirm the relevant account, cable, selected output, permission or status before saving changes. If it is already correct, leave it alone and proceed; do not force a change just to try something. Change only the secondary device to supported access-point mode. Change only this one condition after recording the old value. If it does not improve the result, restore the former value rather than layering additional guesses on top. All test clients obtain the same intended gateway with stable internet access. Repeat the same comparison used in step one. Record what improved, what remains unchanged and whether a reconnect or normal app restart changes the result. Stop here if the expected outcome is stable. Consider isp gateway and personal router both serve dhcp, access point left in router mode and old extender advertises invalid gateway separately. Compare evidence from the working and failing paths, and avoid interpreting a green status indicator as end-to-end proof. Compare DHCP lease default gateway on two affected clients and identify both DHCP servers. Inspect DHCP offers in a controlled capture and map VLAN boundaries. Focus on logs, state, permissions, protocol negotiation or version support relevant to this failure. Do not collect or share credentials, account tokens or unrelated private content. Verify client renewals after carefully disabling duplicate LAN DHCP service. Use an isolated or test-only configuration where possible. Keep an explicit rollback path; do not weaken security, replace backup originals or bypass equipment protection to make one test pass. All test clients obtain the same intended gateway with stable internet access. Observe the behavior through the original trigger again. If the change does not produce this measurable result, undo that change and escalate with the recorded facts, rather than repeating disruptive reset attempts.Step-by-Step Troubleshooting
Capture the failing state
Check the first reversible condition
Apply the lowest-risk targeted fix
Retest and document
Distinguish the competing root causes
Inspect the deeper system layer
Run a second independent isolation test
Validate stability and rollback readiness
Solution Checklist
Common Mistakes to Avoid
- Treating isp gateway and personal router both serve dhcp as certain before running the comparison: Compare DHCP lease default gateway on two affected clients and identify both DHCP servers.
- Trying several changes at once, such as modifying access point left in router mode and old extender advertises invalid gateway simultaneously, which makes the successful change impossible to identify.
- Ignoring the safety boundary: Keep management access before changing router mode and save prior configuration.
- Assuming that a status label or progress indicator guarantees the actual action completed; verify the outcome independently.
How to Verify the Fix
All test clients obtain the same intended gateway with stable internet access.
- Repeat the original failing action under equivalent conditions: Devices alternate between working and no internet when a second router is connected.
- Run the control again: Compare DHCP lease default gateway on two affected clients and identify both DHCP servers.
- Check the positive pass condition: All test clients obtain the same intended gateway with stable internet access.
- Recheck after a normal restart, reconnection or scheduled cycle only when it is safe and relevant.
A single passing attempt is useful but may conceal intermittent failures. Record whether the fix survives the triggering condition without requiring a daily workaround.
If the Problem Continues
Use the deeper comparison rather than repeating the first steps: Inspect DHCP offers in a controlled capture and map VLAN boundaries. Verify client renewals after carefully disabling duplicate LAN DHCP service.
For an ISP escalation, provide the fiber link light state, WAN status, time of failure, and results from one wired client, without sharing passwords or public administrative addresses.
If the issue affects money, alarms, shared business records, or protective power equipment, stop risky experiments and use the official administrator, provider or manufacturer channel.
Prevent Recurrence
- Keep a record of the previously failing condition: Compare DHCP lease default gateway on two affected clients and identify both DHCP servers.
- Preserve the corrected behavior: All test clients obtain the same intended gateway with stable internet access.
- Record ONT and gateway firmware versions, cabling positions and WAN status during a healthy period; keep the provider support reference for line-level faults.
- Review configuration or hardware changes that could reintroduce isp gateway and personal router both serve dhcp.
Frequently Asked Questions
Does this symptom prove isp gateway and personal router both serve dhcp?
No. Start with the controlled comparison: Compare DHCP lease default gateway on two affected clients and identify both DHCP servers. Only treat isp gateway and personal router both serve dhcp as a candidate until the evidence supports it.
What if the first two checks do not change anything?
Move to a different layer rather than repeating the same action: Inspect DHCP offers in a controlled capture and map VLAN boundaries. That helps determine whether access point left in router mode or old extender advertises invalid gateway fits the symptoms.
How do I know the repair actually worked?
Use this outcome, not just an on-screen status message: All test clients obtain the same intended gateway with stable internet access. Keep a record of the working state for future troubleshooting.