Data on the internet is not sent as one continuous stream. It is cut into packets, and every network along the way has a limit on the largest packet it can pass on. That limit is the MTU: maximum transmission unit.
Most of the time nobody needs to think about it. Devices and routers agree on it themselves. But when that agreement fails, the symptoms are among the most confusing in home networking.
The simple picture
Imagine a road used by lorries, with one low tunnel in the middle. Small lorries pass without trouble. A lorry that is too tall must split its load in two, or turn back.
On the internet, that splitting is called fragmentation, and modern networks often refuse to do it. Instead they send a message back to the sender: "your packet is too big". This process is called Path MTU Discovery.
The trouble starts when that reply is blocked along the way, by an over-strict firewall, for instance. The sender never finds out, keeps sending large packets, and they keep disappearing. A router that drops packets without a word like this is often called a black hole. How firewalls sort traffic is explained in the guide to what a firewall is.
Numbers worth knowing
- 1500: the standard MTU for Ethernet and Wi-Fi, used on almost every home network.
- 1492: the usual MTU for PPPoE connections, because PPPoE uses 8 bytes for its label.
- Around 1420: the common default for WireGuard. Other VPNs take different amounts of room, usually a few tens of bytes.
- 1280: the minimum every IPv6 network must be able to pass.
- 28: the IP header (20 bytes) plus the ping header (8 bytes). This figure is used when measuring MTU with ping.
- 40: the IP and TCP headers. MTU minus 40 gives the MSS, the data room inside a TCP packet.
The telltale symptoms
What makes MTU problems hard to spot is how selective they are:
- Some sites open normally; others spin without ever loading.
- A page starts to appear, then stops halfway, usually when a large part such as an image or script loads.
- Sites and apps using encrypted connections, banking, work email, are hit more often.
- Short chat messages send, but photos don't.
- Ordinary pings succeed, but large file uploads always fail or freeze at the same percentage.
- The problem appeared only after installing a VPN, changing router, or switching connection type.
Small packets get through, large ones vanish. That is why the connection seems to "almost work".
Why PPPoE is often involved
Many home connections use PPPoE, which adds an 8-byte label to every packet. The room for data shrinks from 1500 to 1492. A correctly configured router handles this automatically. A router set up by hand with an MTU of 1500 over PPPoE is one of the most classic sources of trouble.
This often happens when the provider's modem or ONT is switched to bridge mode and your own router takes over the PPPoE login. In that setup, your router is the one that must use 1492. The different roles of ONT and router are explained in the guide to modems, routers, and ONTs.
VPNs do something similar with larger labels, shrinking the data room further. Other symptoms with a VPN are covered in the guide to slow internet on a VPN.
MTU on setups common in Indonesia
The right value depends on who runs the internet login. Some of the setups met most often:
| Setup | Who handles PPPoE | What you need to do |
|---|---|---|
| Home fibre, provider-supplied ONT in router mode, devices connected straight to the ONT | The ONT | Usually nothing. Devices at home stay at 1500; the ONT adjusts |
| ONT switched to bridge mode, your own router logs in | Your router | WAN MTU 1492 with MSS clamping on |
| A MikroTik router as a PPPoE client to the provider | The MikroTik | The default is 1460, safe but a little smaller than possible; it can go up to 1492 after testing |
| RT/RW net subscribers or office networks with a MikroTik PPPoE server | The operator's server | The MikroTik server default is 1480. If you put your own router behind it, match the measured value |
| A laptop on a phone hotspot or 4G modem | The operator's network | The value can differ between operators; measure with ping if symptoms appear |
The MikroTik defaults above come from the official RouterOS documentation (checked November 2026). The same documentation states that PPPoE MTU and MRU must not exceed 1492.
A common example: a shophouse owner asks a technician to switch the ONT to bridge mode in order to use a more capable router of their own. The login works and most sites load, but the internet banking portal and document uploads to government sites freeze halfway. A ping test shows 1472 failing and 1464 succeeding, so the path MTU is 1492, while the new router is still on 1500. Once the WAN MTU is set to 1492 and MSS clamping is on, the symptoms disappear. Switching the ONT to bridge mode is covered in the guide to bridge mode and your own router.
Checking without guessing
Ping can send a packet of a set size with fragmentation forbidden. Pick a destination that normally answers ping, such
as 8.8.8.8. The basics of ping are in the
guide to using ping and traceroute.
- Windows:
ping -f -l 1472 8.8.8.8. The-foption forbids fragmentation,-lsets the data size. - macOS:
ping -D -s 1472 8.8.8.8. - Linux:
ping -M do -s 1472 8.8.8.8.
An example on Windows over a PPPoE connection (illustrative):
ping -f -l 1472 203.0.113.10
Pinging 203.0.113.10 with 1472 bytes of data:
Packet needs to be fragmented but DF set.
ping -f -l 1464 203.0.113.10
Pinging 203.0.113.10 with 1464 bytes of data:
Reply from 203.0.113.10: bytes=1464 time=12ms TTL=57
How to read it:
- Start at 1472. If it succeeds, the path's MTU is 1500 and usually nothing needs changing.
- If it reports that the packet needs to be fragmented, or on Linux message too long, lower the number: 1464, 1452, and so on, until it succeeds.
- The largest number that succeeds, plus 28, is the path's MTU. In the example above, 1464 + 28 = 1492.
- If every large size only gives Request timed out with no message, while ordinary pings succeed, the "packet too big" message is being blocked along the way. Keep lowering until it succeeds.
To see the MTU a device is currently using, run netsh interface ipv4 show subinterfaces on Windows,
networksetup -getMTU en0 on macOS, or ip link show on Linux.
Fixing it
- On the router. Log in to the router's admin page (how is in the guide to logging in to 192.168.1.1), find the WAN or Internet menu, then its advanced settings. Change the MTU to the measured figure. Save and restart the connection.
- Turn on MSS clamping. On PPPoE connections, many routers have an option called MSS clamping or TCP MSS adjust that is worth switching on. It tells devices behind the router to use the right packet size from the start, so they don't depend on a message that may be blocked. On MikroTik, the equivalent is Change TCP MSS in the PPP profile.
- In the VPN app. If the problem only happens with the VPN on, change the MTU in the VPN app's settings, not on the router. A value of 1400 or a little below is generally safe.
- On one device only, if only that device has the problem. On Windows, in Command Prompt as
administrator:
netsh interface ipv4 set subinterface "Wi-Fi" mtu=1492 store=persistent. On macOS:sudo networksetup -setMTU en0 1492. On Linux:sudo ip link set dev eth0 mtu 1492(lasts until the device restarts).
After changing it, reopen the sites that failed and try uploading a large file. If nothing changes, return to the automatic value and look for another cause.
Symptoms, causes, and fixes
| Symptom | Most likely cause | Fix |
|---|---|---|
| Some HTTPS sites spin forever after changing router | MTU 1500 over PPPoE | Set the WAN MTU to 1492 and turn on MSS clamping |
| Sites fail only with the VPN on | Packet room shrinks because of the VPN header | Lower the MTU in the VPN app |
| Large pings only time out, small pings succeed | "Packet too big" messages are blocked | Find the largest size that passes, set the MTU at or below it |
| Only one laptop has the problem | MTU set by hand on that laptop | Return the laptop's MTU to 1500 or automatic |
| Certain sites fail on every device, large pings are normal | Not MTU; probably DNS or blocking | Check DNS and blocking |
MTU myths
- "Lowering MTU speeds up the internet." No. The right MTU prevents problems but doesn't add speed.
- "Changing MTU lowers game ping." It has no meaningful effect on latency.
- "1500 is always right." Right for ordinary Ethernet, wrong for PPPoE and VPNs.
- "Jumbo frames make the internet faster." Jumbo frames are only for local networks and don't apply to the internet.
When it isn't MTU
Some sites refusing to load can also stem from DNS or blocking. If large pings succeed normally, the next checks are in the guide to specific apps that won't open and the guide to a DNS server not responding.
In Indonesia, one possibility always worth ruling out is blocking. A blocked site usually fails from the start or is redirected to a warning page; it doesn't load halfway and then stall the way an MTU problem does. You can check a domain on Komdigi's TrustPositif site by typing the domain into its search box. If the domain is listed, changing the MTU won't help. How blocking works is covered in the guide to why sites are blocked.
| Clue | More likely MTU | More likely blocking or DNS |
|---|---|---|
| How it fails | The page starts to appear, then stalls | Fails from the start, or a warning page appears |
| Which sites | Many random HTTPS sites, especially heavy ones | Particular sites only, always the same ones |
| Over mobile data | Often fine | Often still fails, because mobile operators block too |
| Large ping with fragmentation forbidden | Fails above a certain size | Normal |
The bottom line
MTU is the largest packet that can pass. When it is wrong, small packets get through and large ones vanish, so some sites won't load. Measure with sized pings, then set the value on the router or VPN, and turn on MSS clamping on PPPoE connections. As long as there are no symptoms, leave it on automatic.
Frequently asked questions
What is the right MTU value?
For ordinary Ethernet, 1500. PPPoE connections usually need 1492. VPNs and some tunnels need smaller values still. On most home routers the automatic setting is already correct and needs no change.
Does lowering MTU make the internet faster?
No. The right MTU only prevents problems. Lowering it more than necessary slightly adds overhead, because data is split into more packets.
What is the difference between MTU and MSS?
MTU is the size of the whole packet, headers included. MSS is the data room inside one TCP packet, which is the MTU minus 40 bytes of IPv4 and TCP headers. So an MTU of 1500 equals an MSS of 1460, and an MTU of 1492 equals an MSS of 1452.
Should I enable jumbo frames?
Not for the internet. Jumbo frames (an MTU of around 9000) only help on a local network, for example between a computer and a NAS, and only when every device on the path supports them. The internet still uses packets of 1500 bytes or smaller, so enabling them for no reason can actually cause problems.
What MTU do RT/RW net subscribers using MikroTik need?
Many RT/RW nets run a MikroTik PPPoE server, whose default is 1480. If the operator hasn't changed it, a ping with fragmentation forbidden will succeed up to a size of 1452. If you put your own router behind it that logs in to that server over PPPoE, set the WAN MTU to the measured value and turn on MSS clamping.