From owner-freebsd-net@freebsd.org  Thu Nov 16 17:51:54 2017
Return-Path: <owner-freebsd-net@freebsd.org>
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 DDDFBDE4457
 for <freebsd-net@mailman.ysv.freebsd.org>;
 Thu, 16 Nov 2017 17:51:54 +0000 (UTC) (envelope-from ml@netfence.it)
Received: from smtp207.alice.it (smtp207.alice.it [82.57.200.103])
 by mx1.freebsd.org (Postfix) with ESMTP id 748983EF3
 for <freebsd-net@freebsd.org>; Thu, 16 Nov 2017 17:51:53 +0000 (UTC)
 (envelope-from ml@netfence.it)
Received: from soth.ventu (79.40.26.62) by smtp207.alice.it (8.6.060.28)
 id 5A0BFD7B0037E9D2 for freebsd-net@freebsd.org;
 Thu, 16 Nov 2017 18:51:47 +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 vAGHpk0T021214
 for <freebsd-net@freebsd.org>; Thu, 16 Nov 2017 18:51:46 +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
From: Andrea Venturoli <ml@netfence.it>
Subject: bridge0 not working when cable disconnected
To: freebsd-net@freebsd.org
Message-ID: <59452bf1-25fb-970d-1d8d-5ca1463da4fd@netfence.it>
Date: Thu, 16 Nov 2017 18:51:38 +0100
User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101
 Thunderbird/52.4.0
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8; 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 <freebsd-net.freebsd.org>
List-Unsubscribe: <https://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: <https://lists.freebsd.org/mailman/listinfo/freebsd-net>,
 <mailto:freebsd-net-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 16 Nov 2017 17:51:55 -0000

Hello.

I've got the following setup:
re0:  192.168.x.1 (main IP)
       192.168.x.2 (jail)
       192.168.x.3 (jail)
       192.168.x.4 (jail)
tap0: VM-bhyve VM (using 192.168.x.9)
bridge0: connecting re0 and tap0.

The VM used to work properly.
Now, however, I've got the network cable temporarily disconnected from 
re0 and the VM seems to be isolated: it can't reach 192.168.x.1 or any 
jail or anything else (192.168.x.1 is its gateway).
tcpdump on tap0 or bridge0 show packets coming out of the VM, but no 
answer going in.



Pinging 192.168.x.9 from the host yields "no route to host".



Can the network cable disconnection be the reason?
I'm asking here since the box is physically in another place and I 
cannot try this now, but would like to do some work before I go there.





Any other hint, otherwise?

  bye & Thanks
	av.