Hi! We’ll track down your router MTU issues and get rid of the random lag and timeouts. I just need a quick picture of what’s happening so we can choose the right MTU troubleshooting steps.
• What are the main symptoms — packet loss in games, VPN dropping after a few minutes, some websites not loading, or file downloads stalling at a certain percentage?
• Are you using any VPN client (OpenVPN, WireGuard, IPSec), or connecting to work via remote desktop?
• Which router do you have (Netgear, TP-Link, ASUS, ISP modem/router combo, etc.), and do you know if the WAN MTU size was changed from the default 1500?
• Finally, is the connection type PPPoE, DHCP, or static IP according to your ISP? PPPoE connections often need a smaller MTU (like 1492 or 1480) to avoid fragmentation and blackhole routes.
With those details I can help you find the optimal MTU and adjust it on the router and, if needed, on your PC or VPN.
Customer
I think it might be MTU related because normal browsing is mostly okay, but online games and VPN are a mess. In shooters I get random spikes of packet loss and “network error” icons, and my work VPN disconnects every few minutes. Speed tests show full speed, so the ISP says everything is fine. I have a Netgear router in router mode behind a fiber ONT. I don’t remember ever touching the MTU setting but I might have changed it when I was trying to optimize for gaming.
That combination — games and VPN breaking while simple webpages load — is very typical of MTU mismatch or path MTU issues.
In short, MTU (Maximum Transmission Unit) is the largest packet size a device can send without fragmentation. If your router MTU size is too high for some part of the path, packets get fragmented or dropped, causing:
• Occasional packet loss and rubber-banding in games.
• VPN tunnels that connect but then drop when larger packets are sent.
• Some websites hanging on load while others are fine.
If the MTU is set too low, traffic still works, but you may lose a bit of efficiency. So the goal is to find a safe MTU value that is small enough to avoid fragmentation but large enough to be efficient for your ISP and any VPN.
We’ll first confirm whether you’re actually hitting MTU problems on the router by running a quick ping MTU test from your PC, then we’ll mirror that value in the router’s WAN MTU setting.
Customer
That makes sense. I remember seeing a YouTube video telling me to lower the MTU to 1400 for “better ping”, so I think I changed it somewhere in the Netgear admin page but I can’t remember exactly what I did. Since then, some websites just spin forever, and my VPN seems the most unstable. How do I run this MTU test from Windows so we know what number to use?
Perfect, we’ll use the classic ping + “do not fragment” method to discover your maximum MTU without guessing.
Step A — Use ping to find your optimal MTU in Windows
1) On your Windows PC, open Command Prompt as Administrator.
2) First we test a fairly large packet. Type (but don’t press Enter yet):
ping 8.8.8.8 -f -l 1472
Here, -f means “don’t fragment” and -l (lowercase L) sets the payload size in bytes. 1472 bytes of data + 28 bytes of headers ≈ 1500 MTU.
3) Press Enter. If you see “Packet needs to be fragmented but DF set” or timeouts, your path doesn’t support a full 1500-byte MTU.
4) Decrease the size in steps (for example 1464, 1452, 1440…) until ping works with no fragmentation.
5) Once you find the largest value that does not fragment, add 28 to that number to get the optimal MTU. For example, if 1472 fails but 1464 works, 1464 + 28 = 1492 MTU — a common value for PPPoE.
Tell me what is the largest packet size that works without fragmentation and I’ll show you exactly where to set that MTU on your router WAN.
Customer
I tried that. At 1472 I get “packet needs to be fragmented”, same at 1464. When I go down to 1452 it works fine, and 1460 also works. 1470 fails again. So it looks like 1460 is the largest size that doesn’t fragment. That would make the MTU about 1488 if I add 28, right? That’s lower than 1500 but higher than 1400.
Exactly — 1460 (payload) + 28 (IP + ICMP headers) gives an optimal MTU of 1488 for your current path. That means setting your router MTU size to around 1480–1492 is reasonable; going all the way down to 1400 was overkill and may cause odd behavior with some services.
Step B — Set the MTU size on your Netgear router
1) On a device connected to the router, open a browser and go to http://routerlogin.net or the router’s IP (commonly 192.168.1.1).
2) Log in with your router admin username and password.
3) Go to Advanced > Setup > WAN Setup (or similar). Look for the field named MTU Size or Maximum Transmission Unit.
4) Change it from whatever it is now (often 1500 or 1400) to 1488. If the router only accepts “auto / 1500 / manual”, choose Manual and enter a value between 1480 and 1492 to match your ping tests.
5) Apply/save the settings and let the router reconnect your WAN link.
After that, we’ll retest your VPN stability and run a quick game or ping test to see if the MTU issue on the router is resolved.
Customer
I found the WAN setup page and the MTU was actually set to 1400 like I suspected. I changed it to 1488 and let the router reboot. Browsing feels a bit smoother, and my VPN stayed connected longer than it usually does, but I still see some spikes and occasional “request timed out” when I do ping tests while the VPN is on. Do I also need to adjust MTU on the VPN or my PC?
Good catch — VPN MTU issues are a second layer on top of router MTU. VPN protocols add extra headers, so the effective MTU inside the tunnel is smaller than the router’s WAN MTU.
Step C — Tuning MTU for VPN and PC
• Many OpenVPN / IPSec clients have an option like “MSS fix” or “Tunnel MTU”. Values around 1300–1400 bytes inside the VPN often help if you see packet loss only when the tunnel is active.
• If your VPN app has an “MTU” or “Data channel MTU” field, try setting it to 1400 and reconnect. That leaves room for the extra VPN headers on top of the router’s 1488 MTU.
• On Windows you normally keep the NIC MTU at default, but for stubborn path MTU blackhole issues your company’s IT might recommend a specific interface MTU (for example 1400) on the VPN adapter only.
For now, let’s keep the PC at default MTU, keep the router at 1488, and just lower the VPN’s internal MTU/MSS if possible. After changing the VPN setting, we’ll rerun the ping test while connected and see if the timeouts disappear.
Customer
My VPN client does have an “MTU” option and it was set to “auto”. I changed it to 1400 like you suggested and reconnected. Now my ping test while on VPN looks a lot more stable, and my test game didn’t show packet loss warnings in the first match. I still see a bit higher ping, but that’s expected with VPN. Are there any other router MTU settings or advanced options I should avoid touching?
Great — that tells us the main MTU problem on the router/VPN path is under control.
For a typical home network, here are a few guidelines so you don’t accidentally recreate MTU issues:
• Avoid turning on jumbo frames or setting LAN MTU to huge values (like 9000) unless every device and switch in the path supports it and you know why you need it.
• Don’t mix vastly different MTU values on WAN and LAN just for experimentation. Keeping LAN MTU at 1500 and using your tested value on the WAN MTU is usually safest.
• Some routers have hidden “MTU tweak” or “performance optimization” toggles. If you see odd behavior after enabling them, it’s better to revert to standard MTU settings and rely on your ping-discovered value instead of gimmicks.
• You can still use QoS for gaming, but do that separately from MTU. Adjusting QoS won’t fix MTU mismatch and, if misused, can hide the real cause of packet loss.
With your router MTU and VPN MTU aligned, we can now focus on verifying gaming latency and making sure regular browsing, streaming, and downloads all behave normally.
Customer
I played a few more matches and things look much better. No more big red “packet loss” indicators and the connection feels smoother. My work VPN also stayed connected for about an hour without dropping, which never happened before. If MTU is working now, is there anything else I should change so I don’t have to redo all this when I change routers or ISPs later?
Good question — the real win with router MTU troubleshooting is knowing the process so you can repeat it whenever something changes.
Step D — Make your MTU fix repeatable
• Write down your current WAN MTU value (1488), your router model, and the VPN MTU you ended up using.
• Keep a small note with the ping -f -l test commands you ran. Next time you change ISP or add a new router, you can quickly rerun those tests instead of guessing an MTU value you found in a random forum.
• If you ever switch to a PPPoE connection or a different VPN provider, redo the ping test and adjust the router’s MTU and VPN MTU accordingly (many PPPoE links work best around 1492 or 1480).
• Avoid stacking multiple “tuning” tools (registry tweaks, third-party “internet accelerators”, etc.). Keeping configuration simple with a known-good MTU size is more reliable than a bunch of overlapping tweaks.
This way, even if you buy a new router or move house, you can re-apply the same MTU optimization method in a few minutes.
Customer
That all sounds reasonable. I took screenshots of the WAN MTU page and my VPN settings so I won’t forget. Right now everything feels stable: games run smooth, streaming is fine, and my remote desktop session to work isn’t lagging like before. Anything else I should check from a security or maintenance point of view while I’m already in the router settings?
Great job getting through the
MTU diagnostics — let’s do a quick health check while we’re here so your network stays solid.
• Make sure
router firmware is up to date; vendors often fix bugs related to
MTU, PPPoE, and VPN passthrough in updates.
• Confirm Wi-Fi security is set to
WPA2 or WPA3 with a strong password, and disable WPS if you’re not using it.
• If your ISP’s modem also does routing, consider putting it into
bridge mode so your Netgear is the only device handling
MTU and NAT. Double NAT sometimes hides path MTU problems and makes debugging harder.
• Optionally, save or export your router configuration so that if you ever need to factory-reset, you can restore your working
MTU configuration quickly.
Summary: To fix
router MTU issues, you discover the highest non-fragmenting packet size with
ping -f -l, convert that to a proper
WAN MTU on the router, and then tune
VPN MTU / MSS if needed. That stops random packet loss, VPN drops, and odd website timeouts. If MTU ever becomes confusing again, you can
open a chat with an expert and we’ll walk through the tests together in real time.
Customer
Awesome, thanks for the detailed guidance. I had no idea MTU settings could cause so many weird problems, but everything’s running smoothly now. I’ll keep this process handy in case I change providers or hardware in the future.
Any time! If a friend complains about
random packet loss,
VPN disconnects, or games lagging even though their speed test looks great, there’s a good chance they’re also dealing with
router MTU issues. You can share this MTU checklist with them — and if you’d like someone to click through the router settings with you next time, just
start a chat with an expert and we’ll take it from there.
How to test and find the right MTU for your router
To quickly narrow down MTU issues on your router, you don’t need special tools — just the built-in ping command and your router’s admin page.
Start from a wired PC to rule out Wi-Fi noise. Use ping <target> -f -l <size> to test different sizes; the largest value that works without the “packet needs to be fragmented” message gives you the payload size. Add 28 bytes for headers and you have the maximum MTU the path supports. Set your router WAN MTU close to that number (slightly lower is fine) and retest your VPN and critical apps.
If you use PPPoE, L2TP, or other VPN tunnels, repeat a similar test while connected to the VPN or follow your provider’s recommended MTU. Matching the router MTU, VPN MTU, and client MTU makes a huge difference in stability, especially for gaming, remote work, and large file transfers.
Router MTU issues — quick troubleshooting tips
Use ping tests and WAN MTU settings to stop fragmentation and packet loss.
Fast path: from a PC, run ping 8.8.8.8 -f -l X and adjust X until you find the largest packet size that does not fragment → add 28 to get the optimal MTU → set that value as the router’s WAN MTU → restart the router and retest games, VPN, and streaming → if VPN still has issues, lower the VPN MTU or enable MSS clamping so packets inside the tunnel fit under the router MTU. Keeping firmware updated and avoiding unnecessary jumbo frames helps prevent future router MTU issues.
Disclaimer: This information is AI-generated and intended for general guidance only. For advice specific to your router model, ISP, and VPN setup, please consult a verified expert on Whizz-Tech before making decisions.
What are signs of router MTU issues?
Common signs of router MTU problems include websites that partially load or hang, online games showing packet loss and rubber-banding, VPNs that connect but drop under load, and large downloads that stall. Speed tests might still look normal, which is why ISPs often say the line is fine even when MTU is misconfigured.
How do I find the best MTU for my router?
The most reliable way to find your optimal MTU is to use ping tests with the “do not fragment” flag. From a PC, run ping 8.8.8.8 -f -l X with different values of X to find the largest packet size that does not fragment, then add 28 bytes for headers. Set that result as your router’s WAN MTU size, apply the change, and retest your VPN and critical apps.
Should I lower my MTU to 1400 for gaming?
There is no universal “best MTU for gaming”. Setting MTU to 1400 sometimes hides problems, but it can also cause weird slowdowns or inefficiencies. It’s better to measure the correct MTU for your connection using ping tests, then set the router WAN MTU accordingly (often 1480–1500 on non-PPPoE links). For VPN gaming, also tune the VPN MTU/MSS instead of blindly lowering the router MTU.
Do I need to change MTU on my PC or just on the router?
In most home setups you only need to change the WAN MTU on the router. Devices behind the router normally keep the default 1500 MTU. However, if you use a VPN client, that VPN adapter might need its own MTU/MSS tweak to account for tunnel overhead. Adjusting PC interface MTU is usually a last resort or something your company’s IT may instruct you to do for specific work VPNs.