Actions
Bug #14665
closed
IGMP Proxy cannot start on VirtIO (``vtnet``) interfaces
Start date:
Due date:
% Done:
100%
Estimated time:
Plus Target Version:
23.09
Release Notes:
Default
Affected Version:
Affected Architecture:
Description
Moved this over from #14301
From Kristof:
I'm investigating another issue, which I suspect to be limited to virtio interfaces, and possibly only those on bhyve, but as I said: I'm still investigating.
The virtio issue did turn out to be a virtio problem. It doesn't allow IFF_ALLMULTI to be set (on systems where the host doesn't announce VIRTIO_NET_F_CTRL_RX support), so igmpproxy couldn't start.
https://reviews.freebsd.org/D41356 will fix that.
Related issues
Updated by Jim Pingle 9 months ago
- Related to Bug #14301: Input validation error when saving IGMP Proxy settings added
Updated by Kristof Provost 9 months ago
- Status changed from Waiting on Merge to Feedback
I've committed the relevant fix upstream and merged that into our trees. igmpproxy is expected to work in the next snapshots.
Updated by Jim Pingle 8 months ago
- Status changed from Feedback to Resolved
- % Done changed from 0 to 100
Daemon appears to start OK on vtnet interfaces on dev snapshots.
Actions