Hi there,
I discovered a strange behavior of the client network interface tap and an established bridge to the real networking device (em0). Each configuration (/etc/rc.conf...) is done as described in several howtos.
Client is a win 10 with Red Hat Virtio Eth Adapter, Driver 100.74.104.14100, date 19 jul 2017.
Older client-drivers are recommend (e.g. ...1.118), but has this has no effect.
Host:
Creating the bridge _after_ starting bhyve will succeed, otherwise it fails.
It fails:
1.) creating the bridge with
2.) starting bhyve ... -s 5,virtio-net,tap0...
3.) Result: guest can't access network (DHCP is active, IP is class-b! with 255.255.0.0 as netmask!
It works:
1.) starting bhyve ... -s 5,virtio-net,tap0...
2.) now creating the bridge with
3.) voilà, everything is fine.
Any hints?
Thank you!
I discovered a strange behavior of the client network interface tap and an established bridge to the real networking device (em0). Each configuration (/etc/rc.conf...) is done as described in several howtos.
Client is a win 10 with Red Hat Virtio Eth Adapter, Driver 100.74.104.14100, date 19 jul 2017.
Older client-drivers are recommend (e.g. ...1.118), but has this has no effect.
Host:
uname -a
Code:
FreeBSD 11.1-RELEASE FreeBSD 11.1-RELEASE #0 r321309: Fri Jul 21 02:08:28 UTC 2017 root@releng2.nyi.freebsd.org:/usr/obj/usr/src/sys/GENERIC amd64
Creating the bridge _after_ starting bhyve will succeed, otherwise it fails.
It fails:
1.) creating the bridge with
ifconfig bridge0 create
->bridge0 exists2.) starting bhyve ... -s 5,virtio-net,tap0...
3.) Result: guest can't access network (DHCP is active, IP is class-b! with 255.255.0.0 as netmask!
It works:
1.) starting bhyve ... -s 5,virtio-net,tap0...
2.) now creating the bridge with
ifconfig bridge0 create
-> bridge0 exists3.) voilà, everything is fine.
Any hints?
Thank you!