Skip to content

Alexis Perot

← The Voice of the Proton Community

My feedback

1 result found

  1. Automatic MTU negotation

    8 votes

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    2 comments  ·  Proton VPN » New feature  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    Alexis Perot supported this idea  · 
    An error occurred while saving the comment
    Alexis Perot commented  · 

    Another data point in favor of this: PPPoE-based fiber connections have a hard path MTU of 1492 bytes. When ICMP "frag needed" messages are filtered anywhere along the path (common ISP behavior), the app's default tunnel MTU fails silently; sites partially load, requests time out, and users conclude the VPN is broken.

    Currently the only workaround is manual WireGuard config files with MTU = 1400 under [Interface], losing all app conveniences (server switching, Secure Core, kill switch, split tunneling) just to set one number.

    I'd also second Juha's suggestion above of simplifying the title to "Adjustable MTU"; both auto-negotiation and a manual override field solve the same user problem from different ends, and a broader title would aggregate these votes instead of splitting them.

    Concrete ask: Settings → Connection → "Override tunnel MTU" (desktop apps, Linux particularly), or auto-clamping via path-MTU discovery. The config-file ecosystem already supports the concept, so the GUI just needs to expose it.