Bug 253254

Summary:	WireGuard(wg) produces a lot of error messages for inactive devices
Product:	Base System	Reporter:	Gordon Bergling <gbe>
Component:	kern	Assignee:	Bernhard Froehlich <decke>
Status:	Closed Overcome By Events
Severity:	Affects Many People	CC:	decke, emaste, liuxyon, zarychtam
Priority:	---
Version:	CURRENT
Hardware:	Any
OS:	Any

Description Gordon Bergling freebsd_committer

2021-02-04 16:53:30 UTC

I have experienced a little bit with wg(4) and setup to inactive interfaces on a recent -CURRENT. The interfaces are configured as follows,

wg0: flags=8080e1<UP,RUNNING,NOARP,MULTICAST> metric 0 mtu 1420
	options=880000<LINKSTATE>
	inet6 fe80::dea6:32ff:fe9d:64c4%wg0 prefixlen 64 scopeid 0x4
	inet 46.252.18.5 netmask 0xff000000
	groups: wg
	media: Ethernet autoselect (25GBase-ACC <full-duplex>)
	status: active
	nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL>
wg1: flags=8080a0<NOARP,MULTICAST> metric 0 mtu 1420
	options=880000<LINKSTATE>
	groups: wg
	listen-port: 54321
	public-key:  7lWtsDdqaGB3EY9WNxRN3hVaHMtu1zXw71+bOjNOVUw=
	media: Ethernet autoselect (25GBase-ACC <full-duplex>)
	status: active
	nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL>

The console is full of the following output
peer not found - dropping 0xffffa000c7b94800
matchaddr failed
peer not found - dropping 0xffffa00052c27500
matchaddr failed
peer not found - dropping 0xffffa00052d61500
matchaddr failed
peer not found - dropping 0xffffa000d68b7c00
matchaddr failed
peer not found - dropping 0xffffa00004aba400
matchaddr failed
peer not found - dropping 0xffffa00052dbcb00
matchaddr failed
peer not found - dropping 0xffffa000f29b0500
matchaddr failed
peer not found - dropping 0xffffa00004aba000
matchaddr failed
peer not found - dropping 0xffffa0001aa08e00

This output is generated about every minute for each interface.

The device driver should a least print which error belongs to what interface. And for no configured peer, no error message should be printed at all.

Comment 1 liuxyon 2021-02-21 10:38:22 UTC

i using wireguard in pfsense 2.5 and 2.6 base freebsd 12.2 log show the same:

Feb 21 18:16:58	kernel		matchaddr failed
Feb 21 18:16:57	kernel		matchaddr failed
Feb 21 18:16:56	kernel		matchaddr failed



submited in here

https://forum.netgate.com/topic/160897/crash-report-2-5-0-rc/6

Comment 2 Bernhard Froehlich freebsd_committer

2021-03-23 20:34:54 UTC

This problem was fixed in the new kernel module available from the Portstree in net/wireguard-kmod

Comment 3 commit-hook freebsd_committer

2024-09-02 10:50:15 UTC

A commit in branch main references this bug:

URL: https://cgit.FreeBSD.org/ports/commit/?id=bd13085ebce3b0f374357344c35c6a2247bd1f82

commit bd13085ebce3b0f374357344c35c6a2247bd1f82
Author:     Alex Dupre <ale@FreeBSD.org>
AuthorDate: 2024-09-02 10:48:50 +0000
Commit:     Alex Dupre <ale@FreeBSD.org>
CommitDate: 2024-09-02 10:49:50 +0000

    mail/roundcube: update to 1.6.9 release.

    PR:             253254
    Submitted by:   Fabian Wenk <fabian@wenks.ch>

 mail/roundcube/Makefile | 2 +-
 mail/roundcube/distinfo | 6 +++---
 2 files changed, 4 insertions(+), 4 deletions(-)

Comment 4 commit-hook freebsd_committer

2024-09-02 11:03:19 UTC

A commit in branch 2024Q3 references this bug:

URL: https://cgit.FreeBSD.org/ports/commit/?id=9a8a08ad1a55c5ffb65a0bee11aba0f5044a4dd5

commit 9a8a08ad1a55c5ffb65a0bee11aba0f5044a4dd5
Author:     Alex Dupre <ale@FreeBSD.org>
AuthorDate: 2024-09-02 10:48:50 +0000
Commit:     Alex Dupre <ale@FreeBSD.org>
CommitDate: 2024-09-02 11:02:06 +0000

    mail/roundcube: update to 1.6.9 release.

    PR:             253254
    Submitted by:   Fabian Wenk <fabian@wenks.ch>

    (cherry picked from commit bd13085ebce3b0f374357344c35c6a2247bd1f82)

 mail/roundcube/Makefile | 2 +-
 mail/roundcube/distinfo | 6 +++---
 2 files changed, 4 insertions(+), 4 deletions(-)