# IPFire Kernel Optimizations for 10Gb WAN + LAN

**URL:** <https://community.ipfire.org/t/ipfire-kernel-optimizations-for-10gb-wan-lan/15353>\
**Category:** Hardware\
**Created:** [16 December 2025 18:10 UTC](https://community.ipfire.org/t/ipfire-kernel-optimizations-for-10gb-wan-lan/15353 "2025-12-16T18:10:12Z")\
**Posts on this page:** 1\
**Showing post:** 8

<div class="post-metadata">

**Author:** ![ms](https://community.ipfire.org/user_avatar/community.ipfire.org/ms/32/16615_2.png) [@ms](https://community.ipfire.org/u/ms)\
**Post date:** [19 December 2025 12:35 UTC](https://community.ipfire.org/t/ipfire-kernel-optimizations-for-10gb-wan-lan/15353/8 "2025-12-19T12:35:03Z")

</div>

Hello,

> [@pscar13](#):
>
> After the not very constructive discussion about 10Gb WAN problems, I looked into the differences in Linux kernel configuration between VyOS and IPFire.

Well, let’s make this into a constructive one…

> [@pscar13](#):
>
> ```auto
> -# CONFIG_NUMA is not set
> +CONFIG_NUMA=y
> 
> ```

The NUMA changes won’t have any effect on your system because the i3 CPU that you are using won’t have more than one NUMA node.

> [@pscar13](#):
>
> ```auto
> -# CONFIG_IOMMU_DEFAULT_PASSTHROUGH is not set
> +CONFIG_IOMMU_DEFAULT_PASSTHROUGH=y
> 
> ```

As @arne_f has already said, this will introduce some security issues because the hardware would be able to access any memory it desires. Any compromised firmware and so on would be able to read security credentials.

With IPFire, we usually harden the OS against compromised hardware. Obviously it is not possible to do this 100%, because if the hardware is fully compromised, the OS cannot trust anything, but at the same time, there could only be some smaller parts of the hardware being vulnerable. With more and bigger firmware blobs loaded into network interfaces, WiFi modules, storage controllers and so on; with a huge UEFI/BIOS that cannot be audited at all, this seems to be a sensible choice on our behalf.

So why do you see such a big change on your system? It can only be explained that the CPU is quite poor with any kind of IOMMU operations. Whenever the driver wants to send or receive data from the NIC, it has to do some extra work if running in strict mode. That should normally have very little overhead (a few percent, if even). But if the IOTLB or the DMA pages don’t fit into the CPU’s caches, the CPU is spending a lot of time waiting for data. This is quite likely happening here. I don’t think that this is for example repeatable on an Intel Xeon CPU that is simply designed for heavy I/O load compared to the rather power-efficient i3 series.

The huge drop in IPS throughput can also be explained by the CPU having too small buffers and the Spectre/Meltdown measures having a particularly high toll.

Since this is all a runtime setting, you could try to boot the regular IPFire kernel and pass “iommu.passthrough=1” to the kernel command line. That will enable the passthrough mode for you (if you want to trust your hardware) and you should be able to see the faster benchmark results. That would also help us to rule out NUMA.

> [@nickh](#):
>
> Interesting article on tuning Linux for network speed at [Fornax’s Guide To Ridiculously Fast Ethernet ~ pixeldrain](https://pixeldrain.com/100_gigabit_ethernet), but keep clear of IOMMU, it seems.

Although these guides are not wrong per se, they simply don’t apply in the general case. Someone is optimising for a very specific task and aims to bring up throughput (at all costs). Having good latency is at least as important as having good throughput, if not even more important, so we simply cannot take all these settings and apply them to IPFire unless you want to have broken up calls, and small packets being queued inside buffers for seconds.

IPFire is deployed in so many all-round situations. Therefore we are making compromises. IPFire is also running all sorts of hardware, and once again, that has to come with some hard choices that very often sacrifice performance.

The easiest way to keep things fast and secure at the same time would simply be to upgrade the hardware. A desktop-grade i3 CPU is not designed to push tens of gigabits of packets. It can do that, somewhat, but in this specific case it seems that we have to turn off all the security measures.

I would rather replace my hardware before I have my network compromised though…

---

_[View the full topic](https://community.ipfire.org/t/ipfire-kernel-optimizations-for-10gb-wan-lan/15353)._
