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.

I am using the network board in a running a pfSense firewall. It is providing firewall services for a medium size public library. Just a bit of volunteerism, so I appreacated the extremely rea.sonable price!Since the board features an Intel chipset, it is highly compatible with both pfSense (which does not like realtek network cards). The board has performed flawlessly.

I never really need wifi or bluetooth but having to use the pci slot for a 2.5gb card was annoying. This adapter freed up the slot and just gave new life to a bunch of boards. Perfect fit and detected by ubuntu and server 2022 without issue, getting 2.4gb+ speeds on downloads and file transfers.

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.

Works very well in my Lenovo M715q tiny pc.

I had high hopes for this card especially after reading the reviews. It turned out to be very disappointing. I purchased it for my OPNsense firewall and it was ok to get the drivers installed and was easily recognized. However, I don’t even know what it does, but the firewall’s console throws some errors regarding this NIC and after ~5 the console floods with output text that you can’t see because it flashes so fast and the computer reboots. This happens constantly. Stay away from Realtek products, intel NICs are expensive for a good reason.Another issue (not a big deal) but the standard profile bracket is a bit tall for my giant tower.

Working in a headless ubuntu os

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.