From: Kristof Provost Date: Wed, 29 Jun 2022 19:40:16 +0200 Message-ID: In-Reply-To: <2a5bf6c9-c54a-06bb-9649-f19ff5f2be31@...1227...> References: <20220628162848.20103-1-kprovost@...2661...> <2a5bf6c9-c54a-06bb-9649-f19ff5f2be31@...1227...> MIME-Version: 1.0 Subject: Re: [Openvpn-devel] [PATCH DCO]: FreeBSD DCO support List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable To: Arne Schwabe Cc: openvpn-devel On 29 Jun 2022, at 17:15, Arne Schwabe wrote: > Am 28.06.22 um 18:28 schrieb Kristof Provost via Openvpn-devel: >> Hi, >> >> Here's the most recent version of the FreeBSD DCO patch. >> This is based on top of the dco branch, at >> 480fa1c983aba9b0790ea94df209e1686f08336b. >> >> Relatedly, the kernel side of that support has just landed in FreeBSD's >> repo: https://cgit.freebsd.org/src/commit/?id=3Dab91feabcc6f9da21d5c7502= 8153af16d06e679a > > I tested this on top of Antonios branch but got an error when connecting = from a test client: > > 2022-06-29 17:10:57 us=3D506086 lethe/192.168.188.134:61923 dco_new_peer:= peer-id 0, fd 7 > 2022-06-29 17:10:57 us=3D506125 lethe/192.168.188.134:61923 Failed to cre= ate new peer 51 > 2022-06-29 17:10:57 us=3D506137 lethe/192.168.188.134:61923 Cannot add pe= er to DCO: Operation not permitted > > > Any idea why I might get a permission denied from the kernel there? > The first thing to note here is that the =E2=80=98Operation not permitted= =E2=80=99 error is misleading. That=E2=80=99s produced based on the return = value of dco_new_peer(), which is going to be -1. The line above it has the= errno, which is 51 or ENETUNREACH. I suspect this is happening because you=E2=80=99re using ipv6_ipv4mapping (= or sysctl net.inet6.ip6.v6only=3D0). Presumably that indicates a bug on my = side, but can you see if disabling that helps? Br, Kristof