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
We use the linux bridge in VLAN-aware mode to interconnect different container/VMs (podman, libvirt, lxc, systemd-nspawn). To connect podman containers to a specific VLAN I use the CNI bridge plugin in L2-only vlan configuration.
We try to do the same w/o CNI. There are two things missing currently:
Support multiple networks with the same network_interface but different vlan setting
Set the vlan on the veth link like: sudo bridge vlan add vid 20 pvid untagged dev ...
I opened an issue for netavark but first part belongs to common/libnetwork:
1. podman create network
Currently, the podman network create already allows to set a vlan option:
I have the same problem and for me this looks like a new network driver - sth like "brat" as in bridge attach
Background: I have a (and only one) bridge interface on my system with multiple VLANs. For me it would be perfect to have a podman network that just adds the vnet interface to my existing bridge and configures the VLANs.
There are multiple solutions to this problem - any hint on how this should be solved?
Before I start a PR in the complete wrong direction.
When a vlan is used there should be no bridge name conflict check. It is
totally valid to have the same bridge with different vlans in two
configs and that is the intended use case.
Fixescontainers#2095
Signed-off-by: Paul Holzinger <[email protected]>
Luap99
added a commit
to Luap99/common
that referenced
this issue
Jan 30, 2025
When a vlan is used there should be no bridge name conflict check. It is
totally valid to have the same bridge with different vlans in two
configs and that is the intended use case.
Fixescontainers#2095
Signed-off-by: Paul Holzinger <[email protected]>
Thank you, I'm looking forward using it. With the upcoming release of podman/netavark I can retire all my custom bash cni plugins (except the nft one) . Great work!
We use the linux bridge in VLAN-aware mode to interconnect different container/VMs (podman, libvirt, lxc, systemd-nspawn). To connect podman containers to a specific VLAN I use the CNI bridge plugin in L2-only vlan configuration.
We try to do the same w/o CNI. There are two things missing currently:
network_interface
but differentvlan
settingsudo bridge vlan add vid 20 pvid untagged dev ...
I opened an issue for netavark but first part belongs to
common/libnetwork
:1. podman create network
Currently, the
podman network create
already allows to set a vlan option:results in
/etc/containers/networks/vlan20.json
But it fails to create another network on the same bridge with different vlan tag:
Relevant code is in
libnetwork/internal/util/bridge.go#L16
The text was updated successfully, but these errors were encountered: