Date: Thu, 20 Nov 2025 19:32:42 +0000 From: bugzilla-noreply@freebsd.org To: net@FreeBSD.org Subject: [Bug 291105] Intel i350 not receiving arp replies Message-ID: <bug-291105-7501-qeCajEYZ0C@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-291105-7501@https.bugs.freebsd.org/bugzilla/> References: <bug-291105-7501@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=291105 --- Comment #2 from Dave Hayes <dave@jetcafe.org> --- So yes ... I have already created a static ARP entry and this works. Sadly, this is actually my workaround to get machines talking to each other; the IP I referenced in my report is one of several that are not working. I will also point out that igb1 on the affected machine works like a charm. It is igb0 and igb2 that are not receiving arp requests. Each switch is a different make/model. I did try turning off all the TSO/VLAN stuff (as you can see in the previous message). This had no effect. As to 13.5 vs 14.3, I've no way to actually test that at the moment as I have no more 13.5 machines on my network. All my machines run the exact same version of STABLE: FreeBSD 14.3-STABLE stable/14-n272138-592f2e599f24 Now that I look, one of these machines has an I350 running the exact same OS version. For the 2nd machine, here's the pciconf information: igb0@pci0:133:0:0: class=0x020000 rev=0x01 hdr=0x00 vendor=0x8086 device=0x1521 subvendor=0x8086 subdevice=0x0001 vendor = 'Intel Corporation' device = 'I350 Gigabit Network Connection' class = network subclass = ethernet and the dmesg information: igb0: <Intel(R) I350 (Copper)> mem 0xf0300000-0xf03fffff,0xf040c000-0xf040ffff irq 58 at device 0.0 numa-domain 0 on pci8 igb0: EEPROM V1.63-0 eTrack 0x8000116b igb0: Using 1024 TX descriptors and 1024 RX descriptors igb0: Using 8 RX queues 8 TX queues igb0: Using MSI-X interrupts with 9 vectors igb0: Ethernet address: 50:7c:6f:55:f8:58 igb0: netmap queues/slots: TX 8/1024, RX 8/1024 The only differences appear to be - the "subdevice" - the EEPROM version - and of course the ethernet address, but that's probably pedantic Does this help at all? -- You are receiving this mail because: You are the assignee for the bug.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-291105-7501-qeCajEYZ0C>