net/igmp-proxy: expose per-interface multicast whitelist in the GUI

Abierto
  • ¿Algo no está bien?
#5,755 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 2 días

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
3/5
Tiempo estimado
1-2 días
Aptitud para principiantes
76/100
Tipo de issue
Nueva funcionalidad
Claridad
Bien especificado
Estado de actividad
Activo
Stack tecnológico
php
Área
frontend, networking

Línea de trabajo

Start at /services_igmpproxy_edit.php and compare the requested Whitelist rows with the existing Network(s) layout. Review the attached patch and trace the plugin's persistent storage and configuration generation paths. Done means upstream and downstream interfaces accept validated multicast whitelist entries, preserve empty-field behavior, and regenerate the expected configuration.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

Important notices

Before you add a new report, we ask you kindly to acknowledge the following:

Is your feature request related to a problem? Please describe.

The IGMP Proxy GUI does not expose igmpproxy's whitelist option. I need to restrict the multicast groups allowed on individual interfaces without manually editing the generated configuration.

This is useful in networks where multicast serves several purposes, such as IPTV and local services. An upstream whitelist limits the multicast groups requested on the ISP’s IPTV VLAN, preventing requests for unrelated local groups from being forwarded to the ISP.

The existing Network(s) field configures altnet, which controls source networks rather than multicast group whitelisting.

Describe the solution you'd like

Add a Whitelist section below Network(s) in the interface editor at /services_igmpproxy_edit.php, available for both upstream and downstream interfaces.

It should follow the existing Network(s) layout: a Network input, a CIDR dropdown, and add/remove buttons for each row.

Leaving the field empty should preserve the existing behavior of allowing all multicast groups.

Describe alternatives you've considered

Manually editing /usr/local/etc/igmpproxy.conf, but those changes are overwritten when OPNsense regenerates the configuration. A GUI setting would make the whitelist persistent and easier to maintain.

Additional context

A patch is available that adds GUI input, validation, persistent storage, and configuration generation. It rejects invalid or non-multicast ranges and removes duplicate entries.

I also successfully applied and tested the patch on my live OPNsense system.

Image
Lenguaje dominante
PHP
Estrellas
1.2k
Forks
909
Merge medio
4 d 19 h
PR fusionados (30 d)
21

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de opnsense/plugins

Todos los issues de opnsense/plugins

Issues similares

Más issues de PHP

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.