FOR TIPS, gUIDES & TUTORIALS

subscribe to our Youtube

GO TO YOUTUBE

12050 questions

14345 answers

22600 comments

36089 members

0 votes
163 views 1 comments
by

Hello,

By default the MTU of the wireguard interfaces is set to 1420 bytes (1500=default MTU of wwan0  minus 80). This will lead to dropped frames if the MTU of wwan0 is smaller for example 1460 then the limit is 1380. See here  here and probably others.

Would it be possible for the UI to check the MTU of the wan interface when the tunnel is created and adjust the value accordingly ?

Regards,

1 Answer

0 votes
by

Hello,

I'll bring attention to this question separately and will discuss it with our RnD internally. While having a lower default MTU might help for some mobile/PPPoE users, I've seen some complaints that even lower MTU (1360 when using IPv6 for example or even as low as 1280 in some very specific cases, see RFC2460, section 5) is necessary to make things work without interruptions. It's quite difficult to predict how service will function in any specific environment and setting MTU too low may cause performance drops due to increased packet fragmentation.

One thing I'd like to note is it may be enough to enable MSS Clamping by default (when WG zone is created) instead of lowering the default MTU. However, this may not work every case - in some cases MTU would still have to be set below 1420 (1400, 1392, 1380, 1360 etc...). Issues would arise (most notably) when using mobile or PPPoE interfaces.

Best regards,

Tomas.

by
I have one case a RUTX11 in the EU to a dd-wrt in the US, both ends have a 1500 bytes MTU on the wwan interface the tunnel isn't usable for any wg MTU above 1360 bytes. MSS clamping changes nothing. Go figure ...