From owner-freebsd-virtualization@FreeBSD.ORG  Wed Oct 22 14:09:49 2014
Return-Path: <owner-freebsd-virtualization@FreeBSD.ORG>
Delivered-To: freebsd-virtualization@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115])
 (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by hub.freebsd.org (Postfix) with ESMTPS id 1E00CCDA
 for <freebsd-virtualization@freebsd.org>; Wed, 22 Oct 2014 14:09:49 +0000 (UTC)
Received: from potato.growveg.org (potato.growveg.org [62.49.247.163])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id CFF40D63
 for <freebsd-virtualization@freebsd.org>; Wed, 22 Oct 2014 14:09:48 +0000 (UTC)
Received: from john by potato.growveg.org with local (Exim 4.84 (FreeBSD))
 (envelope-from <john@potato.growveg.org>) id 1XgwbW-0000HH-Hf
 for freebsd-virtualization@freebsd.org; Wed, 22 Oct 2014 15:09:34 +0100
Date: Wed, 22 Oct 2014 15:09:34 +0100
From: John <freebsd-lists@potato.growveg.org>
To: freebsd-virtualization@freebsd.org
Subject: bhyve tapN additions
Message-ID: <20141022140934.GA367@potato.growveg.org>
Reply-To: freebsd-lists@freebsd.org
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.5.23 (2014-03-12)
Sender: John <john@potato.growveg.org>
X-SA-Exim-Connect-IP: <locally generated>
X-SA-Exim-Mail-From: john@potato.growveg.org
X-SA-Exim-Scanned: No (on potato.growveg.org); SAEximRunCond expanded to false
X-BeenThere: freebsd-virtualization@freebsd.org
X-Mailman-Version: 2.1.18-1
Precedence: list
List-Id: "Discussion of various virtualization techniques FreeBSD supports."
 <freebsd-virtualization.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-virtualization>, 
 <mailto:freebsd-virtualization-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-virtualization/>
List-Post: <mailto:freebsd-virtualization@freebsd.org>
List-Help: <mailto:freebsd-virtualization-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization>, 
 <mailto:freebsd-virtualization-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 22 Oct 2014 14:09:49 -0000

Hi all,

I couldn't see the following answered clearly in the literature, so I'll 
ask it here. 

When a freeBSD host is running a [anything] guest, a tap interface needs to be
created. Let's say I've done all this:

# ifconfig tap0 create
# sysctl net.link.tap.up_on_open=1
net.link.tap.up_on_open: 0 -> 1
# ifconfig bridge0 create
# ifconfig bridge0 addm igb0 addm tap0
# ifconfig bridge0 up

I want to add another tap, I don't want to restart the host. If I do

# ifconfig bridge0 addm tap1

then configure another vm to use tap1, can I expect it to work? Or, If I want 2
vns with 2 taps, do I need to do this:

# ifconfig bridge0 create
# ifconfig bridge0 addm igb0 addm tap0 addm tap1
# ifconfig bridge0 up

The reason I ask, is because I'm expecting a freebsd vm to work on tap1, and it's 
not.

thanks,
-- 
John