Date: Wed, 4 Nov 2015 12:07:55 -0700 From: John Nielsen <lists@jnielsen.net> To: Victor Sudakov <vas@mpeks.tomsk.su> Cc: freebsd-net@freebsd.org Subject: Re: tap(4) and host-only networking between host and guest Message-ID: <C3B51AB9-3964-49D9-90F6-E56AF2FF57B2@jnielsen.net> In-Reply-To: <20151104184503.GC1117@admin.sibptus.tomsk.ru> References: <20151104075454.GA99850@admin.sibptus.tomsk.ru> <5639FF12.1020109@freebsd.org> <20151104131230.GA1117@admin.sibptus.tomsk.ru> <20151104184503.GC1117@admin.sibptus.tomsk.ru>
next in thread | previous in thread | raw e-mail | index | archive | help
On Nov 4, 2015, at 11:45 AM, Victor Sudakov <vas@mpeks.tomsk.su> wrote:
> Victor Sudakov wrote:
>> Julian Elischer wrote:
>>>>=20
>>>> I am experimenting with bhyve which uses tap(4) for network access.
>>>>=20
>>>> I don't want to bridge tap0 with any of the hosts's real NICs. How =
can
>>>> I create a private network just between the host and the guest?
>>> you are thinking too hard!
>>>=20
>>> tap IS the interface..
>>>=20
>>> ifconfig tap0 $address...
>>> and in the VM, ifconfig vtnet0 ${some_other_address}
>>=20
>> Thank you, Julian! It works. I felt I was missing something obvious.=20=
>=20
> For some reason, after a guest is shutdown or rebooted, the IP address
> on the host's tap0 interface is deleted.
>=20
> It's kind of inconvenient.=20
What I have done in this scenario is create a bridge interface, assign =
the host=E2=80=99s IP to the bridge, and add the tap as a member to the =
bridge.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?C3B51AB9-3964-49D9-90F6-E56AF2FF57B2>