On 06.11.2015 07:59, Craig Rodrigues wrote:
> On Thu, Nov 5, 2015 at 4:36 PM, Miroslav Lachman <000.f...@quip.cz> wrote:
>
>> Eugene Grosbein wrote on 11/05/2015 18:06:
>>
>>> Yes, it is. And there is a solution:
>>> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=165174
>>>
>>
>> I don't
On 6-11-2015 09:09, Eugene Grosbein wrote:
> On 06.11.2015 07:59, Craig Rodrigues wrote:
>> On Thu, Nov 5, 2015 at 4:36 PM, Miroslav Lachman <000.f...@quip.cz> wrote:
>>
>>> Eugene Grosbein wrote on 11/05/2015 18:06:
>>>
Yes, it is. And there is a solution:
On 04.11.2015 22:34, Victor Sudakov wrote:
> tap(4) says that tapN is an exclusive-open device. And when I tried it
> out, the second bhyve instances said "open of tap device /dev/tap0 failed",
> which was kind of expected.
Hmm, false memory... I have missed "exclusive" part.
On 11/5/15 10:31 AM, Victor Sudakov wrote:
Neel Natu wrote:
Julian Elischer wrote:
I am experimenting with bhyve which uses tap(4) for network access.
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
Julian Elischer wrote:
[dd]
> >>> For some reason, after a guest is shutdown or rebooted, the IP address
> >>> on the host's tap0 interface is deleted.
> >>>
> >> Try using 'vmnet0' instead of 'tap0'. It will retain the IP address
> >> even after a guest reboot/shutdown.
> > Thanks, I see now
On 05.11.2015 01:45, Victor Sudakov wrote:
> For some reason, after a guest is shutdown or rebooted, the IP address
> on the host's tap0 interface is deleted.
>
> It's kind of inconvenient.
Yes, it is. And there is a solution:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=165174
Eugene Grosbein wrote on 11/05/2015 18:06:
On 05.11.2015 01:45, Victor Sudakov wrote:
For some reason, after a guest is shutdown or rebooted, the IP address
on the host's tap0 interface is deleted.
It's kind of inconvenient.
Yes, it is. And there is a solution:
On Thu, Nov 5, 2015 at 4:36 PM, Miroslav Lachman <000.f...@quip.cz> wrote:
> Eugene Grosbein wrote on 11/05/2015 18:06:
>
>> Yes, it is. And there is a solution:
>> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=165174
>>
>
> I don't understand why such useful patches are left uncommited and
Hi Victor,
On Wed, Nov 4, 2015 at 10:45 AM, Victor Sudakov wrote:
> Victor Sudakov wrote:
>> Julian Elischer wrote:
>> > >
>> > > I am experimenting with bhyve which uses tap(4) for network access.
>> > >
>> > > I don't want to bridge tap0 with any of the hosts's real NICs.
Neel Natu wrote:
> >> Julian Elischer wrote:
> >> > >
> >> > > I am experimenting with bhyve which uses tap(4) for network access.
> >> > >
> >> > > 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?
> >>
John Nielsen wrote:
>
> I am experimenting with bhyve which uses tap(4) for network access.
>
> 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!
> >>>
On Nov 4, 2015, at 11:45 AM, Victor Sudakov wrote:
> Victor Sudakov wrote:
>> Julian Elischer wrote:
I am experimenting with bhyve which uses tap(4) for network access.
I don't want to bridge tap0 with any of the hosts's real NICs. How can
I create
04.11.2015 20:12, Victor Sudakov пишет:
And if I need the VMs to talk to one another, I think I can bridge
several tapN devices on the host.
You could also just use broader IP network and single tap interface
for several VMs.
___
On 11/4/15 3:54 PM, Victor Sudakov wrote:
Colleagues,
I am experimenting with bhyve which uses tap(4) for network access.
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!
tap IS
Julian Elischer wrote:
> >
> > I am experimenting with bhyve which uses tap(4) for network access.
> >
> > 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!
>
> tap IS the
Eugene Grosbein wrote:
>
> > And if I need the VMs to talk to one another, I think I can bridge
> > several tapN devices on the host.
>
> You could also just use broader IP network and single tap interface
> for several VMs.
Do you mean to say I can run several bhyve instances on the same
tap0
Victor Sudakov wrote:
> Julian Elischer wrote:
> > >
> > > I am experimenting with bhyve which uses tap(4) for network access.
> > >
> > > 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
Colleagues,
I am experimenting with bhyve which uses tap(4) for network access.
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?
I even tried to create a lo1 interface on the host and bridge it with
tap0 but
18 matches
Mail list logo