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.
VPN Dashboard → Options → MTU → [blank] → Apply. I get a sucess, however nothing seems to have changed.
Wireguard client → Surfshark → specific config → edit → deleting the MTU line → apply.
This gives me success, but does not stick.
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.
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