[systemd-devel] bridge vlan-aware

[Salvatore Mazzarino]

Also to prove that it’s not a switch issue I have launched this configuration and everything works. VMs get IP in the VLAN 166.

However this configuration is not very dynamic because I cannot control Libvirt vnet names so I need to match all the vnet interfaces.

salmazz at nux-11-i7 /e/s/network> cat br0.netdev
[NetDev]
Name=br0
Kind=bridge

[Bridge]
VLANFiltering=yes
salmazz at nux-11-i7 /e/s/network> cat br0.network
[Match]
Name=br0

[Network]
DHCP=yes

salmazz at nux-11-i7 /e/s/network> cat enp89s0.network
# This file is managed by Salt via salt://systemd/networkd/templates/profile.jinja

[Match]
Name=enp89s0
[Network]
Bridge=br0
[BridgeVLAN]
VLAN=166
salmazz at nux-11-i7 /e/s/network> cat vnet.network
[Match]
Name=vnet*

[Network]
Bridge=br0

[BridgeVLAN]
VLAN=166
PVID=166
EgressUntagged=166
On 19. 11. 2022 10:26 +0100, Salvatore Mazzarino <apocalipse89 at gmail.com>, wrote:
> bridge vlan show
>
> port vlan-id
> enp89s0 1 PVID Egress Untagged
> br0     1 PVID Egress Untagged
> br166   1 PVID Egress Untagged
> eth.166 1 Egress Untagged
>         166 PVID Egress Untagged
> virbr0  1 PVID Egress Untagged
>
> Just to understand. I attach VMs to the br166. In this case also enp89s0 should allow VLAN 166?
> On 19. 11. 2022 10:17 +0100, Salvatore Mazzarino <apocalipse89 at gmail.com>, wrote:
> > I do not think it's a switch issue.  The systemd configuration is surely wrong but I'm not sure where.
> >
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/systemd-devel/attachments/20221119/4449b807/attachment.htm>