https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=287163
--- Comment #3 from Martin Birgmeier <d8zne...@aon.at> --- Regarding the doubts about using the native em0 instead of net/intel-em-kmod (issue 2. in this bug report): They are unfortunately justified. Because the bridge setup did not work, I reverted to em0 directly, but this time using the native driver. The result is quite disastrous, the Windows 10 VirtualBox client does not get connectivity at all using this setup. Reverting to if_em_updated (i.e., net/intel-em-kmod) and rebooting results in a fully behaving Windows 10 vbox client. This should actually go to bug 235031. -- Martin p.s. I just realize - even though the interface name is the same, might it be necessary to newly select this interface in the VirtualBox configuration? VirtualBox did not complain when starting the machine, so I assumed the setup was o.k. -- You are receiving this mail because: You are the assignee for the bug.
