Bug #11892
closedWireGuard: dpinger does not start correctly on a WireGuard gateway at boot
0%
Description
With a WireGuard interface assigned and with a gateway set dpinger does not start correctly at boot. Instead it shows as pending.
This is likely because the interface an gateway info cannot be assigned before the tunnel comes up when other static interfaces can. Resulting in:
rc.bootup: The command '/sbin/ifconfig 'tun_wg0' description 'WG0'' returned exit code '1', the output was 'ifconfig: interface tun_wg0 does not exist'
Tested in:
21.09-DEVELOPMENT (amd64) built on Wed May 05 01:04:33 EDT 2021 FreeBSD 12.2-STABLE WireGuard package 0.0.8
Updated by Christian McDonald almost 3 years ago
Fixed internally, fix will be in next PR
Updated by Christian McDonald almost 3 years ago
Updated by Jim Pingle almost 3 years ago
- Status changed from New to Feedback
- Target version deleted (
2.6.0)
Updated by Alhusein Zawi almost 3 years ago
[2.6.0-DEVELOPMENT][admin@pfSense.home.arpa]/root: ifconfig tun_wg0
tun_wg0: flags=80c1<UP,RUNNING,NOARP,MULTICAST> metric 0 mtu 1500
description: OPT2
options=80000<LINKSTATE>
inet 20.20.20.1 netmask 0xffffff00
groups: wg WireGuard
nd6 options=101<PERFORMNUD,NO_DAD>
2.6.0.a.20210527.0100
Updated by Azamat Khakimyanov almost 2 years ago
- Status changed from Feedback to Resolved
Tested on 21.05_2, 22.01 and on 22.05-BETA (built on Fri May 27 06:21:09 UTC 2022)
I saw no issue with dpinger and WireGuard gateways at boot.
I marked this Bug as resolved.