svn commit: r260224 - head/sys/netinet

[Bryan Venteicher]

On Mon, Jan 6, 2014 at 12:53 AM, Yonghyeon PYUN <pyunyh at gmail.com> wrote:

> On Fri, Jan 03, 2014 at 11:03:12AM +0000, Gleb Smirnoff wrote:
> > Author: glebius
> > Date: Fri Jan  3 11:03:12 2014
> > New Revision: 260224
> > URL: http://svnweb.freebsd.org/changeset/base/260224
> >
> > Log:
> >   Make failure of ifpromisc() a non-fatal error. This makes it possible
> to
> >   run carp(4) on vtnet(4).
> >
>
> vtnet(4) is the only device that doesn't correctly support
> promiscuous mode?  I don't know details of vtnet(4) but it seems
> it's not hard to mimic promiscuous mode.  I'm not sure why the
> driver returns ENOTSUP to user land given that vtnet(4) defaults
> to promiscuous mode for backwards compatibility.  It also does
> not handle multicast filter configuration when VTNET_FLAG_CTRL_RX
> flag is not set.  If vtnet(4) does not support multicast filter,
> it shouldn't announce IFF_MULTICAST. I wonder how vtnet(4) can work
> with carp(4) given that its multicast handling is ignored.
>

I've talked to Gleb off-list about this. I intent to remove the default to
promiscuous mode hack. Previous versions of the specification had a
footnote about this, but it has since been removed. Note that both promisc
and multicast likely require some host configuration on the
tap/bridge/physical interfaces as well.

I'll look at the multicast handling. If carp(4) already works with bhyve,
we might want to add a minimalist control virtqueue support to bhyve.