Hi,
The wg(4) man page indicates there is a "debug" option for the interface.
I can see that the DEBUG flag is set, but how to I access that debugging
information?
mini# ifconfig wg1
wg1: flags=80c7 mtu 1420
I have my OpenBSD server set up as a public Wireguard server and it's
working fine
Hi,
What is your configuration that you have a wg process running?
I'm configuring Wireguard currently and am just using the hostname.wg0,
hostname.wg1. Still struggling making OpenBSD a client to a Wireguard server,
but I think it's the server that's an issue.
Do you have a package installed
Steve Williams wrote:
> What is your configuration that you have a wg process running?
Your /etc/hostname.wg0 file should contain a line such as the following at the
end:
!/usr/local/bin/wg setconf wg0 /etc/wireguard/wg0.conf
The ! specifies a shell command - see hostname.if(5)
You will nee
What is the meaning behind the following output from security(8):
Checking root sh paths, umask values:
/etc/profile /root/.profile
Failed to find ENV in /root/.profile.
I get these daily complaints on every box where root's .profile calls out to a
shell script for some housekeeping tasks on a l
Lloyd writes:
> What is the meaning behind the following output from security(8):
>
> Checking root sh paths, umask values:
> /etc/profile /root/.profile
> Failed to find ENV in /root/.profile.
>
> I get these daily complaints on every box where root's .profile calls out to
> a shell script for
On Thu, Dec 19, 2024 at 10:48:41PM +0100, Maurice Janssen wrote:
> On Thu, Dec 19, 2024 at 09:40:20AM +1000, David Gwynne wrote:
> >
> >> On 19 Dec 2024, at 08:20, David Gwynne wrote:
> >>
> >>> On 19 Dec 2024, at 02:17, Maurice Janssen wrote:
> >>> kstat(1) shows me that there are (nearly) no e
Posting here, but will post elsewhere if this is not the right place.
Is there any desire for using kqueue natively in the wayland libraries
instead of epoll-shim? I'm sure epoll-shim is great, but I wanted to
learn to use kqueue and figured this was a good project (since I was
already working on
Steve Williams wrote:
Hi,
The wg(4) man page indicates there is a "debug" option for the interface.
I can see that the DEBUG flag is set, but how to I access that
debugging information?
mini# ifconfig wg1
wg1: flags=80c7 mtu 1420
I have my OpenBSD server set up as a public Wireguard serve
Peter Piwowarski wrote:
> Steve Williams wrote:
>
> > I can see that the DEBUG flag is set, but how to I access that
> > debugging information?
>
> You should be seeing it spam dmesg pretty voluminously.
The current implementation of Wireguard debugging leaves a bit to be
desired. Not just spam
I've been doing some testing against Wireguard and was able to get the system
in a state where it was unable to reboot via the shutdown command.
Unfortunately,
I've been unable to reproduce the issue again so far. This particular system was
running an unmodified GENERIC kernel from -current:
Open
10 matches
Mail list logo
