On 12/30/2022 11:15 AM, Andrey Kulikov wrote:
Hello,
I've got an Intel Fortville XL710-based Ethernet controller with 4 x 10GbE
SFP+ ports.
Platform is based on Intel Xeon CPU E5-2697 v4
Platform running Debian 11.6, kernel 5.10.0
# uname -a
Linux 5.10.0-20-amd64 #1 SMP Debian 5.10.158-2 (2022-12-13) x86_64 GNU/Linux
Current i40e driver: 2.22.8 (out-of tree, self-built from sources).
Are you loading the 8021q.ko module?
Setup: Two identical platforms, with absolutely identical hardware and
software. Connected directly with LC-LC SR patchcord using Intel 10G SFP+
transceivers (FTLX8571D3BCV-IT it makes any difference).
Issue: When I configure VLAN on HW interface - it doesn't work. When
pinging via VLAN the other side is just do not see anything (tcpdump shows
nothing).
At the same time, if I ping on HW interfaces directly - it does work
perfectly well.
But it was working with i40e driver 2.18.9 half of a year ago, with Debian
11.4(? here I could be wrong) kernel.
Relevant fragment from my /etc/network/interfaces on one side:
auto enp132s0f0
iface enp132s0f0 inet static
address 192.168.33.2
netmask 255.255.255.0
mtu 1500
auto enp132s0f0.545
iface enp132s0f0.545 inet static
address 192.168.44.2
netmask 255.255.255.0
mtu 1500
Once the network setup is done, what does 'ip link' show?
The other side looks identical except IP-addresses (they both end with '1').
Workaround: disable tx-vlan-offload and and rx-vlan-offload:
ethtool -K enp132s0f0 tx-vlan-offload off rx-vlan-offload off
Checked with CISCO NEXUS 7000 and NEXUS 9000 as remote counterparts - they
behave identically to described above.
Based on what you said I doubt it's switches or cables, but someting is
up with your config.
Current XL710 firmware is 8.15. But I've got adapters with firmware
7.something - there is no difference in behavior.
Does it ring a bell?
I don't recall hearing reports of other issues.
Does it have something to do with the i40e driver?
Is any further information required?
When pinging, it would be useful to see what ethtool -S shows as
changing, like
ethtool -S enp132s0f0
ping -c2 192.168.33.1
<fail>
ethtool -S enp132s0f0
arp -an
output would be useful as well.
_______________________________________________
E1000-devel mailing list
E1000-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/e1000-devel
To learn more about Intel Ethernet, visit
https://forums.intel.com/s/topic/0TO0P00000018NbWAI/intel-ethernet
