From owner-freebsd-virtualization@freebsd.org Sat Dec 30 06:11:38 2017 Return-Path: Delivered-To: freebsd-virtualization@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id A8B5CEAC04E for ; Sat, 30 Dec 2017 06:11:38 +0000 (UTC) (envelope-from shawn.webb@hardenedbsd.org) Received: from mail-qk0-x230.google.com (mail-qk0-x230.google.com [IPv6:2607:f8b0:400d:c09::230]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 5BC866FE73 for ; Sat, 30 Dec 2017 06:11:38 +0000 (UTC) (envelope-from shawn.webb@hardenedbsd.org) Received: by mail-qk0-x230.google.com with SMTP id v188so27397209qkh.11 for ; Fri, 29 Dec 2017 22:11:38 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=hardenedbsd-org.20150623.gappssmtp.com; s=20150623; h=date:from:to:subject:message-id:mime-version:content-disposition :user-agent; bh=hB5m2gAwRmW1ixB7R9lgmIHq0lQzcOc/OmldW5o5jXw=; b=Xq3yOWYcMcU4ueVGOCBDXhTAsZ1Zge2pLtkF9wqA7r7QudG2ofqFuxN/e6Abe5m/7M dVnW0kc+BzI7n1W3iVNDKKC+29RQwCUlTRdO+k6XM8FslJZHzhdJLZ2AOm26Gag0LaEr ZGPQawo9E4cSeDNvL326dVDvXgixfKcs2iT2LmFF91+M7N2QfbyrKozqm/UgNf7Kq1V5 cBhcZv1w7MTnG+J0mdUBPuxnbE6ZNSOuH1pnsFiYpk6QSjCsNqkZVUmtREs6qng1ZiE9 O685kbZP9iiE7m5QcnaJGmyOplJc9Y3E+X00kv6uFsvHiNyBl9jG4B9xIahegWEtXKVu CWJg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:subject:message-id:mime-version :content-disposition:user-agent; bh=hB5m2gAwRmW1ixB7R9lgmIHq0lQzcOc/OmldW5o5jXw=; b=CaqHs1+UXcxdY8BhypEov+etCS9kss6QiHjWoUHv+AZjD0LJdxkRAhKDuMWkFjeArh M4s1aPtqjyuxxMcUpwMCnrN27pPjWQW2eYzJC9nZRl6r1GfrYsyN3njWZKM2Z4b45FH+ Z5n6gA1JWG1klq/CwLYGR7grOZKTe/117LDcpeubBCtNuBTP7aE3NHn5jcQ1tu20higC 9NFfCVnS8riW2HJihHBSg6OJdrjnWlKRGPQNYl99BoqIVldG36ODHSoMjUD8gtqEj+tZ KSHktzdRYCEbYsbkCi9o0Q/j9Bf1J//CWatSi28QR/jCne2uITGqvVvjIsgD6BEj9fsa eXfQ== X-Gm-Message-State: AKGB3mKS7SbjyukqVveDCUBG+gGzNMVmY1gEnN2TWbrmzIF9UNv7brII wrZAF2Qs03mMpzpvzAHBtZlrOtDpVwVVsILH4QTryvkpbFvDDPKFF3pvfMd+1Har1XOBDg3Z+1z E3E8uVmteWYNIXuCR1bV635Qq/CER9zjsjzRRK0ya4wnuh+TscWX9y8TQwmtkS9am/WfIeI2Uly Fhn9x/CVsoSPBHI2Mc X-Google-Smtp-Source: ACJfBotnREgOfPlha+z+8Ixroqk1vxL5CRJ7lO2fZXVvaAhYf+FKWkNyECLGylE+eTxz2fkasF8cuA== X-Received: by 10.55.221.20 with SMTP id n20mr49207796qki.181.1514614296861; Fri, 29 Dec 2017 22:11:36 -0800 (PST) Received: from mutt-hbsd (xanaduregio.emeraldonion.org. [23.129.64.102]) by smtp.gmail.com with ESMTPSA id f34sm20024411qtb.63.2017.12.29.22.11.31 for (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Fri, 29 Dec 2017 22:11:36 -0800 (PST) Date: Sat, 30 Dec 2017 01:10:53 -0500 From: Shawn Webb To: freebsd-virtualization@freebsd.org Subject: Unable to use renamed tap device Message-ID: <20171230061053.ui4wc4yqw7szsbuw@mutt-hbsd> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="tpupydl7rq2r67qv" Content-Disposition: inline X-Operating-System: FreeBSD mutt-hbsd 12.0-CURRENT FreeBSD 12.0-CURRENT X-PGP-Key: http://pgp.mit.edu/pks/lookup?op=vindex&search=0x6A84658F52456EEE User-Agent: NeoMutt/20171208 X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: "Discussion of various virtualization techniques FreeBSD supports." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 30 Dec 2017 06:11:38 -0000 --tpupydl7rq2r67qv Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Hey All, I'm in the process of reorganizing my bhyve setup on my development laptop. I'd like to have rename the tap devices to match the name of the VM so that it's easier to keep track of. Otherwise, I have to keep a spreadsheet of (tap3 -> win10-vm, tap4 -> fbsd-vm). It appears bhyve doesn't attach renamed tap devices. Here's the steps I used: ifconfig bridge0 create ifconfig tap0 create name fbsd-01 ifconfig bridge0 addm em0 addm fbsd-01 up sh /usr/share/examples/bhyve/vmrun.sh -t fbsd-01 [normal vmrun.sh arguments= here] (In this example, em0 is the physical network device connected to the LAN. I want to share em0 with the host and the guest via the bridge.) The net.link.tap.up_on_open sysctl node is set to 1. Normally, when bhyve starts up (with tap0 instead of fbsd-01), it opens the tap device and UPs it. I'm not seeing that same behavior with a renamed tap interface: $ ifconfig ld-03_01 ld-03_01: flags=3D8903 metric 0 mtu= 1500 options=3D80000 ether 00:bd:df:e9:f6:04 groups: tap media: Ethernet autoselect status: no carrier nd6 options=3D29 So, it seems to me that bhyve doesn't like it when tap devices are renamed. Can anyone shed some light on this? Thanks, --=20 Shawn Webb Cofounder and Security Engineer HardenedBSD Tor-ified Signal: +1 443-546-8752 GPG Key ID: 0x6A84658F52456EEE GPG Key Fingerprint: 2ABA B6BD EF6A F486 BE89 3D9E 6A84 658F 5245 6EEE --tpupydl7rq2r67qv Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEEKrq2ve9q9Ia+iT2eaoRlj1JFbu4FAlpHLesACgkQaoRlj1JF bu4VrRAArGaSuhDPhy6J21kHF7cPCJvFQxXvIqGzA1o/GaPx56EI6KpRc4Urm85Q uhpzWWV/c6SmUSgqGwIFmQI3VNlYfkn3yELKVzLT9ohxdsm/CfctFWhGxfzl4166 am0XjNj7f6wYPhqrY7i7KXzWy4BzAJiFuppDurUWIU4J8OslPr6jHLBiUo7I1lUO JVR1x6z68wgETK/3TOJhi3RExPuozCU0Sb//bdZmv5lRiqF+Tk6L3G3Gg57R2Sen y3z4V/pYJGeSFLGNgROXQv7H8p/7IW2p/y+mz2msVT1ZF/JJ+/Bm/+ScQOWDRSPs esiIvHuMDPqGb93yS2t2QX/ZERqfOq3QAtIdJzRd1dHUuVjM3qwYwngkgu9bU1E2 kdMT/yaR9HaTDNU58ueZDQcipOMu1QSzzAfhgzmadFXbsQySQnT1jrMfV5jfeTwY T9BPnine6W1f1NKvl3L2wrChzdyF/4cNdluT7y2si6p1TIeR1HLwTxMkC5ZSgPK0 1i3igLEEX0aq2tR9TkVo0rPWvGqDAEGVCJmwp5Hwu8+7vIvtHpi4/4+vLkahbA4c vJ4S45mMqEPBnQcY26QZ1NH9li/YUqDyHksQ2H22y8LFpeLtPLi0NfyDThIYrsaM k2RmUdp8iOG1e79S/Iqu4O1bsJI2kj82NMod9E5YnaOJl4NNIxY= =BB1k -----END PGP SIGNATURE----- --tpupydl7rq2r67qv--