le socket. Separating
them again requires matching the contents of log messages, which is
inefficient and error-prone. Getting syslog to work in chroots can be
annoying, since it requires opening the logging socket before chrooting
(which requires support by the daemon), or providing a /dev/log sock
On Tue, 17 Mar 2020 18:12:05 + Luis Ressel wrote:
>
> If you're adding logging support, I'd prefer logs on stderr over a
> centralized legacy mechanism such as syslog. That's much more flexible;
> in particular, it makes it much easier to direct logs of different
> daemons to d
On Tue, Mar 17, 2020 at 08:37:17AM +0100, J.R. Oldroyd wrote:
> Since adding syslog support is so trivial, given the existing code
> is already designed around logging levels and given Go's clean support
> of syslog, why not just build it in so that wireguard's logging is done
>
Here's the same syslog logging files sent from git.
J.R. Oldroyd (1):
Add support for logging to syslog(3) on operating systems that support
it (i.e., non-Windows, non-Plan9).
device/logger.go| 45 ++--
device/logger_syslog.go | 112
Signed-off-by: J.R. Oldroyd
---
device/logger.go| 45 ++--
device/logger_syslog.go | 112
2 files changed, 129 insertions(+), 28 deletions(-)
create mode 100644 device/logger_syslog.go
diff --git a/device/logger.go
ned-off-by line? (Or even to Github?)
>
Will do.
> I'm curious to know: is there a reason why you prefer this to something like:
>
> `LOG_LEVEL=debug wireguard-go -f wg0 2>&1 | logger &`
>
Since adding syslog support is so trivial, given the existing code
is already
Hi JR,
Adding direct syslog support might make sense. I'll look into
integrating those files you sent, though, perhaps it'd be better if
you submitted those as a patch to the mailing list with a proper
Signed-off-by line? (Or even to Github?)
I'm curious to know: is there a reason why you prefer
On P, 2020-03-15 at 14:16 +0100, J.R. Oldroyd wrote:
> New here. Apologies if I am re-hashing something discussed before.
> I did read back a few months of this list and didn't see any relevant
> discussion.
Quite a lot of information can also be obtained via Linux Wireguard
module. wg(8) man
Hi all,
New here. Apologies if I am re-hashing something discussed before.
I did read back a few months of this list and didn't see any relevant
discussion.
Unlike many here who are providing anonymous VPN services and who
don't want logging at all, I am helping set up Wireguard in a corporate
en building should print to dmesg.
That's good to know, but not very useful in our case, because we get the
module from Fedora COPR. Moreover, I'd consider ability to log incoming
connections info-level, not debug-level logging.
-K
___
WireGuar
Hello:
For auditing purposes, I would like to be able to log the remote
endpoint IP for each wg connection on the server side. What's the best
way to do this, preferably using syslog?
Best,
-K
___
WireGuard mailing list
WireGuard@lists.zx2c4.com
11 matches
Mail list logo
