I run into this problem too, and in my case my laptop (where I'm testing
bhyve) only has one NIC and its wireless!
I have an ath card "MAC spoofinc" is not availeble, so for now I opted
for nating with PF and I assign manual IP's to the host tap0 and the
guest's vtnet0.
However it would be nice t
Hi Craig,
In this case, I am not connected to the lan nic. From you look
at the ifconfig output from my previous posting,
you will see that my bridge0 interface only has two members:
tap0
wlan0
APs generally only allow a single MAC per client, so any packets with
a source address other tha
I was refering to how it behavs in general and was using LAN NIC as an
example of a non-virtual NIC
On Wed, Oct 9, 2013 at 8:27 PM, Craig Rodrigues wrote:
> Aryeh,
>
> In this case, I am not connected to the lan nic. From you look
> at the ifconfig output from my previous posting,
> you will s
Aryeh,
In this case, I am not connected to the lan nic. From you look
at the ifconfig output from my previous posting,
you will see that my bridge0 interface only has two members:
tap0
wlan0
--
Craig
On Wed, Oct 9, 2013 at 4:36 PM, Aryeh Friedman wrote:
> It sometimes doesn't like adding both
It sometimes doesn't like adding both the lan nic and tap to the bridge at
the same time
On Wed, Oct 9, 2013 at 7:30 PM, Craig Rodrigues wrote:
> Hi,
>
> I am using this script to set up my tap device before
> running BHyve:
>
> =
Hi,
I am using this script to set up my tap device before
running BHyve:
=
#!/bin/sh
#iface=em0
iface=wlan0
ifconfig bridge0 create
ifconfig tap0 create
ifconfig bridge0 addm $iface addm tap0 up
sysctl net.link.tap.user_open=1
sy
