Setting MTU Back to Blank/Optional doesn't seem to work

I own both a SlateAX and a Beryl, however I am currently playing with the AX (FW 4.0.3) .

I have a bunch of WG configs for surfshark. On one of the configs, I played with the MTU setting trying to make it work with a cruise connection. I don’t seem to be able to remove the “optional” field anymore.

I have tried the following.

  1. VPN Dashboard → Options → MTU → [blank] → Apply. I get a sucess, however nothing seems to have changed.
  2. Wireguard client → Surfshark → specific config → edit → deleting the MTU line → apply.
    This gives me success, but does not stick.
  3. Wireguard client → Surfshark → specific config → edit → item mode → deleting the MTU field → apply.
    This gives me success, but does not stick.

Is this really an optional field? If so, shouldn’t i be able to remove this field and have it figure itself out? Or does it make sense to just set it to 1420 and let it be.

As the MTU is the Maximum Transfer Unit (aka How big is my Packet before it needs to be split), it makes no sense to delete the value.

In IPv6 this value should be negotiated. Bit as you played around with the MTU of the tunnel, I think there’s is simply a default.
In worst case the MTU of the physical adapter is used. This means it will work, but lead to a huge amount of fragments with only the size of the overhead in the second frame.

What is your goal by deleting this value?

1 Like

Are you referring to Internet on a cruise ship? Internet on cruise ships tend to be flaky and have high latency, although some cruise lines offer premium plans for extra $$. Lowering the MTU for WireGuard may help:

I do not work for and I am not directly associated with GL.iNet

1 Like

The MAX mtu is 1500, which is also the default one.

As vpn has headers, so it should have a lower MTU.

For Wireguard you may need 1380 etc.

Ok, so it sounds like when the field is blank, it defaults to a 1500 byte MTU.

Is there a MTU discovery process when using IPv4?

If there were some discovery process, then having a blank option of “do MTU discovery” vs a hard coded value could have different effects.

However, if there is no MTU discovery process, typing in 1500 would be equivalent of just deleting the MTU field?

You should see the MTU for all interfaces by running the ifconfig command in SSH.

There is MTU discovery but it is not reliable. It is better just to set the correct mtu.

The MTU discovery is done by applications, not the router. So a lot of problems.