Date: Tue, 22 Aug 2017 15:55:46 +0700 From: Eugene Grosbein <eugen@grosbein.net> To: Boris <borisbsd@gmail.com> Cc: freebsd-net@freebsd.org Subject: Re: bridge interface IP connectivity issue when using oce interface Message-ID: <599BF192.1010802@grosbein.net> In-Reply-To: <CAJYdwgVH9knt4W88UoVYWWPOt%2BVBooh0L5sxtqWefM2-o678kQ@mail.gmail.com> References: <CAJYdwgUDWbp=2ONfSJdpNzNb8h7NomnJQecMqivg1j-tAjLhSg@mail.gmail.com> <599B8576.8030801@grosbein.net> <CAJYdwgU13rBf%2BZ_UdL%2BQaBpgNQrLH8fVM3dEJy7pBP9Uv5xSgQ@mail.gmail.com> <599BEEEF.7080807@grosbein.net> <CAJYdwgVH9knt4W88UoVYWWPOt%2BVBooh0L5sxtqWefM2-o678kQ@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?599BF192.1010802>