From owner-freebsd-net@FreeBSD.ORG  Tue Mar 31 23:39:16 2015
Return-Path: <owner-freebsd-net@FreeBSD.ORG>
Delivered-To: net@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 0BC14EFE
 for <net@freebsd.org>; Tue, 31 Mar 2015 23:39:16 +0000 (UTC)
Received: from shell1.rawbw.com (shell1.rawbw.com [198.144.192.42])
 by mx1.freebsd.org (Postfix) with ESMTP id D0C2AAA7
 for <net@freebsd.org>; Tue, 31 Mar 2015 23:39:15 +0000 (UTC)
Received: from yuri.doctorlan.com (c-50-184-63-128.hsd1.ca.comcast.net
 [50.184.63.128]) (authenticated bits=0)
 by shell1.rawbw.com (8.14.9/8.14.9) with ESMTP id t2VNdE8J051627
 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO)
 for <net@freebsd.org>; Tue, 31 Mar 2015 16:39:14 -0700 (PDT)
 (envelope-from yuri@rawbw.com)
X-Authentication-Warning: shell1.rawbw.com: Host
 c-50-184-63-128.hsd1.ca.comcast.net [50.184.63.128] claimed to be
 yuri.doctorlan.com
Message-ID: <551B3021.4050206@rawbw.com>
Date: Tue, 31 Mar 2015 16:39:13 -0700
From: Yuri <yuri@rawbw.com>
User-Agent: Mozilla/5.0 (X11; FreeBSD amd64;
 rv:31.0) Gecko/20100101 Thunderbird/31.5.0
MIME-Version: 1.0
To: net@freebsd.org
Subject: tap(4): will it be more reasonable if it preserved UP/DOWN state,
 when closed?
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
X-BeenThere: freebsd-net@freebsd.org
X-Mailman-Version: 2.1.18-1
Precedence: list
List-Id: Networking and TCP/IP with FreeBSD <freebsd-net.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-net>,
 <mailto:freebsd-net-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-net/>
List-Post: <mailto:freebsd-net@freebsd.org>
List-Help: <mailto:freebsd-net-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-net>,
 <mailto:freebsd-net-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 31 Mar 2015 23:39:16 -0000

Currently tap(4) device gets to 'down' state when the last process 
closes it, regardless of the original 'up/down' state.
Will it be reasonable to modify this behavior and keep this bit 
'was_up_before_open', and leave it 'up' if it was 'up' when it was first 
opened?

Practically speaking, I set it up in rc.conf to be 'up' with the 
particular IP, but it goes to 'down' state  when VirtualBox closes it.

If tap(4) can be 'up' without users, there shouldn't be any problem in 
leaving it 'up' after use as well?

Yuri