issues with syslogd include redirecting wg0 output to custom location

2024-09-17 Thread fuxjez
Hi, I'm experimenting with FreeBSD's 14.1's wireguard implementation. So far i've been quite satisfied with using it locally (over an unsecured network). I would like to set up a PoC using wg as a VPN provider (replacing openvpn) next. Before opening wireguard endpoints up for global connect

Re: issues with syslogd include redirecting wg0 output to custom location

2024-09-17 Thread fuxjez
/ramdisk_log/wireguard.log does redirect the logstream perfectly. Thank you for your suggestion :) Regards, ruben On 9/17/24 14:09, Miroslav Lachman wrote: On 17/09/2024 13:06, fuxjez wrote: [..] and have since attempted to redirect the "wg0" logs to /var/ ramdisk_log/wireguard.log by u

Re: APU1 bricked on stable/14 - solved

2024-10-07 Thread fuxjez
Hi, I've included the dmesg from my apu1d device below. Regards, ruben On 10/6/24 16:11, Warner Losh wrote: Great. Just need the APU1 now. Warner On Sun, Oct 6, 2024, 7:56 AM Karl Denninger > wrote: ---<>--- Copyright (c) 1992-2023 The FreeBSD Project. Copyrig

Re: issues with syslogd include redirecting wg0 output to custom location

2024-09-18 Thread fuxjez
Hi, I ended up replacing : *.notice;authpriv.none;kern.debug;lpr.info;mail.crit;news.err /var/log/messages with !-wg0 *.notice;authpriv.none;kern.debug;lpr.info;mail.crit;news.err /var/log/messages !wg0 in /etc/syslog.conf and placing this: # Log wgX messages :msg, ereregex, "wg[0-9]{1,

Re: issues with syslogd include redirecting wg0 output to custom location

2024-09-19 Thread fuxjez
Hi Joachim/Steffen, That specific check was causing issues some time ago as well, removed it from my mail setup. Thanks for your feedback :) ruben On 9/19/24 10:17, Joachim Durchholz wrote: On 19.09.24 01:09, Steffen Nurpmeso wrote: Ha. Steffen Nurpmeso wrote in   <20240918225906.Npft_PNY

Controlling verbosity of wireguard logs

2024-09-19 Thread fuxjez
Hi List, Somebody managed to get Wireguard logging running vebosely on 14.1? I've tried setting the LOG_LEVEL (mentioned in the wg 8 manpage, albeit directed at "userspace implementations") to debug, but I wasn't able to identify any ip information (for instance) looking at the debug informat