From owner-freebsd-net@freebsd.org Tue Aug 22 08:55:55 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 69307DD9F19 for ; Tue, 22 Aug 2017 08:55:55 +0000 (UTC) (envelope-from eugen@grosbein.net) Received: from hz.grosbein.net (hz.grosbein.net [78.47.246.247]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "hz.grosbein.net", Issuer "hz.grosbein.net" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id F30B07CD4C for ; Tue, 22 Aug 2017 08:55:54 +0000 (UTC) (envelope-from eugen@grosbein.net) Received: from eg.sd.rdtc.ru (root@eg.sd.rdtc.ru [62.231.161.221] (may be forged)) by hz.grosbein.net (8.15.2/8.15.2) with ESMTPS id v7M8toDn041341 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Tue, 22 Aug 2017 10:55:50 +0200 (CEST) (envelope-from eugen@grosbein.net) X-Envelope-From: eugen@grosbein.net X-Envelope-To: borisbsd@gmail.com Received: from eg.sd.rdtc.ru (eugen@localhost [127.0.0.1]) by eg.sd.rdtc.ru (8.15.2/8.15.2) with ESMTP id v7M8tkdO024927; Tue, 22 Aug 2017 15:55:46 +0700 (+07) (envelope-from eugen@grosbein.net) Subject: Re: bridge interface IP connectivity issue when using oce interface To: Boris References: <599B8576.8030801@grosbein.net> <599BEEEF.7080807@grosbein.net> Cc: freebsd-net@freebsd.org From: Eugene Grosbein X-Enigmail-Draft-Status: N1110 Message-ID: <599BF192.1010802@grosbein.net> Date: Tue, 22 Aug 2017 15:55:46 +0700 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:38.0) Gecko/20100101 Thunderbird/38.4.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Spam-Status: Yes, score=5.5 required=5.0 tests=BAYES_00, DATE_IN_FUTURE_96_Q, LOCAL_FROM,RDNS_NONE autolearn=no autolearn_force=no version=3.4.1 X-Spam-Report: * 3.3 DATE_IN_FUTURE_96_Q Date: is 4 days to 4 months after Received: date * -2.3 BAYES_00 BODY: Bayes spam probability is 0 to 1% * [score: 0.0000] * 1.9 RDNS_NONE Delivered to internal network by a host with no rDNS * 2.6 LOCAL_FROM From my domains X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on hz.grosbein.net X-Spam-Flag: YES X-Spam-Level: ***** X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 22 Aug 2017 08:55:55 -0000 On 22.08.2017 15:48, Boris wrote: > I own the upstream network and have full access to it. > It is configured as a simple router interface (Cisco device). > Before looking at that element (which I am not minimizing in the overall issue), shouldn't the VM be able to reach the IP setup on the bridge? At the moment, that does not work and it is very much local to the host. > Any thoughts? I've no experience with bhyve and its networking. And yes, you should be able to run ping between VM and host without problems. You should make sure tcpdump shows you ARP traffic on BOTH sides of the interface between host and VM. If not, you should first disconnect it from the bridge and repeat the test. If that does not help, stay away from bridge(4) for a while until you fix that. You may need to contact bhyve developers in that case.