To add more info. Also br0 has to allow vlan 166 to pass through. This was my
mistake
I've fixed the systemd configuration and now everything works as expected. The
config was wrong. Thanks anyway to chime in
On 19.11.2022 12:26, Salvatore Mazzarino 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
On Fri, Nov 18, 2022 at 5:33 PM Barry wrote:
>
>
>
> > On 17 Nov 2022, at 20:03, Ted Toth wrote:
> >
> > The comment about inotify was just an example, I understand that there
> > is a 'notify' service type but I'm not using it because of its
> > documented shortcomings.
>
> I thought using
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@nux-11-i7 /e/s/network>
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
I do not think it's a switch issue. The systemd configuration is surely wrong
but I'm not sure where.
Please reply to list
On 19.11.2022 12:05, Salvatore Mazzarino wrote:
The vlan 166 has a dhcp server. The switch port is set to accept tagged and
untagged traffic.
I am not sure what "accept tagged and untagged" traffic does on your
switch. But so far it sounds more like switch
On 18.11.2022 03:46, Salvatore Mazzarino wrote:
Posted a wrong config for br0.netdev. the correct one is the following
br0.netdev
[NetDev]
Name=br0
Kind=bridge
[Bridge]
DefaultPVID=1
VLANFiltering=yes
On Fri, Nov 18, 2022 at 1:43 AM Salvatore Mazzarino
wrote:
I have a physical interface
