Recent posts

#1
Quote from: nero355 on Today at 06:30:17 PMOK, but this clearly shows there is something wrong with the OPNsense Mini PC itself :
Quoteiperf3:
1.60 Gbits/sec from Win11 to OPNsense iperf3 server.
2.37 Gbits/sec from Win11 to Unraid (N95) iperf3 server.
These two should always be equal IMO :)

No:

1. There is a big difference between OpnSense routing sessions between different partners and OpnSense being the endpoint (the latter one is slower).

2. Since this is iperf, I also like to point out this article, point 10. I totally depends on how many TCP sessions you use.

Pulling these together, I see ~1.87 Gbps with iperf -P1 vs. 3.56 Gbps with iperf -P4 vs. 6 Gbps when OpnSense routes only.
#2
I'll get a Linux based Live Boot up over the next few days and give it a test, plus maybe a fresh OPNsense basic install on a spare drive.
#3
Quote from: meyergru on Today at 06:15:06 PMThere are big timing differences between internet and local connections and also, the endpoints can behave differently, thus there can be any number of problems w/r to timing and/or buffering.
The latter depends on which TCP algorithms are in use, such that flow control and buffering or interrupt coalescing can very well play a role.
OK, but this clearly shows there is something wrong with the OPNsense Mini PC itself :
Quote from: Ozymandias on June 06, 2026, 11:39:10 PMiperf3:
1.60 Gbits/sec from Win11 to OPNsense iperf3 server.
2.37 Gbits/sec from Win11 to Unraid (N95) iperf3 server.
These two should always be equal IMO :)

To rule out FreeBSD specific issues he could also test with a random Linux based Live Boot Environment now that I think of it...
#4
An intel core i5 also has a way higher TDP.

About the UDP vlan fragmentation issue, on a DEC device you can solve that in Interfaces: Settings by enabling vlan hardware filtering.
#5
Quote from: ou1 on Today at 06:08:40 PMjust a quick update - I decided to try some different hardware. I loaded my config into the following machine:

M920q, Intel i5-8500T, Intel X710-DA2, 16GB RAM

The performance increased dramatically.

iperf3 single stream went from 2Gbps to 4.6Gbps
iperf3 multi-stream went from 5Gbps to 9.2Gbps

CPU load peaks at 50% then drops during the tests.

It's not as compact and elegant as my DEC750, and I cut a hole in the top for a fan, but it seems much more powerful.
Make sense I guess when you do a quick search for some comparisons : https://duckduckgo.com/?q=AMD+V1500B+vs+Intel+i5-8500T&ia=web

It's simply the better choice performance-wise :)
#6
Quote from: nero355 on Today at 06:07:27 PM
Quote from: Ozymandias on June 06, 2026, 11:39:10 PMPeaks at about 40%.

iperf3:
1.48 Gbits/sec from the router to a public server.
1.28 Gbits/sec from Win11 to the same public server.
1.60 Gbits/sec from Win11 to OPNsense iperf3 server.
2.37 Gbits/sec from Win11 to Unraid (N95) iperf3 server.
I forgot to mention this :
Quote from: dirtyfreebooter on Today at 03:28:26 AMI did update my i226 firmwares to v2.32 tho i dont think that mattered.
So have a look at this topic : https://forum.opnsense.org/index.php?topic=48695.0

Maybe that's the issue here...

Quote from: meyergru on Today at 08:35:27 AMI have tested the pure routing speed of N100-based OpnSense systems between VLANs to ~6 Gbps, so that should work.
NICE! :)

So far I only knew that a N100 can satisfy the 2,5 Gbps NICs out there as long as you don't use any IDS/IPS stuff.

QuoteW/R to the Windows 11 system, I have seen network drivers that needed tuning to exceed 1.5 Gbps on some network adapters, like disabling interrupt moderation, enlarge buffer sizes or changing flow of control settings.
He got good speeds to his DIY NAS :
Quote2.37 Gbits/sec from Win11 to Unraid (N95) iperf3 server.
So I am guessing that's not the issue...

There are big timing differences between internet and local connections and also, the endpoints can behave differently, thus there can be any number of problems w/r to timing and/or buffering. The latter depends on which TCP algorithms are in use, such that flow control and buffering or interrupt coalescing can very well play a role.
#7
Hardware and Performance / Re: DEC750 realistic 10G expec...
Last post by ou1 - Today at 06:08:40 PM
just a quick update - I decided to try some different hardware. I loaded my config into the following machine:

M920q, Intel i5-8500T, Intel X710-DA2, 16GB RAM

The performance increased dramatically.

iperf3 single stream went from 2Gbps to 4.6Gbps
iperf3 multi-stream went from 5Gbps to 9.2Gbps

CPU load peaks at 50% then drops during the tests.

It also seems to have solved an issue with invalid checksums for fragmented UDP packets on non-default VLAN.

It's not as compact and elegant as my DEC750, and I cut a hole in the top for a fan, but it seems much more powerful.
#8
Quote from: Ozymandias on June 06, 2026, 11:39:10 PMPeaks at about 40%.

iperf3:
1.48 Gbits/sec from the router to a public server.
1.28 Gbits/sec from Win11 to the same public server.
1.60 Gbits/sec from Win11 to OPNsense iperf3 server.
2.37 Gbits/sec from Win11 to Unraid (N95) iperf3 server.
I forgot to mention this :
Quote from: dirtyfreebooter on Today at 03:28:26 AMI did update my i226 firmwares to v2.32 tho i dont think that mattered.
So have a look at this topic : https://forum.opnsense.org/index.php?topic=48695.0

Maybe that's the issue here...

Quote from: meyergru on Today at 08:35:27 AMI have tested the pure routing speed of N100-based OpnSense systems between VLANs to ~6 Gbps, so that should work.
NICE! :)

So far I only knew that a N100 can satisfy the 2,5 Gbps NICs out there as long as you don't use any IDS/IPS stuff.

QuoteW/R to the Windows 11 system, I have seen network drivers that needed tuning to exceed 1.5 Gbps on some network adapters, like disabling interrupt moderation, enlarge buffer sizes or changing flow of control settings.
He got good speeds to his DIY NAS :
Quote2.37 Gbits/sec from Win11 to Unraid (N95) iperf3 server.
So I am guessing that's not the issue...
#9
General Discussion / Re: NetFlow Traffic Diagram WA...
Last post by Smash - Today at 06:05:16 PM
I wonder why a multi-gig switch isn't configured for this scenario by default though...

And the issue of this OP is back. The Traffic Graph worked for a while, but now WAN is missing again, really no idea why
#10
General Discussion / Re: NetFlow Traffic Diagram WA...
Last post by nero355 - Today at 05:59:28 PM
Quote from: Smash on June 06, 2026, 08:41:56 PMCurrently it seems that I fixed it by fixing another upload related issue: https://lemmy.world/post/47842833
There are issues out there with certain Switches when they need to buffer traffic between 1 Gbps and 10 Gbps indeed, so that's always something to watch out for :)