Re: Troubleshoot wireguard

From	Mike Easter <MikeE@ster.invalid>
Newsgroups	alt.os.linux
Subject	Re: Troubleshoot wireguard
Date	2022-09-07 08:32 -0700
Message-ID	<jnrrrnFokg4U1@mid.individual.net> (permalink)
References	<jnp8leFc1v6U1@mid.individual.net> <jnqs8vFoie1U1@mid.individual.net>

Show all headers | View raw

J.O. Aho wrote:
> Mike Easter wrote:
> 
>> What doesn't work: Attempt to connect to vpn server via wireguard 
>> fails: returns invalid configuration
>>
>> Method for wireguard:
>> https://protonvpn.com/support/wireguard-configurations/  WireGuard 
>> configuration files are available
>>
>> The requirements for getting the wireguard enhancement of the network 
>> manager for protonvpn require some compilation.
>>
>>> How to use WireGuard with NetworkManager on Ubuntu 20.04 LTS
> 
> I would say the implementation of wireguard in networkmanager is flawed, 
> myself I spent days on trying things to get working, I got only to a 
> point where the connection was set up, but all the routing was messed up 
> which lead to a non-usable setup. networkmanager do not use the wg, but 
> tries to setup things itself.
> 
> I ended up with writing a small daemon that just keeps track of which 
> configurations exists and which of them are up and uses the wg command 
> to set up or tear down a wireguard connection. Then I wrote a small app 
> for the desktop, so I can get the list of wireguard setups in 
> /etc/wireguard and start/stop those.
> 
I've gotten it working twice at separate times in Mint 20 Cinnamon 
running live based on Ub 20.04 using the above pub'd instructions and 
briefly successfully tested it with a couple of VPN servers.   Since I 
don't regularly vpn, I haven't spent more than a few seconds each time.

One of the behaviors at Protonvpn that it documents but somehow 'slipped 
by me' (call it not paying proper attention) is that the .conf files it 
creates and makes available for dl for the user and also saves at its 
site, are not saved at proton w/ the private key which is only saved as ***.

Early in my confusion, when I would boot the live system again and 
'reacquire' the previously created .conf file from proton, I was 
'bamboozled' by the missing private key from the .conf, which won't work 
w/o it.



-- 
Mike Easter

Back to alt.os.linux | Previous | Next — Previous in thread | Next in thread | Find similar

Thread

Troubleshoot wireguard Mike Easter <MikeE@ster.invalid> - 2022-09-06 08:52 -0700
  Re: Troubleshoot wireguard Killadebug <killadebug@mouse-potato.com> - 2022-09-06 16:00 +0000
    Re: Troubleshoot wireguard Mike Easter <MikeE@ster.invalid> - 2022-09-06 09:37 -0700
    Re: Troubleshoot wireguard Mike Easter <MikeE@ster.invalid> - 2022-09-06 10:22 -0700
      Re: Troubleshoot wireguard Mike Easter <MikeE@ster.invalid> - 2022-09-06 11:50 -0700
  Re: Troubleshoot wireguard Mike Easter <MikeE@ster.invalid> - 2022-09-06 10:20 -0700
  Re: Troubleshoot wireguard "J.O. Aho" <user@example.net> - 2022-09-07 08:33 +0200
    Re: Troubleshoot wireguard Mike Easter <MikeE@ster.invalid> - 2022-09-07 08:32 -0700
    Re: Troubleshoot wireguard Mike Easter <MikeE@ster.invalid> - 2022-09-07 10:52 -0700
      Re: Troubleshoot wireguard "J.O. Aho" <user@example.net> - 2022-09-07 20:38 +0200

csiph-web