10Gtek Mini PCIe 1G Ethernet Network Card (Intel I210AT), 30-cm Cable Length, Single Port RJ45, Mini Pice Interface, not for M.2

When building a Linux system the last thing you want to deal with is weird drivers. So I always look for Intel or Broadcom chipsets in ethernet cards. Intel chipsets in particular are pretty much guaranteed to work. Most of the servers I build have Intel I350 ethernet cards for a reason. They're fast, reliable, and use the rock-solid "igb" driver that you can be absolutely certain will be included in the stock kernel from any Linux distributionThe I350 controller chip has been in production since 2011 and Intel plans to manufacture it through 2031. It's fast, reliable, inexpensive, and uses only 2.8W of power. Those features, combined with the high availability of the chip has made it ubiquitous on server motherboards. As a result it's extremely well supported by any operating system you might want to use.Thie PCI interface on the card identifies itself as being built by Beijing Sinead Technology Co. The ethernet MAC address has the correct prefix (98:b7:85) for Shenzhen 10Gtek Transceivers, which matches the name of the seller on Amazon. That's always a good sign; they're using properly assigned MAC addresses rather than just cloning some other card.The card appears to be identical to the I350 cards sold by Intel. The only difference is the price, which is less than half what Intel charges.I'll probably buy more of these in the future. Great pricing and like the other 10Gtek products I've purchased in the past it's a solid product.

Works perfectly for me

In my homelab, I have a pretty robust server based around Proxmox 7.1, an AMD 5950X and 128GB of RAM. It's a sweet little playground. I wanted to play around with virtualized firewalls, particularly PFSense. The cheapest way I could find to do it was by adding NIC's to my existing server.I selected this dual NIC primarily because it used an x1 PCIe interface. My mainboard has two of these slots. The 4 port version is an x4 PCIe and my mainboard has none of these, meaning I'd have to use the x16 slot. I generally prefer to reserve my higher end x16 PCI slots for more capable hardware, not a basic 1G multi-NIC.Install was standard PCIe, about as simple as it gets. I read the reviews indicating compatibility with Proxmox and I can attest that it works well in my 7.1 build. I had the typical issue where Linux's dynamic network interface monitoring feature jacked up my interface name and bridge configuration. Easily fixed with a trip to /etc/network/interfaces though. (And to be sure, this is a Linux issue, not a hardware one.)I've had my setup going for a few months now with no troubles. I don't know much about this network card, such as who makes it or where to get drivers that I didn't need in Proxmox. That hasn't seemed to matter. Oh, and if you're interested in virtualized firewalls, I'd encourage you to explore it. I've had a lot of fun with PFSense so far.

The card works, yet the connector between the M.2 card and the LAN socket can be connected wrongly as there is no marking to guide user (therefore 4 stars). Luckily there were no repercussions of performance after the connector was flipped to rectify wrong connection.Other than that - seems good product.In my case the I have returned the cards as I could not fit properly the cards in my Lenovo M90q.

Very good product and working fine with pfsense and good performance with suricata IPS inline mode.pciconf -lcv #Output of pciconf command on freebsd.igb2@pci0:3:0:0: class=0x020000 card=0xa03c8086 chip=0x10c98086 rev=0x01 hdr=0x00vendor = 'Intel Corporation'device = '82576 Gigabit Network Connection'class = networksubclass = ethernetcap 01[40] = powerspec 3 supports D0 D3 current D0cap 05[50] = MSI supports 1 message, 64 bit, vector maskscap 11[70] = MSI-X supports 10 messages, enabledTable in map 0x1c[0x0], PBA in map 0x1c[0x2000]cap 10[a0] = PCI-Express 2 endpoint max data 128(512) FLRlink x1(x4) speed 2.5(2.5) ASPM disabled(L0s/L1)ecap 0001[100] = AER 1 0 fatal 0 non-fatal 1 correctedecap 0003[140] = Serial 1 6cb311ffff1b17c0ecap 000e[150] = ARI 1ecap 0010[160] = SR-IOV 1 IOV disabled, Memory Space disabled, ARI disabled0 VFs configured out of 8 supportedFirst VF RID Offset 0x0180, VF RID Stride 0x0002VF Device ID 0x10caPage Sizes: 4096 (enabled), 8192, 65536, 262144, 1048576, 4194304igb3@pci0:3:0:1: class=0x020000 card=0xa03c8086 chip=0x10c98086 rev=0x01 hdr=0x00vendor = 'Intel Corporation'device = '82576 Gigabit Network Connection'class = networksubclass = ethernetcap 01[40] = powerspec 3 supports D0 D3 current D0cap 05[50] = MSI supports 1 message, 64 bit, vector maskscap 11[70] = MSI-X supports 10 messages, enabledTable in map 0x1c[0x0], PBA in map 0x1c[0x2000]cap 10[a0] = PCI-Express 2 endpoint max data 128(512) FLRlink x1(x4) speed 2.5(2.5) ASPM disabled(L0s/L1)ecap 0001[100] = AER 1 0 fatal 0 non-fatal 1 correctedecap 0003[140] = Serial 1 6cb311ffff1b17c0ecap 000e[150] = ARI 1ecap 0010[160] = SR-IOV 1 IOV disabled, Memory Space disabled, ARI disabled0 VFs configured out of 8 supportedFirst VF RID Offset 0x0180, VF RID Stride 0x0002VF Device ID 0x10caPage Sizes: 4096 (enabled), 8192, 65536, 262144, 1048576, 4194304

Absolutely does not work. I spent 4 hours troubleshooting this before concluding the card is defective. Monumental waste of time.

Motherboards Ethernet cord was extremely faulty. Put this in the pcie and haven’t worried about it since. Great connectivity works a charm!

This was a perfect replacement for my Proxmox system, the onboard nic was a realtek and started giving me errors. I wish I bought a two port version so I could play with opnsense, but I'm sure their will be opportunity later.