[SOLVED] Re: bridge0 not working when cable disconnected

[Vincenzo Maffione]

Hi,
  The VM IP is assigned to the emulated interface inside the guest OS (e.g.
vtnet0).
It would not make sense to assign an IP to tap0, and I'm quite sure bhyve
doesn't do that.
If tap0 is attached to bridge0 (which is normally the case, and I guess
it's your case), there is no reason for tap0 to have an IP (because it's a
data port of an L2 switch).

If you give an IP to tap0 it's not dangerous, but there is no need to do
that. (The only use-case for giving an IP to tap0 I can think of is when
you don't attach tap0 do any bridge, and you use tap0 as a peer-to-peer
link for applications on your host to communicate with applications in the
VM. But nobody does that since you can do the same with the bridge0
interface, which can be used to talk to multiple VMs, not just one).

Cheers,
  Vincenzo

2017-11-24 8:24 GMT+01:00 Andrea Venturoli <ml at netfence.it>:

> On 11/16/17 19:01, Eugene Grosbein wrote:
>
> If you add an interface to a bridge, you should remove all IP addresses
>> from it
>> and assign them to the bridge itself instead. And you will be fine.
>>
>
> Thanks.
>
> In fact, assigning the base IP and all the jails to bridge0, instead of
> re0 solved.
> I still think bhyve assigns the VM's IP to tap0, but that doesn't seam to
> be a problem.
>
>  bye
>         av.
> _______________________________________________
> freebsd-net at freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-net
> To unsubscribe, send any mail to "freebsd-net-unsubscribe at freebsd.org"
>



-- 
Vincenzo Maffione