FreeBSD on VMware
Monah Baki
monahbaki at gmail.com
Wed Jun 28 19:17:22 UTC 2017
Ok peeps, I solved the dilemma
First off, you need to bridge VMware Network Adapter VMnet8 (just this in
bridge mode)
Second on your FreeBSD your first network adapter set it to Bridge, then
create another adapter and set it to NAT
Bootup FreeBSD
em0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
options=9b<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM>
ether 00:0c:29:73:3b:d4
inet 192.168.1.16 netmask 0xffffff00 broadcast 192.168.1.255
nd6 options=29<PERFORMNUD,IFDISABLED,AUTO_LINKLOCAL>
media: Ethernet autoselect (1000baseT <full-duplex>)
status: active
em1: flags=8802<BROADCAST,SIMPLEX,MULTICAST> metric 0 mtu 1500
options=9b<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM>
ether 00:0c:29:73:3b:de
nd6 options=29<PERFORMNUD,IFDISABLED,AUTO_LINKLOCAL>
media: Ethernet autoselect (1000baseT <full-duplex>)
status: active
Hope this helps
Monah
On Tue, Jun 27, 2017 at 1:26 PM, Eric Melville <emelville at anomali.com>
wrote:
> > If I configure FreeBSD as Bridged: connected directly to the physical
> > network, which is what I want, no IP gets assigned to the interface.
> >
> >
> > Any idea why?
>
> Wireless is great for laptops but generally wired ethernet works much
> better with VM environments. There are various hacks in certain
> hypervisors, but promiscuous mode on the wire simply works and on top of
> that modern cards have enhancements to further support virtualization.
More information about the freebsd-questions
mailing list