NetBSD Problem Report #60464

From www@netbsd.org  Sun Jul 19 22:08:21 2026
Return-Path: <www@netbsd.org>
Received: from mail.netbsd.org (mail.netbsd.org [199.233.217.200])
	(using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)
	 key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256
	 client-signature RSA-PSS (2048 bits) client-digest SHA256)
	(Client CN "mail.netbsd.org", Issuer "YR2" (not verified))
	by mollari.NetBSD.org (Postfix) with ESMTPS id BE4001A923B
	for <gnats-bugs@gnats.NetBSD.org>; Sun, 19 Jul 2026 22:08:21 +0000 (UTC)
Message-Id: <20260719220820.B1B481A923C@mollari.NetBSD.org>
Date: Sun, 19 Jul 2026 22:08:20 +0000 (UTC)
From: campbell+netbsd@mumble.net
Reply-To: campbell+netbsd@mumble.net
To: gnats-bugs@NetBSD.org
Subject: x86/XEN3_DOMU kernel missing ipsecif(4)
X-Send-Pr-Version: www-1.0
X-From4GNATS: "campbell+netbsd@mumble.net via gnats" <gnats-admin@NetBSD.org>

>Number:         60464
>Category:       port-xen
>Synopsis:       x86/XEN3_DOMU kernel missing ipsecif(4)
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    port-xen-maintainer
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Sun Jul 19 22:10:01 +0000 2026
>Originator:     Taylor R Campbell
>Release:        current, 11, 10, 9
>Organization:
The XenIPSEC Foundation, Inc.
>Environment:
>Description:
GENERIC and XEN3_DOM0 have `pseudo-device ipsecif', but XEN3_DOMU does not.

It does have options IPSEC -- just not the ipsecif(4) interface.
>How-To-Repeat:
ifconfig ipsec0 create
>Fix:
+pseudo-device ipsecif

Maybe sync other things with GENERIC too?

Home	PR Database Search