10GBASE-T RJ45 SFP+ Copper Module compatibility on Intel N150 Mini PC (non-axgbe

[alhaddar]

Hi everyone,

I recently got a Firewall Mini PC with the following specs:
- CPU: Intel N150
- Ports: 2x 10G SFP+ and 3x 2.5G (i226-V)
- RAM: DDR5
- Storage: NVMe
- OS: OPNsense (latest)

I'm looking to use the 10G SFP+ ports with a 10GBASE-T RJ45 Copper module instead of fiber or DAC, since I need to connect to standard Cat6a ethernet.

I know the official OPNsense compatibility list only covers their own hardware (axgbe-based appliances), and my device uses a different SFP+ controller.

Has anyone used a 10GBASE-T RJ45 SFP+ copper transceiver on a similar Mini PC setup running OPNsense?

Specifically I'd love to know:
1. Which module did you use? (brand/model)
2. Did it work out of the box or did it require any configuration?
3. Any issues with heat since the device is fanless?

Thanks in advance!

[meyergru]

Many of the "china boxes" use the Intel 82559 variants. Most SFP(+) modules should work in those, they use the ix driver.

It may be neccessary to disable ASPM if you experience link drops, by using hw.pci.enable_aspm=0 and dev.ix.0.fc=0 if you see packet drops. There is also hw.ix.unsupported_sfp, which can be set to 1 in order to enable some otherwise unsupported models.

The slot itself can only accommodate 1 and 10 Gbps, no NBase-T intermediate speeds. Some SFP+ modules can adapt NBase-T speeds to 10 GBps, but you cannot use GPON adapters at SGMII speeds.

That being said, 10 GbE SFP+ modules tend to get very hot, especially if you plan to use two in adjacent positions, you may need active cooling. I gave up on these in favor of DAC cables that use virtually no power at all, so I cannot recommend any specific brand or model.

[BrandyWine]

IIRC, the ix in kernel tree lists specific models of hardware, much of it being Intel stuff.
I would at least try and use an item that is specifically listed (some hardware has variants, so using, as example, 85523-v may not work if 85523 is listed), and, buy from a vendor that does not have questionable supply chain. The gold rule still applies, but low cost questionable stuff means higher probability of issues creeping out.

[pfry]

IIRC, the ix in kernel tree lists specific models of hardware, much of it being Intel stuff.[...]

I wouldn't expect third-party Atom-based devices to have network interfaces with a vendor-locked NVM... but you never can tell. My one actual Intel 82599 (= x520) is not, but most (but not all) of my x710s are. So as you pointed out, a recommended device is a safe bet. Before Patrick chimes in, there's always fs.com for compatibles.

[alhaddar]

Thank you, friends, for expressing your opinions.

[BrandyWine]

IIRC, the ix in kernel tree lists specific models of hardware, much of it being Intel stuff.[...]

I wouldn't expect third-party Atom-based devices to have network interfaces with a vendor-locked NVM... but you never can tell. My one actual Intel 82599 (= x520) is not, but most (but not all) of my x710s are. So as you pointed out, a recommended device is a safe bet. Before Patrick chimes in, there's always fs.com for compatibles.

Help me understand that. Atom based mobo? Vendor-locked NVM?
The in-tree driver code simply cannot house all devices. If the NIC used is in the tree (driver) code then its the P-&-P situation, should just work. Otherwise the NIC vendor should have a driver to install (my preferred method).

Post #1 seems to confuse OPNsense & FreeBSD. The hardware and OS versions determine what NICs will and will not work out-of-the-box.

Has anyone used a 10GBASE-T RJ45 SFP+ copper transceiver on a similar Mini PC setup running OPNsense?

If a 10GBASE-T RJ45 SFP+ copper transceiver is in any in-tree NIC driver for the OS version, then that specific model should be good to go. Other 10GBASE-T RJ45 SFP+ copper transceivers would need their own KLM to work.

[pfry]

Help me understand that. Atom based mobo? Vendor-locked NVM?[...]

I could have been more clear. Atom-based integrated system.

As far as the vendor lock, some (most) of my discrete Intel (Intel branded, not OEM) NICs (specifically x710 and e810) only support Intel-branded (in firmware) optics. It's not a driver issue; it appears to be built into the NVM. There is no vendor lock for DAC cables; I haven't tried a UTP SFP+ (I only have one, which sits in a drawer because it's a burning weenie roaster). (Shouldn't be an issue for the original poster.)

[alhaddar]

Hi everyone,

I've been researching a direct 10G connection between a Firewall Mini PC (with 2x 10G SFP+ ports) and an Intel X520-DA2 NIC installed in a separate server. Both sides use the same network chipset and driver.

Here's a quick compatibility summary based on my findings:

Item   Details
Chip on Firewall (built‑in SFP+)   Intel 82599ES
Chip on X520-DA2   Intel 82599ES
Driver (both ends)   ixgbe
DAC cable compatibility   ✅ Excellent – same chipset, passive DAC works natively
OPNsense support   ✅ Native support (ix driver / iflib)
Key takeaways:

Both endpoints use identical 82599ES controllers, so a direct passive SFP+ DAC cable works without protocol mismatches.

OPNsense supports these interfaces out of the box. If you use third‑party SFP+ modules, add the tunable:
hw.ix.unsupported_sfp = 1

No extra configuration is needed for a DAC cable straight between these two devices.

Hope this helps anyone building a similar 10G backbone between a firewall appliance and a server.

Feel free to share your own experiences or ask questions.

[alhaddar]

Hi ,

I recently made a post about my Firewall Mini PC specs. I mistakenly wrote that the CPU is an Intel N150, but the correct CPU is actually an Intel i3‑N300.

Here are the correct specifications:

    CPU: Intel i3‑N300

    Ports: 2x 10G SFP+ and 3x 2.5G (i226‑V)

    RAM: DDR5

    Storage: NVMe

    OS: OPNsense (latest)

My apologies for the confusion. The rest of the details about the 10GBASE‑T SFP+ modules and compatibility remain the same.

Thank you to everyone who responded, and I appreciate your understanding.