Project

General

Profile

Actions
Copy link

Bug #14665

closed
JP KP

IGMP Proxy cannot start on VirtIO (``vtnet``) interfaces

Bug #14665: IGMP Proxy cannot start on VirtIO (``vtnet``) interfaces

Added by Jim Pingle about 3 years ago. Updated almost 3 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
Kristof Provost
Category:
IGMP Proxy
Target version:
2.7.1
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 1 (0 open — 1 closed)

Related to Bug #14301: Input validation error when saving IGMP Proxy settingsResolvedKristof Provost

Actions

JP Updated by Jim Pingle about 3 years ago Actions
Copy link
 #1

  • Related to Bug #14301: Input validation error when saving IGMP Proxy settings added

KP Updated by Kristof Provost about 3 years ago Actions
Copy link
 #2

  • 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.

JP Updated by Jim Pingle almost 3 years ago Actions
Copy link
 #3

  • Status changed from Feedback to Resolved
  • % Done changed from 0 to 100

Daemon appears to start OK on vtnet interfaces on dev snapshots.

JP Updated by Jim Pingle almost 3 years ago Actions
Copy link
 #4

  • Target version changed from 2.8.0 to 2.7.1
Actions
Copy link

Also available in: Atom