You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Virtualization and containerization platforms, such as Docker or Proxmox VE, often create network bridges dynamically. These bridges usually share common prefixes.
For example, Docker creates networks with the br-* prefix.
Potential Benefits
Manually adding network interfaces created programmatically is inconvenient, especially when they can be created or removed at any time.
This functionality would provide seamless support for Docker Compose without the need to manually add network bridge interface.
The text was updated successfully, but these errors were encountered:
Greetings
No response
Feature Request
It would be nice to add support for wildcard interface names for LAN networks.
For instance, using
br-*
should match all local network interfaces that start withbr-
.This feature could potentially be implemented by modifying the following code:
dae/control/control_plane_core.go
Lines 214 to 222 in 046dab6
Use Cases
Virtualization and containerization platforms, such as Docker or Proxmox VE, often create network bridges dynamically. These bridges usually share common prefixes.
For example, Docker creates networks with the
br-*
prefix.Potential Benefits
Manually adding network interfaces created programmatically is inconvenient, especially when they can be created or removed at any time.
This functionality would provide seamless support for Docker Compose without the need to manually add network bridge interface.
The text was updated successfully, but these errors were encountered: