damn son! the price also will soooooooooo damnnnnn

Mine still show 1480, with no error log anymore.

weird, mine show 1492 on previous 7.20 beta and latest 7.20 stable

maybe something is making your MTU to get 1480, if me i do backup first and then reset factory, after that i do minimum configuration , see if still getting 1480 or 1492.



This post has been edited by syahpian: Oct 2 2025, 12:37 PM

also mine didnt force max MTU

In your pppoe client, set:
Max MTU 1500
Max MRU 1500
Delete Keepalive Timeout

Thanks guy, removed max MTU and MRU and removed keep alive timeout fixed the issue.

just updated to V7.20 and the winbox3.43 or it will not connect.

also updated the MTU and MRU to 1500.

I am not quite sure, I was having issue when it stayed at 1480... is it with lost package?

I am not sure about winbox as I don't use it.

Is your MRU = 1500 and MTU = 1492 now?

Actually all connections with MTU less than 1500 requires special handling. In Mikrotik, the default firewall rule perform MSS Clamping, but it only works for TCP connections.
Later on the PPPoE profile provided this without firewall rules.

By right when your MRU is 1500, half your problem is gone.

you may be right. previously when I set up Wireguard... it was like sluggish or not working correctly, I cannot upload files or create folders.... I just tested it and it works. wireguard mtu is only 1420.

Interface pppoe out1... actual MTU 1492

set Max MTU 1500
Max MRU 1500 as per your advise.

yup MRU is 1500 --- I went into the status tab to see it.

This post has been edited by skywardsword: Oct 3 2025, 08:39 PM

Wireguard overhead is 80 bytes. So you must recalculate it. Set it to 1492 - 80 = 1412.
The default WG MTU is wrong because it is based on full 1500 bytes packet.

If you use WG on mobile network, it is actually 1400 - 80 = 1320.
So set 1320 as MTU in wireguard app on devices using mobile network.
You can keep the 1412 in Mikrotik.

Also go to your IPv6 > ND. Set MTU 1492 there.

Wireguard overhead is not 60? So if calculated it's 1432 max, so we'll use 1420 to be safe.

In your case 1412, same 1420 to be safe.

Correct me if wrong.

It is only 60 bytes if you exclusively use IPv4.
There is an extra 20 bytes for IPv6 inside WG.

1412 is the correct size. 1420 packet is too big and cannot fit smaller pipe.
1420 is only valid if TM don't use PPPoE.

I am using the Mikrotik "Back to home" app... which does not have the MTU setting from what I could see. when it is connected it shows connected via IPv4 relay. (I off the wifi to test the mobile connection). at this moment, after updating to V7.20 and setting the mikrotik's setting to max MTU MRU 1500. the back to home app seems to work pretty ok already. so I probably do not need to set the mobile phone's Back to home app's MTU.


edit: sorry I said I used wireguard. I am actually using the Back to home app, by mikrotik , which uses Wireguard.

This post has been edited by skywardsword: Oct 3 2025, 10:05 PM

I don't use the BTH app, but I am guessing they should have some kind of Path MTU Discovery mechanism inside. They are networking product maker and cannot be that dumb. Mobile network is notorious for smaller than usual MTU due to all the encapsulation between eNB.

Upload should work because your MRU allows it.
If you test download and it works too, then you can stop here.
Else you might need to set 1320 inside Mikrotik

BTH is still wireguard behind the scene. They just package it into an easy to use app and Mikrotik operates a relay.

This post has been edited by kwss: Oct 3 2025, 10:11 PM

I have been playing with the Back to Home app, and adjusting the MTU 1500>1420>1412...did not get amazing speed, at most is 3-4mbps download from cloudflare and upload speed of 500kbps. My mobile line is TM mobile, even without "wireguard/vpn" speed is at best 15mbps, and 3 mbps... so I am not expecting too much from it since it have to hope around.


I have yet to try 1320 (all setting done on mikrotik since like mentioned b4, BTH app no control, and each time I would delete the BTH's tunnel and have the app redo it again. )

yah TP-Link cannot do cannot do roaming when using MLO
so i don't need MLO so very imported roaming hmmm

i watched but wifi 6 and still use 1GBPS Port outdate
long time mikrotik no new launch 2.5Gbps Port hmmm i think possible 2026 or 2027 i will be old age lol

If MLO is not important, might as well just stick to Wifi 6 or 6E. Wifi 7 with MLO supposed to allow more speed but it is half baked now.

Mikrotik tour



This post has been edited by cyberic: Oct 7 2025, 07:30 PM