Date: Fri, 5 May 2023 13:54:27 -0400 From: Steven Friedrich <freebsdlouisville@gmail.com> To: Tomek CEDRO <tomek@cedro.info> Cc: freebsd-questions@freebsd.org Subject: Re: Can't figure out getting network into bhyve instance. Message-ID: <ce28d6fb-b882-a869-a411-5e60365a3473@gmail.com> In-Reply-To: <CAFYkXjna8ytEfdqx-GAc6qThar04JC%2BYCMNGZMnK=Y0GSbQrrg@mail.gmail.com> References: <8d3a09fe-e69f-2c0e-8cc8-ca87ccfcfa42@gmail.com> <CAFYkXjna8ytEfdqx-GAc6qThar04JC%2BYCMNGZMnK=Y0GSbQrrg@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
BTW, I invoked the sysctls. Wait, were those on the host on in the vm? On 5/5/23 13:22, Tomek CEDRO wrote: > On Fri, May 5, 2023 at 5:55 PM Steven Friedrich wrote: >> I had found a bhyve tutorial on the Internet: https://klarasystems.com/articles/from-0-to-bhyve-on-freebsd-13-1/ >> (..) > In a simple scenario read `man vm` :-) > > Just add public switch with selected physical port / interface. > Machines will use that for networking by default. > > I had the same problem(?). Packets were not going out of the guest vm. > There are some sysctls to do in order to pass the bridged traffic. > > sysctl net.link.bridge.ipfw=0 > sysctl net.link.bridge.pfil_bridge=0 > sysctl net.link.bridge.pfil_member=0 > > I have provided a man page update on that, any comments welcome :-) > > https://github.com/churchers/vm-bhyve/pull/510 > > Hope that helps :-) > -- uname -a FreeBSD freebsd.friedrich.org 13.2-RELEASE FreeBSD 13.2-RELEASE FREEBSD amd64
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?ce28d6fb-b882-a869-a411-5e60365a3473>