From: Marios Makassikis <mmakassikis@freebox.fr>
To: Chris Eidem <ceidem@ceidem.com>
Cc: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: Ubuntu client OpenBSD server
Date: Tue, 30 Nov 2021 10:22:29 +0100 [thread overview]
Message-ID: <CAF6XXKWbYasBFCp5-Fyqp_g-13sXbZvRmVfvve7nKwi7vH60Ng@mail.gmail.com> (raw)
In-Reply-To: <d83162a4-05bf-22f1-f8de-7ec183ed9173@ceidem.com>
On Mon, Nov 29, 2021 at 4:45 PM Chris Eidem <ceidem@ceidem.com> wrote:
>
> I have a Wireguard server set up on an OpenBSD 6.9 server with OpenBSD,
> Android, iOS and Ubuntu clients. All clients are connecting, although
> the Ubuntu clients only work when the PSK is not enabled in the wg0.conf
> file. Has anyone else seen this behavior? Is there any information I
> could provide to help figure out why the PSK isn't working on my Linux
> clients?
>
> I don't know if wg uses the system's TLS libraries, but if so, I suspect
> that the fact gnutls and libressl don't play well together may have
> something to do with it. But, that is a guess pulled from my fundament...
>
> - chris
>
wg doesn't use TLS libraries at all, so the issue is somewhere else.
Have you checked that the PSK is the same on both ends ?
Which kernel version are you using ?
Enabling debug logs on both ends may shed some light on what is
going on. On OpenBSD, enable using the command:
ifconfig wgX debug
To disable:
ifconfig wgX -debug
On Ubuntu, enable using:
echo 'module wireguard +p' > /sys/kernel/debug/dynamic_debug/control
and disable with:
echo 'module wireguard -p' > /sys/kernel/debug/dynamic_debug/control
prev parent reply other threads:[~2021-11-30 9:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-25 18:41 Chris Eidem
2021-11-30 9:22 ` Marios Makassikis [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAF6XXKWbYasBFCp5-Fyqp_g-13sXbZvRmVfvve7nKwi7vH60Ng@mail.gmail.com \
--to=mmakassikis@freebox.fr \
--cc=ceidem@ceidem.com \
--cc=wireguard@lists.zx2c4.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).