Symptoms
Small requests pass, but larger VPN transfers stall on fiber WAN.
Use the following observations to establish that this is the specific failure described here, rather than an unrelated outage or different account:
- Failing behavior: Small requests pass, but larger VPN transfers stall on fiber WAN.
- Comparison to run: Compare small and large secure transfers and VPN client fragmentation logs.
- Pass condition: Large transfer completes with supported MTU and no dropped fragments.
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:
- PPPoE path MTU lower than expected — investigate this first only if the local state or controlled comparison supports it.
- ICMP fragmentation feedback blocked — a second layer that may survive a simple restart and requires a targeted check.
- VPN tunnel overhead not accounted for — investigate when the first two paths do not account for the observed behavior.
Before Making Changes
Do not lower MTU across all interfaces without confirming the path bottleneck. 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 small and large secure transfers and VPN client fragmentation logs. 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 small and large secure transfers and VPN client fragmentation logs. | 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 | Record MTU settings before changing anything. | This can expose or rule out pppoe path mtu lower than expected without changing several settings together. |
| Inspect the deeper layer | Evaluate path MTU discovery without indiscriminately blocking ICMP. | Use the evidence to separate icmp fragmentation feedback blocked from vpn tunnel overhead not accounted for; do not assume either is proven. |
If the local comparison is inconclusive, keep the current system unchanged while checking whether icmp fragmentation feedback blocked is consistent with the evidence. If not, investigate vpn tunnel overhead not accounted for rather than applying every possible fix.
Use Beginner for reversible checks; use Advanced only when the comparison indicates a deeper fault. Small requests pass, but larger VPN transfers stall on fiber WAN. Run a harmless test and write down the time, device/account, current status indicators and the exact difference from normal behavior. Compare small and large secure transfers and VPN client fragmentation logs. Do not erase logs or reset the device yet. Record MTU settings before changing anything. 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. Use VPN vendor's supported auto-MTU or diagnostics. 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. Large transfer completes with supported MTU and no dropped fragments. 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 pppoe path mtu lower than expected, icmp fragmentation feedback blocked and vpn tunnel overhead not accounted for separately. Compare evidence from the working and failing paths, and avoid interpreting a green status indicator as end-to-end proof. Compare small and large secure transfers and VPN client fragmentation logs. Evaluate path MTU discovery without indiscriminately blocking ICMP. 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. Ask ISP and VPN administrator to review encapsulation overhead and policy. 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. Large transfer completes with supported MTU and no dropped fragments. 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 pppoe path mtu lower than expected as certain before running the comparison: Compare small and large secure transfers and VPN client fragmentation logs.
- Trying several changes at once, such as modifying icmp fragmentation feedback blocked and vpn tunnel overhead not accounted for simultaneously, which makes the successful change impossible to identify.
- Ignoring the safety boundary: Do not lower MTU across all interfaces without confirming the path bottleneck.
- Assuming that a status label or progress indicator guarantees the actual action completed; verify the outcome independently.
How to Verify the Fix
Large transfer completes with supported MTU and no dropped fragments.
- Repeat the original failing action under equivalent conditions: Small requests pass, but larger VPN transfers stall on fiber WAN.
- Run the control again: Compare small and large secure transfers and VPN client fragmentation logs.
- Check the positive pass condition: Large transfer completes with supported MTU and no dropped fragments.
- 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: Evaluate path MTU discovery without indiscriminately blocking ICMP. Ask ISP and VPN administrator to review encapsulation overhead and policy.
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 small and large secure transfers and VPN client fragmentation logs.
- Preserve the corrected behavior: Large transfer completes with supported MTU and no dropped fragments.
- 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 pppoe path mtu lower than expected.
Frequently Asked Questions
Does this symptom prove pppoe path mtu lower than expected?
No. Start with the controlled comparison: Compare small and large secure transfers and VPN client fragmentation logs. Only treat pppoe path mtu lower than expected 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: Evaluate path MTU discovery without indiscriminately blocking ICMP. That helps determine whether icmp fragmentation feedback blocked or vpn tunnel overhead not accounted for fits the symptoms.
How do I know the repair actually worked?
Use this outcome, not just an on-screen status message: Large transfer completes with supported MTU and no dropped fragments. Keep a record of the working state for future troubleshooting.