Re: Wireguard woes

[Peter Miller <feurry%gmail.com@localhost>]

On Sat, Sep 27, 2025 at 1:10 PM beaker <beaker%sdf.org@localhost> wrote:

>         sudo ifconfig wg0 create
>         sudo ifconfig wg0 inet 10.2.0.2/32
>         # /etc/wg/wg0 contains just the Proton PrivateKey
>         sudo wgconfig wg0 set private-key /etc/wg/wg0
>         sudo wgconfig wg0 add peer Proton '<Proton PublicKey>' \
>           --allowed-ips=0.0.0.0/0,::/0 --endpoint=<Proton Endpoint:Port>
>         sudo ifconfig wg0 up
>     fi

I have wireguard working fine on NetBSD server and client with a
similar looking config. No experience with Proton, but I don't see
anything wrong here.

> My understanding is that changing the default route shouldn't be needed with
> wireguard and doing so via 'sudo route -f add default 10.2.0.2' consistently
> hangs the system..

try this

# change default route to the Proton servers Peer address. I'm just
guessing that it's 10.2.0.1
route change default 10.2.0.1

You might want to remove the DNS line too just while troubleshooting,
or set it to 1.1.1.1 or something first.
-- 
Thanks
Peter