Hello,
It looks like a misconfiguration. Combining information on wg0
configuration earlier emails:
On Thu, May 14, 2026 at 04:46:25PM +0200, Gabriele Vento wrote:
> >> wg0: flags=80c3<UP,BROADCAST,RUNNING,NOARP,MULTICAST> mtu 1300
> >> description: ...
> >> index 8 priority 0 llprio 3
> >> wgport 22670
> >> wgpubkey ...
> >> wgpeer ...
> >> wgpsk (present)
> >> wgpka 15 (sec)
> >> wgendpoint 15.204.55.83 42070
> >> tx: 7844, rx: 0
> >> wgaip 15.204.55.83/10
> >> groups: wg
> >> inet ... netmask 0xffffffff
the inet is 100.65.0.138
However I think it should be from the same network which is allowed
by wgaip option. Perhaps you should run:
ifconfig wg0 15.204.55.83/10
Once you'll be able to fix wireguard configuration using ifconfig(8),
then I would suggest to take a look at 'ifconfig wg0' output and
save information from there to etc/hostname.wg0 file.
For example, this is ifconfig wg0 output on my virtual guest I use for testing:
pf# ifconfig wg0
wg0: flags=80c3<UP,BROADCAST,RUNNING,NOARP,MULTICAST> mtu 1420
index 6 priority 0 llprio 3
wgport 4433
wgpubkey 3ni8zRYIoXgolLbnrB6bHCtNMkWKeFfwoG3bQvxHLSo=
wgpeer wVNVajQQdLKRQKghS42uaFm7YszMiA5WDz4X4gDLUkM=
tx: 0, rx: 0
wgaip 192.168.10.0/24
groups: wg
inet 192.168.10.11 netmask 0xffffff00 broadcast 192.168.10.255
and this is the content of the /etc/hostname.wg0 file which brings wg0
interface up on system boot:
pf# cat /etc/hostname.wg0
#
# wgkey comes from `openssl rand -base64 32`
#
# more details on Solene's blog here:
# https://dataswamp.org/~solene/2021-10-09-openbsd-wireguard-exit.html
#
wgkey EYR0EQVIREUFiVR25aCnSg2Z+45fcynEauiQw8Jsy+k=
#
# if wg interface is supposed to act as tunnel wgaip 0.0.0.0/0
# makes wg interface to accept all packets.
#wgpeer wVNVajQQdLKRQKghS42uaFm7YszMiA5WDz4X4gDLUkM= wgaip 0.0.0.0/0
#
# settings below make wg iface to accept 192.168.10 packets only.
wgpeer wVNVajQQdLKRQKghS42uaFm7YszMiA5WDz4X4gDLUkM= wgaip 192.168.10.0/24
inet 192.168.10.1/24
wgport 4433
up
hope it helps
regards
sashan
