[Bug 253254] WireGuard(wg) produces a lot of error messages for inactive devices

[bugzilla-noreply at freebsd.org]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=253254

            Bug ID: 253254
           Summary: WireGuard(wg) produces a lot of error messages for
                    inactive devices
           Product: Base System
           Version: CURRENT
          Hardware: Any
                OS: Any
            Status: New
          Severity: Affects Many People
          Priority: ---
         Component: kern
          Assignee: bugs at FreeBSD.org
          Reporter: gbe at FreeBSD.org

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.

-- 
You are receiving this mail because:
You are the assignee for the bug.