From owner-freebsd-virtualization@freebsd.org Mon Feb 13 12:38:04 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 EBA00CD1B69 for ; Mon, 13 Feb 2017 12:38:04 +0000 (UTC) (envelope-from 000.fbsd@quip.cz) Received: from elsa.codelab.cz (elsa.codelab.cz [94.124.105.4]) (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 AB09E1D88 for ; Mon, 13 Feb 2017 12:38:04 +0000 (UTC) (envelope-from 000.fbsd@quip.cz) Received: from elsa.codelab.cz (localhost [127.0.0.1]) by elsa.codelab.cz (Postfix) with ESMTP id 64EBC284CF; Mon, 13 Feb 2017 13:37:56 +0100 (CET) Received: from illbsd.quip.test (ip-86-49-16-209.net.upcbroadband.cz [86.49.16.209]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by elsa.codelab.cz (Postfix) with ESMTPSA id BAF09284D4; Mon, 13 Feb 2017 13:37:55 +0100 (CET) Subject: Re: tap interfaces disappears after bhyve guests shutdowns To: "C. L. Martinez" , freebsd-virtualization@freebsd.org References: <20170213120938.hr3zu7flnm33v3zn@scotland.uxdom.org> From: Miroslav Lachman <000.fbsd@quip.cz> Message-ID: <58A1A8A3.3030603@quip.cz> Date: Mon, 13 Feb 2017 13:37:55 +0100 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:42.0) Gecko/20100101 Firefox/42.0 SeaMonkey/2.39 MIME-Version: 1.0 In-Reply-To: <20170213120938.hr3zu7flnm33v3zn@scotland.uxdom.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.23 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: Mon, 13 Feb 2017 12:38:05 -0000 C. L. Martinez wrote on 2017/02/13 13:09: > Why when a bhyve guest shutdowns or reboot tap interfaces goes down and lost IP assigned address?. I need to use same tap interface for several guests and assign an IP to this tap interface to act as a router for these guests. > > How can I do a "persistent tap" interface?? I think you need this sysctl: # sysctl -d net.link.tap.up_on_open net.link.tap.up_on_open: Bring interface up when /dev/tap is opened