From nobody Sat Dec 7 22:45:07 2024 X-Original-To: virtualization@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4Y5NW01rrCz5gKhF for ; Sat, 07 Dec 2024 22:45:16 +0000 (UTC) (envelope-from herbert@gojira.at) Received: from mail.bsd4all.net (mail.bsd4all.net [94.130.200.20]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature ECDSA (P-384) client-digest SHA384) (Client CN "mail.bsd4all.net", Issuer "E6" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4Y5NVy5fS6z4Qlv for ; Sat, 7 Dec 2024 22:45:14 +0000 (UTC) (envelope-from herbert@gojira.at) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=gojira.at header.s=mail202005 header.b=ypa9aQwL; spf=pass (mx1.freebsd.org: domain of herbert@gojira.at designates 94.130.200.20 as permitted sender) smtp.mailfrom=herbert@gojira.at; dmarc=none Date: Sat, 7 Dec 2024 23:45:07 +0100 DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=gojira.at; s=mail202005; t=1733611507; bh=YsnK8uFpxKT+FCcO/Gg7OU83SESqYJX5CpaETVPUM/M=; h=Date:From:To:Subject:Message-ID:MIME-Version:Content-Type; b=ypa9aQwLfX46Hge53RQPjHSmWMaQKs4jWRyElS+L+LYeUin9CMKEq7PDjFD4KWOf5 ydaTnGMTUyQANHv73mqI5IIv3LP82cZY3NAjEdhh8XeYMZOOT6RAoeDQabTvsKSQkZ YqgiHESlVLHfCvJ8OhF5R32/W0zT/Hxsrl6f2LHFOM/mhwbZtgn00HL6cJOcPI90ux bHXoZunp1EcAzqyflp48ezwO31K7CR4N/jiSLROL+vcCD07E+XMKIV8jZk9Qma1CJG g3BVZjB35IuAN6niZUmLIZvIe38wAFTfgH76nTAkszToMr16KSImOwpxlu5qKPhj3v BGYa3QekqeWzA== From: "Herbert J. Skuhra" To: virtualization@freebsd.org Subject: Re: Tap device problem on FreeBSD 14.2-RELEASE Message-ID: References: <0fc1d487-b254-4c64-9db1-a982169924e4@acm.org> List-Id: Discussion List-Archive: https://lists.freebsd.org/archives/freebsd-virtualization List-Help: List-Post: List-Subscribe: List-Unsubscribe: X-BeenThere: freebsd-virtualization@freebsd.org Sender: owner-freebsd-virtualization@FreeBSD.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <0fc1d487-b254-4c64-9db1-a982169924e4@acm.org> X-Spamd-Result: default: False [-3.50 / 15.00]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_SHORT(-1.00)[-1.000]; R_SPF_ALLOW(-0.20)[+ip4:94.130.200.20]; R_DKIM_ALLOW(-0.20)[gojira.at:s=mail202005]; MIME_GOOD(-0.10)[text/plain]; MIME_TRACE(0.00)[0:+]; RCPT_COUNT_ONE(0.00)[1]; ASN(0.00)[asn:24940, ipnet:94.130.0.0/16, country:DE]; MISSING_XM_UA(0.00)[]; FROM_HAS_DN(0.00)[]; RCVD_COUNT_ZERO(0.00)[0]; DMARC_NA(0.00)[gojira.at]; FROM_EQ_ENVFROM(0.00)[]; ARC_NA(0.00)[]; TO_DN_NONE(0.00)[]; MLMMJ_DEST(0.00)[virtualization@freebsd.org]; TO_MATCH_ENVRCPT_ALL(0.00)[]; DKIM_TRACE(0.00)[gojira.at:+] X-Rspamd-Queue-Id: 4Y5NVy5fS6z4Qlv X-Spamd-Bar: --- On Sat, Dec 07, 2024 at 04:37:31PM -0500, Thomas Laus wrote: > I used FreeBSD-update to go from 14.1-RELEASE to 14.2-RELEASE and there is > an issue with creating and using the tap device. The device doesn't get > created during the boot process and can't be created or used after the > system is up. The UPDATING file has just one entry concerning the tap > device and that is change the 'tap' name in all configuration files with > 'tuntap'. I did that and get an invalid device reply. I installed the > latest package for vm-bhyve which did not make any difference. I also > deleted /usr/obj/* and checked out a fresh /usr/src and rebuilt > FreeBSD-14.2-RELEASE from source without anything working differently. I guess you are misreading UPDATING (20190507?). "device tuntap" is included in GENERIC since 251a32b5b2bab (2019!). So this entry is not relevant for the 14.1-RELEASE to 14.2-RELEASE update. What files have you modified? > If anyone has a working tap device using FreeBSD 14.2-RELEASE, I would > appreciate you sharing your bhyve portions of /etc/rc.conf, /etc/sysctl.conf > and /boot/loader.conf files. You should be able to create tun/tap interfaces with "ifconfig tun0 create" or "ifconfig tap0 create". What error do you get?