From owner-freebsd-net@freebsd.org Fri Nov 24 07:25:22 2017 Return-Path: Delivered-To: freebsd-net@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 73667DBBA0E for ; Fri, 24 Nov 2017 07:25:22 +0000 (UTC) (envelope-from ml@netfence.it) Received: from smtp208.alice.it (smtp208.alice.it [82.57.200.104]) by mx1.freebsd.org (Postfix) with ESMTP id 0E27868BEA for ; Fri, 24 Nov 2017 07:25:21 +0000 (UTC) (envelope-from ml@netfence.it) Received: from soth.ventu (80.182.75.25) by smtp208.alice.it (8.6.060.28) id 5A0BFDF101B0763C; Fri, 24 Nov 2017 08:24:39 +0100 Received: from alamar.ventu (alamar.local.netfence.it [10.1.2.18]) by soth.ventu (8.15.2/8.15.2) with ESMTP id vAO7OaNv052661; Fri, 24 Nov 2017 08:24:37 +0100 (CET) (envelope-from ml@netfence.it) X-Authentication-Warning: soth.ventu: Host alamar.local.netfence.it [10.1.2.18] claimed to be alamar.ventu Subject: [SOLVED] Re: bridge0 not working when cable disconnected To: Eugene Grosbein , freebsd-net@freebsd.org References: <59452bf1-25fb-970d-1d8d-5ca1463da4fd@netfence.it> <5A0DD27A.3010304@grosbein.net> From: Andrea Venturoli Message-ID: <17132d5f-0708-04a4-9a82-3a1afb49d19b@netfence.it> Date: Fri, 24 Nov 2017 08:24:31 +0100 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.5.0 MIME-Version: 1.0 In-Reply-To: <5A0DD27A.3010304@grosbein.net> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 24 Nov 2017 07:25:22 -0000 On 11/16/17 19:01, Eugene Grosbein wrote: > If you add an interface to a bridge, you should remove all IP addresses from it > and assign them to the bridge itself instead. And you will be fine. Thanks. In fact, assigning the base IP and all the jails to bridge0, instead of re0 solved. I still think bhyve assigns the VM's IP to tap0, but that doesn't seam to be a problem. bye av.