RandomChain

joined 2 years ago
sorted by: new top controversial old
Changing Wireguard connection MTU on Linux app in c/[email protected]
[โ€“] [email protected] 1 points 1 week ago

Seems there is already a feature request open for this issue, please vote for it if it's relevant for you as well. https://protonmail.uservoice.com/forums/932836-proton-vpn/suggestions/48509147-permanent-mtu-setting-for-wireguard-in-protonvpn

Changing Wireguard connection MTU on Linux app in c/[email protected]
[โ€“] [email protected] 1 points 1 week ago

Well, in case anyone is interested, I found a way to workaround my problem.

I edited ../proton/vpn/backend/linux/networkmanager/protocol/wireguard/wireguard.py. Added mtu property to the Config class, then at the end of _set_wireguard_properties added this:

# Added by RandomChain - setting the MTU
logger.info(f'### RandomChain says: setting mtu to {wg_config.ipv4.mtu}')
wireguard_config.set_property(
    NM.SETTING_WIREGUARD_MTU,
    wg_config.ipv4.mtu
)

I know it's ugly and hacky, but it works for me. I should probably open a bug to be able to properly change it from the app settings.

4
Changing Wireguard connection MTU on Linux app (lemm.ee)
 

I'm using Pop!_OS 20.04. Until now I've been using wireguard conf files that I set up manually with nmcli and that works fine, but I though I'd give the linux app a try, mainly to be able to quickly switch servers without needing to download a new conf file each time.

My issue is I have to set the wireguard connection MTU to 1400 on my network. With the default value of 1420, connections are always timing out and I can't get any site loaded on Firefox. Now, I can run ip link set from terminal and change it after the app creates the proton0 interface, and that's a workaround, but is there some way to change the MTU parameter for all connections?

1
Why is the new 6.8.0 kernel package named "daily"? (lemm.ee)
 

I noticed the newest kernel package is named "linux-image-6.8.0-76060800daily20240311-generic".

Why is it named daily? Does it mean we will be getting more frequent kernel updates? Or just some daily build that someone forgot to change its name?