Date: Tue, 22 Aug 2017 15:44:31 +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: <599BEEEF.7080807@grosbein.net> In-Reply-To: <CAJYdwgU13rBf%2BZ_UdL%2BQaBpgNQrLH8fVM3dEJy7pBP9Uv5xSgQ@mail.gmail.com> References: <CAJYdwgUDWbp=2ONfSJdpNzNb8h7NomnJQecMqivg1j-tAjLhSg@mail.gmail.com> <599B8576.8030801@grosbein.net> <CAJYdwgU13rBf%2BZ_UdL%2BQaBpgNQrLH8fVM3dEJy7pBP9Uv5xSgQ@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 22.08.2017 15:39, Boris wrote: > Ok thanks Eugene. > net.link.bridge.inherit_mac=1 helped get the connectivity from the bridge however, when I start a FreeBSD bhyve VM and attached that to a tap interface in the bridge, I don't get connectivity from the VM. > > SETUP: > Gateway - 192.168.0.222/29 <http://192.168.0.222/29>; > Server - 192.168.0.218/29 <http://192.168.0.218/29>; > VM - 192.168.0.219/29 <http://192.168.0.219/29>; > > On the VM, I see the ARP entries for the GW and the VM itself but cannot ping the gateway nor the host. This means your uplink filters traffic of your VM due to its fabricated MAC address. You should ask administrator of switching network you are connected to for assistance or hide your VM behind NAT using bridging VM traffic with tap(4) interface instead of real one or bridge and do routing/NAT for VM.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?599BEEEF.7080807>