-
Notifications
You must be signed in to change notification settings - Fork 262
Description
Currently, FOG requires specifying a single network interface for multicast operations. This works fine in a flat network, but in environments with multiple subnets or VLANs (e.g., VLANs 10, 40, and 80), this becomes a limitation. For example, if I want to perform a multicast deployment only on computers in VLAN 80, I need to manually adjust the FOG settings to use the correct interface before starting the multicast.
Proposed Idea: Introduce the ability to register subnets within FOG and associate them with specific network interfaces. This way:
- Groups of hosts could be linked to a subnet (e.g., Group X belongs to VLAN 80).
- When initiating a multicast task for that group, FOG would automatically select the appropriate network interface based on the subnet configuration.
- If no specific interface is configured for that subnet/group, FOG would fall back to the global multicast interface setting.
This approach would eliminate the need for manual configuration changes before each multicast operation and make deployments across segmented networks much more efficient.
I know there is a Subnet plugin, but it doesn’t seem to address multicast behavior (I apologize if it has and I didn't saw that option on it!). Extending this concept to include multicast interface mapping would be a great improvement for environments with multiple VLANs.