From owner-freebsd-virtualization@FreeBSD.ORG Wed Oct 22 21:54:44 2014 Return-Path: Delivered-To: freebsd-virtualization@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 60F61A3B; Wed, 22 Oct 2014 21:54:44 +0000 (UTC) Received: from alto.onthenet.com.au (alto.OntheNet.com.au [203.13.68.12]) by mx1.freebsd.org (Postfix) with ESMTP id 23116A09; Wed, 22 Oct 2014 21:54:43 +0000 (UTC) Received: from dommail.onthenet.com.au (dommail.OntheNet.com.au [203.13.70.57]) by alto.onthenet.com.au (Postfix) with ESMTP id 10FD11268C; Thu, 23 Oct 2014 07:54:36 +1000 (EST) Received: from Peter-Grehans-MacBook-Pro-2.local ([64.245.0.210]) by dommail.onthenet.com.au (MOS 4.4.4-GA) with ESMTP id BZE35732 (AUTH peterg@ptree32.com.au); Thu, 23 Oct 2014 07:54:35 +1000 Message-ID: <54482799.8080003@freebsd.org> Date: Wed, 22 Oct 2014 14:54:33 -0700 From: Peter Grehan User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:24.0) Gecko/20100101 Thunderbird/24.6.0 MIME-Version: 1.0 To: Allan Jude Subject: Re: bhyve tapN additions References: <20141022140934.GA367@potato.growveg.org> <20141022141232.36446387.74087.1991@gmail.com> <20141022141631.GB367@potato.growveg.org> <5447C7EB.4060105@freebsd.org> In-Reply-To: <5447C7EB.4060105@freebsd.org> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-virtualization@freebsd.org X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.18-1 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: Wed, 22 Oct 2014 21:54:44 -0000 Hi Allan, > The tap device can also be created automatically by bhyve, make sure you > specify a different tap device for each instance of bhyve. That may require some devd scripting to get it to be added to a bridge group. We're looking at having the bridge interface have a cloneable tap-style interface so this step can be avoided i.e. point bhyve at a /dev/bridgeN device, and it will automatically become a part of that bridge. later, Peter.