From owner-freebsd-net@FreeBSD.ORG Wed Apr 1 10:13:51 2015 Return-Path: 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 D14C177D for ; Wed, 1 Apr 2015 10:13:51 +0000 (UTC) Received: from elsa.codelab.cz (elsa.codelab.cz [94.124.105.4]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 8B3713A1 for ; Wed, 1 Apr 2015 10:13:51 +0000 (UTC) Received: from elsa.codelab.cz (localhost [127.0.0.1]) by elsa.codelab.cz (Postfix) with ESMTP id A56492842F; Wed, 1 Apr 2015 12:13:42 +0200 (CEST) Received: from illbsd.quip.test (ip-89-177-50-74.net.upcbroadband.cz [89.177.50.74]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by elsa.codelab.cz (Postfix) with ESMTPSA id 6545628428; Wed, 1 Apr 2015 12:13:41 +0200 (CEST) Message-ID: <551BC4D5.9010006@quip.cz> Date: Wed, 01 Apr 2015 12:13:41 +0200 From: Miroslav Lachman <000.fbsd@quip.cz> User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:35.0) Gecko/20100101 Firefox/35.0 SeaMonkey/2.32 MIME-Version: 1.0 To: Yuri , net@freebsd.org Subject: Re: tap(4): will it be more reasonable if it preserved UP/DOWN state, when closed? References: <551B3021.4050206@rawbw.com> In-Reply-To: <551B3021.4050206@rawbw.com> Content-Type: text/plain; charset=ISO-8859-1; 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 01 Apr 2015 10:13:51 -0000 Yuri wrote on 04/01/2015 01:39: > 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? Doesn't sysctl net.link.tap.up_on_open=1 fix your problem? Miroslav Lachman