Hi! > Am 22.10.2020 um 04:47 schrieb D'Arcy Cain <da...@druid.net>: > public: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500 > ether 02:9d:b2:b8:78:00 > inet 98.158.139.65 netmask 0xffffffe0 broadcast 98.158.139.95 > id 00:00:00:00:00:00 priority 32768 hellotime 2 fwddelay 15 > maxage 20 holdcnt 6 proto rstp maxaddr 2000 timeout 1200 > root id 00:00:00:00:00:00 priority 32768 ifcost 0 port 0 > member: eth0 flags=143<LEARNING,DISCOVER,AUTOEDGE,AUTOPTP> > ifmaxaddr 0 port 1 priority 128 path cost 55 > groups: bridge > nd6 options=9<PERFORMNUD,IFDISABLED> > tap0: [...]
tap0 is not a member of your bridge. With the VM running you can try
ifconfig public addm tap0
and check if that changes things.
Then go back to the drawing board and probably let vm-bhyve manage
all that stuff. Just make sure to configure your physical interface with
the hardware acceleration features disabled.
You *can* put the IP address on the physical interface and have
vm-bhyve create the bridge. I honestly don't know why the documentation
explicitly states that you should not. FreeNAS has been running like this
for years and only supports the "correct" configuration since 11.3 or so.
On the other hand coming from Cisco and friends putting the address on
the topmost layer 3 interface does make perfect sense to me - so e.g.
on a Cisco switch you have physical ports that are members of a VLAN
and if you run anything layer 3 on that box, of course the address goes
on the VLAN, not the port ...
But give vm-bhyve a spin with the address on the physical. Or use two
different physical interfaces - one for the host, one for the "public" bridge.
HTH,
Patrick
--
punkt.de GmbH
Patrick M. Hausen
.infrastructure
Kaiserallee 13a
76133 Karlsruhe
Tel. +49 721 9109500
https://infrastructure.punkt.de
i...@punkt.de
AG Mannheim 108285
Geschäftsführer: Jürgen Egeling, Daniel Lienert, Fabian Stein
signature.asc
Description: Message signed with OpenPGP
