Project

General

Profile

Bug #11892

WireGuard: dpinger does not start correctly on a WireGuard gateway at boot

Added by Steve Wheeler about 1 month ago. Updated 18 days ago.

Status:
Feedback
Priority:
Normal
Assignee:
-
Category:
WireGuard
Target version:
-
Start date:
05/05/2021
Due date:
% Done:

0%

Estimated time:
Affected Version:
2.6.x
Affected Architecture:
All

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

History

#1 Updated by Christian McDonald about 1 month ago

Fixed internally, fix will be in next PR

#3 Updated by Jim Pingle 22 days ago

  • Status changed from New to Feedback
  • Target version deleted (2.6.0)

#4 Updated by Alhusein Zawi 18 days ago

[2.6.0-DEVELOPMENT][]/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

Also available in: Atom PDF