Date: Thu, 22 Oct 2020 09:56:39 +0200 From: "Patrick M. Hausen" <hausen@punkt.de> To: D'Arcy Cain <darcy@druid.net> Cc: freebsd-virtualization@freebsd.org Subject: Re: When is a switch not a switch? Message-ID: <FEAD843A-6E76-4299-A94F-7D4ECEB098FD@punkt.de> In-Reply-To: <6267599d-bc0c-6d63-bb19-1fc695e53997@druid.net> References: <57c32e6d-5572-3d3b-1a57-f3064bee7dc2@druid.net> <20201020065630.GE8272@funkthat.com> <CF189122-7D85-4BF1-9172-75D3EE0E77FB@punkt.de> <3ed627e2-d99a-107e-4135-8aef1ad4ec71@druid.net> <30A67F82-312E-4651-A5E7-2E2AD926FF24@punkt.de> <973b1b56-817f-6976-e5d3-34cfbc373b13@druid.net> <A075C069-1F89-428C-BDB7-7A9F44A4E283@punkt.de> <723CA318-80E9-4A6B-91ED-E791A40CC2C0@punkt.de> <6267599d-bc0c-6d63-bb19-1fc695e53997@druid.net>
next in thread | previous in thread | raw e-mail | index | archive | help
--Apple-Mail=_A83E54F4-A6CC-4CAB-ADD4-1DE2A8FE37F2 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=utf-8 Hi! > Am 22.10.2020 um 04:47 schrieb D'Arcy Cain <darcy@druid.net>: > public: flags=3D8843<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=3D143<LEARNING,DISCOVER,AUTOEDGE,AUTOPTP> > ifmaxaddr 0 port 1 priority 128 path cost 55 > groups: bridge > nd6 options=3D9<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 info@punkt.de AG Mannheim 108285 Gesch=C3=A4ftsf=C3=BChrer: J=C3=BCrgen Egeling, Daniel Lienert, Fabian = Stein --Apple-Mail=_A83E54F4-A6CC-4CAB-ADD4-1DE2A8FE37F2 Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename=signature.asc Content-Type: application/pgp-signature; name=signature.asc Content-Description: Message signed with OpenPGP -----BEGIN PGP SIGNATURE----- iQEzBAEBCAAdFiEEgzqrjO/mj9CSsTg2kG8u4u3aiVwFAl+ROzcACgkQkG8u4u3a iVygIAgAsfdcJLK9HQXeSTjdcckL50UsVuMWXIPat029dNlfm8GUyPlDoU3/axfg m6xsDj0cy4UGW20ZHjl+7vsF5UvgjSU7CNg1iF08Z8X4PscIiUj7oX6b034HG52U 6NQ/H9ma22pum+ae6/73hU9+sgftHqXuMo4Akbis4qRTsMtviBaaW++B/pVt40nS 6aAKN/75srHfcL7lE9rkAk3fku+wGwje3X7s6ZYuSRZcXotuvwrMOEyIcaUlSONF a1UfL4vWsBWddFt4qx7gO40C6nDIxK31qaQQEReY9Pgbd+7Ds/04mKTigt+lU+oZ Qti3b41klkPvrf6p99IiX1nG4tGT2g== =JDnA -----END PGP SIGNATURE----- --Apple-Mail=_A83E54F4-A6CC-4CAB-ADD4-1DE2A8FE37F2--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?FEAD843A-6E76-4299-A94F-7D4ECEB098FD>