[WireGuard] Troubleshooting with WireGuard
Jason A. Donenfeld
Jason at zx2c4.com
Mon Jul 11 21:14:49 CEST 2016
On Mon, Jul 11, 2016 at 5:21 PM, Daniel Kahn Gillmor
<dkg at fifthhorseman.net> wrote:
> Would it be possible to log more when the kernel is in a more vebose
> mode, or to have a module parameter that increases the logging? Not
> having to rebuild make it simpler for people experimenting with
> pre-packaged (or dkms-built) modules to just "enable debugging", which
> might produce more verbose problem reports.
> Or does anyone know of the simplest way to encourage dkms to build a
> specific module in debug mode? If so, i could try to ship a
> wireguard-dkms-debug package (which Conflicts: wireguard-dkms and
> Provides: wireguard-dkms) as an alternate option for people who don't
> want to do the build themselves.
I'd prefer that early experimenters not get used to having too much
log output from WireGuard. It's supposed to appear "stateless" to the
user, and I'm afraid that this sort of thing might encourage bad
patterns with regards to it.
I'd rather learn precisely what issues the user is facing, and see if
we can debug it from there. Maybe that approach will prove impossible,
and in the end we'll need some logging, but I think it's worth at
least trying without logs.
That said, if you intend to help with the /development/ of wireguard,
the debug logs are quite helpful, but in that situation you'll already
be building the module yourself.
More information about the WireGuard