[SOLVED] Intel I226-v doesn't tag vlan correctly, onyl untagged trafic will pass to physical switch

[aow770]

Hi folks,

iam new here and Iam a linux mid-range admin (but not expert level). I switch from esxi-free to proxmox and have an appliance with 4 2.5GBit intel i226-v nics. My final goal is make a bond to my ubi-Pro-switch and tag all traffic to vm and lxc.

For better understanding of my problem, I has remove my bond and use only one nic with following switch setting - untagged trafic to vlan 1 and other allow all vlans.
I have create two Linux bridges vmbr100 and vmbr200 with parent-interfaces "enp3s0.100" and "enp3s0.200" and use "vlan aware=off" on both. Then I have a lxc and give network to vmbr100 and field vlan-tag empty. (In case of VM, I use same setting).

The guest don't get dhcp-adress from dhcp-server. Other devices they connected by wire to same vlan works fine.

I think it is a problem with Intel i226-v driver and the functionality to tag traffic.


root@pve:~# modinfo igb | grep version
srcversion: A155E7614ABF2D3E40E0F20
vermagic: 6.5.13-3-pve SMP preempt mod_unload modversions

Is that an know issue?
Has anyone some idea's? On esxi, all working fine without any actions before.

ByeBye
aow

 

[Alwin Antreich]

I have create two Linux bridges vmbr100 and vmbr200 with parent-interfaces "enp3s0.100" and "enp3s0.200" and use "vlan aware=off" on both. Then I have a lxc and give network to vmbr100 and field vlan-tag empty. (In case of VM, I use same setting).

The notation interfaceXY.vlan will tell the kernel to handle the VLAN. It means also that these interfaces are filtering to the VLAN tag, which means you will need to set the VLAN on the switch as well.

The guest don't get dhcp-adress from dhcp-server. Other devices they connected by wire to same vlan works fine.

Where does your DHCP server sit (which vlan)? As you might know already, DHCP doesn't travel across broadcast boundaries (vlan).

 

[aow770]

I have solved myself. The DHCP-Server is an VM under Proxmox and the switch has an good hidden function to prevent Rough DHCP-Servers named DHCP-Guard. After I configure the Switch on whitelisted DHCP-Server IP address the cable and wireless connected clients on physical switch get an correct DHCP-Offer and IP address.