Date: Tue, 16 Oct 2018 00:10:50 +0800 From: Marcelo Araujo <araujobsdport@gmail.com> To: bzeeb-lists@lists.zabbadoz.net Cc: freebsd-virtualization@freebsd.org Subject: Re: bhyve on reboot loses tap(4) configuration Message-ID: <CAOfEmZguTq7iL=X38oQNYpVt84EQrsNViMJ1fX-LmxCSLdpMPg@mail.gmail.com> In-Reply-To: <02210D52-A45B-4E54-BCEE-EC61026B70C0@lists.zabbadoz.net> References: <02210D52-A45B-4E54-BCEE-EC61026B70C0@lists.zabbadoz.net>
next in thread | previous in thread | raw e-mail | index | archive | help
Em ter, 16 de out de 2018 =C3=A0s 00:06, Bjoern A. Zeeb < bzeeb-lists@lists.zabbadoz.net> escreveu: > Hi, > > I tried to use bhyve with the tap(4)/vtnet(4) solution as documented in > the handbook (tap needs autoopen). > However, I am using no bridge(4) interface but a =E2=80=9Cpoint-to-point= =E2=80=9D > configuration. > > Example: > guest configures vtnet0 to 192.0.2.2/24 > host configures tap0 to 192.0.2.1/24 > > When rebooting the guest inside the bhyve, it seems bhyve loses the > outside tap0 configuration. I assume that is because the tap0 interface > is closed and re-opened on the =E2=80=9Cwarm restart=E2=80=9D. > > Apart from using devd and possibly tracking tap interfaces to come up > and track things there, is there are better solution for not having to > reconfigure the host interface on every guest reboot? > Not sure if I understood well your case, but have you tried to set this sysctl: net.link.tap.up_on_open? Best, --=20 --=20 Marcelo Araujo (__)araujo@FreeBSD.org \\\'',)http://www.FreeBSD.org <http://www.freebsd.org/>; \/ \ ^ Power To Server. .\. /_)
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAOfEmZguTq7iL=X38oQNYpVt84EQrsNViMJ1fX-LmxCSLdpMPg>