• Martin Husemann [2024-01-18 11:36]:
> > Step 3 has to be a different one: load if_wg module, to make sure wg is
> > listed as a clonable interface.
>
> Yes, indeed, and it is slightly subtle (auto-hiding by module auto-loading).
>
> I have all my router kernels running securelevl >= 1 and
k...@krot.org (Kirill Miazine) writes:
>> Maybe he still has auto_ifconfig=NO ?
>no, he didn't... but issue was if_wg not being loaded upon boot -- but
>loaded when ifconfig wg0 create was called.
The perils of the module autoloader.
On Thu, Jan 18, 2024 at 11:16:16AM +0100, Kirill Miazine wrote:
> Step 3 has to be a different one: load if_wg module, to make sure wg is
> listed as a clonable interface.
Yes, indeed, and it is slightly subtle (auto-hiding by module auto-loading).
I have all my router kernels running securelevl
• Michael van Elst [2024-01-18 10:10]:
> mar...@duskware.de (Martin Husemann) writes:
>
> >On Thu, Jan 18, 2024 at 10:23:11AM +0100, Kirill Miazine wrote:
> >> Does your custom kernel provide some wg devices initially?
>
> >No, but "ifconfig -C" lists wg as a clonable device, so
Step 3 has to be a different one: load if_wg module, to make sure wg is
listed as a clonable interface.
• Kirill Miazine [2024-01-18 08:46]:
> Hi, NetBSD users
>
> I've been setting up a NetBSD box, which has to be connected to the wider
> WireGuard network. There's a while since I managed
• Martin Husemann [2024-01-18 10:46]:
> On Thu, Jan 18, 2024 at 10:23:11AM +0100, Kirill Miazine wrote:
> > Does your custom kernel provide some wg devices initially?
>
> No, but "ifconfig -C" lists wg as a clonable device, so /etc/ifconfig.wg0
> is loaded.
Ah, of course! I overlooked that one.
mar...@duskware.de (Martin Husemann) writes:
>On Thu, Jan 18, 2024 at 10:23:11AM +0100, Kirill Miazine wrote:
>> Does your custom kernel provide some wg devices initially?
>No, but "ifconfig -C" lists wg as a clonable device, so /etc/ifconfig.wg0
>is loaded.
Maybe he still has auto_ifconfig=NO
On Thu, Jan 18, 2024 at 10:23:11AM +0100, Kirill Miazine wrote:
> Does your custom kernel provide some wg devices initially?
No, but "ifconfig -C" lists wg as a clonable device, so /etc/ifconfig.wg0
is loaded.
Martin
• Martin Husemann [2024-01-18 09:46]:
> On Thu, Jan 18, 2024 at 09:27:59AM +0100, Kirill Miazine wrote:
> >
> > Yet for some reason mine isn't being picked up -- even if I use wg0 instead
> > of wg1.
>
> Oh, sorry - I forgot the obvious part: you need to make sure your kernel
> has wg(4)
Hi, Martin
Thanks for sharing your configuration.
• Martin Husemann [2024-01-18 09:02]:
> On Thu, Jan 18, 2024 at 08:46:11AM +0100, Kirill Miazine wrote:
> > Hi, NetBSD users
> >
> > I've been setting up a NetBSD box, which has to be connected to the wider
> > WireGuard network. There's a while
On Thu, Jan 18, 2024 at 09:27:59AM +0100, Kirill Miazine wrote:
>
> Yet for some reason mine isn't being picked up -- even if I use wg0 instead
> of wg1.
Oh, sorry - I forgot the obvious part: you need to make sure your kernel
has wg(4) support - it is not part of GENERIC on most architectures
On Thu, Jan 18, 2024 at 08:46:11AM +0100, Kirill Miazine wrote:
> Hi, NetBSD users
>
> I've been setting up a NetBSD box, which has to be connected to the wider
> WireGuard network. There's a while since I managed NetBSD, so I'd like to
> ask for feedback as to whether current setup is considered
Hi, NetBSD users
I've been setting up a NetBSD box, which has to be connected to the
wider WireGuard network. There's a while since I managed NetBSD, so I'd
like to ask for feedback as to whether current setup is considered a
"proper" way of setting up WireGuard on NetBSD:
1. Create files
13 matches
Mail list logo
