I think it expects you to use a standardized device name structure such as wg0 however it doesn’t exactly (or rather clearly) enforce this, and it tries to name the new device whatever the file is named during the import step.
This problem is somewhat compounded by VPN providers, who often generate some long filename when you export a WG config.
The reason wg-quick wants ten character filenames in the conf file is that it (the conf file name) is gonna be the virtual adapter name and the limit on those is ten characters.
Some vpns are annoying and give you confs that will totally work except that they’re a whole goddamn sentence. One of those vpns is air.
threaded - newest
Worth noting, it doesn’t like long
.conffilenames. If you get an error that the file can’t be found when importing, try shortening the filename.Lol was it written for DOS?
I think it expects you to use a standardized device name structure such as
wg0however it doesn’t exactly (or rather clearly) enforce this, and it tries to name the new device whatever the file is named during the import step.This problem is somewhat compounded by VPN providers, who often generate some long filename when you export a WG config.
The reason wg-quick wants ten character filenames in the conf file is that it (the conf file name) is gonna be the virtual adapter name and the limit on those is ten characters.
Some vpns are annoying and give you confs that will totally work except that they’re a whole goddamn sentence. One of those vpns is air.
yeah, proton vpn is the same, this guide is what made it finally work for me personally