Re: Can't figure out getting network into bhyve instance.

From: Steven Friedrich <freebsdlouisville_at_gmail.com>
Date: Fri, 05 May 2023 17:53:06 UTC
I can get in with vm console nameofguest

root@freebsd:~ # ifconfig
vtnet0: flags=8863<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 
1500
        options=80028<VLAN_MTU,JUMBO_MTU,LINKSTATE>
        ether 58:9c:fc:02:aa:68
        inet 192.168.1.14 netmask 0xffffff00 broadcast 192.168.1.255
        media: Ethernet autoselect (10Gbase-T <full-duplex>)
        status: active
        nd6 options=29<PERFORMNUD,IFDISABLED,AUTO_LINKLOCAL>
lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> metric 0 mtu 16384
        options=680003<RXCSUM,TXCSUM,LINKSTATE,RXCSUM_IPV6,TXCSUM_IPV6>
        inet6 ::1 prefixlen 128
        inet6 fe80::1%lo0 prefixlen 64 scopeid 0x2
        inet 127.0.0.1 netmask 0xff000000
        groups: lo
        nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL>

vtnet0 has an IP address, I assume it got it from DHCP.

But ping to my router at 192.168.1.1 fails.  100% packet loss.

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