#iperf3 — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #iperf3, aggregated by home.social.
-
A request came in to add iperf3 3.20 to BashCore.
iperf3 is a solid, widely used tool for real network performance testing (TCP/UDP, throughput, jitter, loss...).
I started using it recently while working with Buildroot, and it fits BashCore’s minimal approach very well.
It will be available soon in upcoming BashCore releases 😉
-
A request came in to add iperf3 3.20 to BashCore.
iperf3 is a solid, widely used tool for real network performance testing (TCP/UDP, throughput, jitter, loss...).
I started using it recently while working with Buildroot, and it fits BashCore’s minimal approach very well.
It will be available soon in upcoming BashCore releases 😉
-
A request came in to add iperf3 3.20 to BashCore.
iperf3 is a solid, widely used tool for real network performance testing (TCP/UDP, throughput, jitter, loss...).
I started using it recently while working with Buildroot, and it fits BashCore’s minimal approach very well.
It will be available soon in upcoming BashCore releases 😉
-
A request came in to add iperf3 3.20 to BashCore.
iperf3 is a solid, widely used tool for real network performance testing (TCP/UDP, throughput, jitter, loss...).
I started using it recently while working with Buildroot, and it fits BashCore’s minimal approach very well.
It will be available soon in upcoming BashCore releases 😉
-
A request came in to add iperf3 3.20 to BashCore.
iperf3 is a solid, widely used tool for real network performance testing (TCP/UDP, throughput, jitter, loss...).
I started using it recently while working with Buildroot, and it fits BashCore’s minimal approach very well.
It will be available soon in upcoming BashCore releases 😉
-
⚠️ CVE-2025-54351: HIGH-severity buffer overflow in ES iperf3 (<3.19.1) via --skip-rx-copy. Remote attackers can impact confidentiality/integrity. Upgrade to 3.19.1 & restrict access. Details: https://radar.offseq.com/threat/cve-2025-54351-cwe-420-unprotected-alternate-chann-916a43de #OffSeq #iperf3 #CVE202554351 #infosec
-
⚠️ CVE-2025-54351: HIGH-severity buffer overflow in ES iperf3 (<3.19.1) via --skip-rx-copy. Remote attackers can impact confidentiality/integrity. Upgrade to 3.19.1 & restrict access. Details: https://radar.offseq.com/threat/cve-2025-54351-cwe-420-unprotected-alternate-chann-916a43de #OffSeq #iperf3 #CVE202554351 #infosec
-
⚠️ CVE-2025-54351: HIGH-severity buffer overflow in ES iperf3 (<3.19.1) via --skip-rx-copy. Remote attackers can impact confidentiality/integrity. Upgrade to 3.19.1 & restrict access. Details: https://radar.offseq.com/threat/cve-2025-54351-cwe-420-unprotected-alternate-chann-916a43de #OffSeq #iperf3 #CVE202554351 #infosec
-
⚠️ CVE-2025-54351: HIGH-severity buffer overflow in ES iperf3 (<3.19.1) via --skip-rx-copy. Remote attackers can impact confidentiality/integrity. Upgrade to 3.19.1 & restrict access. Details: https://radar.offseq.com/threat/cve-2025-54351-cwe-420-unprotected-alternate-chann-916a43de #OffSeq #iperf3 #CVE202554351 #infosec
-
⚠️ CVE-2025-54351: HIGH-severity buffer overflow in ES iperf3 (<3.19.1) via --skip-rx-copy. Remote attackers can impact confidentiality/integrity. Upgrade to 3.19.1 & restrict access. Details: https://radar.offseq.com/threat/cve-2025-54351-cwe-420-unprotected-alternate-chann-916a43de #OffSeq #iperf3 #CVE202554351 #infosec
-
Es que #WíreGuard está a otro nivel... Es un cable seguro "literal" 😆 #iperf3
-
Es que #WíreGuard está a otro nivel... Es un cable seguro "literal" 😆 #iperf3
-
Es que #WíreGuard está a otro nivel... Es un cable seguro "literal" 😆 #iperf3
-
Netzwerkdurchsatz mit #iperf3 messen #raspberrypi
https://raspithek.de/software/tools/netzwerkdurchsatz-mit-iperf3-messen/
-
Netzwerkdurchsatz mit #iperf3 messen #raspberrypi
https://raspithek.de/software/tools/netzwerkdurchsatz-mit-iperf3-messen/
-
Netzwerkdurchsatz mit #iperf3 messen #raspberrypi
https://raspithek.de/software/tools/netzwerkdurchsatz-mit-iperf3-messen/
-
Netzwerkdurchsatz mit #iperf3 messen #raspberrypi
https://raspithek.de/software/tools/netzwerkdurchsatz-mit-iperf3-messen/
-
me@pi5:~ $ iperf3 -4 -R -c server
...
[ ID] Interval Transfer Bitrate Retr
[ 5] 0.00-10.00 sec 1.08 GBytes 932 Mbits/secNice!
-
me@pi5:~ $ iperf3 -4 -R -c server
...
[ ID] Interval Transfer Bitrate Retr
[ 5] 0.00-10.00 sec 1.08 GBytes 932 Mbits/secNice!
-
me@pi5:~ $ iperf3 -4 -R -c server
...
[ ID] Interval Transfer Bitrate Retr
[ 5] 0.00-10.00 sec 1.08 GBytes 932 Mbits/secNice!
-
me@pi5:~ $ iperf3 -4 -R -c server
...
[ ID] Interval Transfer Bitrate Retr
[ 5] 0.00-10.00 sec 1.08 GBytes 932 Mbits/secNice!
-
me@pi5:~ $ iperf3 -4 -R -c server
...
[ ID] Interval Transfer Bitrate Retr
[ 5] 0.00-10.00 sec 1.08 GBytes 932 Mbits/secNice!
-
ok, the udp was solved by specifying bigger #iperf3 `-b` , but single tcp connection remains clamped and only bandwidth use scales only with `-P` setting :/
-
ok, the udp was solved by specifying bigger #iperf3 `-b` , but single tcp connection remains clamped and only bandwidth use scales only with `-P` setting :/
-
ok, the udp was solved by specifying bigger #iperf3 `-b` , but single tcp connection remains clamped and only bandwidth use scales only with `-P` setting :/
-
Replacing “iperf3” with “ntttcp” to measure networking throughput in reviews
One of the things I test when reviewing mini PCs for Liliputing is WiFi performance or network throughput. And up until recently I’ve used the popular iperf3 tool to do that, since it allows me to see how real-world performance compares with the speeds you’d expect from the specifications provided by WiFi chip makers.
For some time though, I’ve […] -
#Microsoft on why you should not use #iperf3 on #Windows, but #ntttcp or #ctsTraffic instead. https://techcommunity.microsoft.com/t5/networking-blog/three-reasons-why-you-should-not-use-iperf3-on-windows/ba-p/4117876
-
Good to know, that the home network works fine 😊
-
Such an excellent post by @ryanhuber at Defined.
I remember Ryan & Nate working heavily with me - for free - in 2019 to help me get the best performance out of Nebula in my lab. This post builds on that work, and also answers a lot of confusion around VPN performance and tools like iperf3.
A must read for anyone considering mesh VPN / overlay solutions.
#Nebula #iperf3 #Mesh #VPN #Networking #Linux #Golang
https://www.defined.net/blog/nebula-is-not-the-fastest-mesh-vpn/
-
#iPerf3 for Windows is...a mystery. Sending UDP packets one way works enormously well. Using -R for reversing the role of server and client brings me 30% packet losses at 40 Mbps.
Yet the Windows-own logging (Performance Monitor) does not show any packet losses, so it must be an application-site loss.
-
Ok, some more info. Decided to do some basic #benchmark. Run #iperf3 on it. I was able to get gigabit against my desktop. No routing, I have just one network card. But I tried #veth interfaces and benchmarked throughput between two namespaces and got to 7 gigabits. #cryptsetup benchmarks just #aes-cbc and claims 40MiB/s for 128b and 30MiB/s for 256b which sounds like no accelerator is used and support for other ciphers might be missing from the kernel. Still using official firmware - no time to reinstall yet.
-
SD card in my #StarFive #VisionFive2 #RiscV #SBC died (it was a "great deal" SD card for few bucks bought primarilly to save on shiping costs), so before fixing it I decided to try some benchmark on it - since I have to reinstall it anyway. I tried how good router it is (too see how far away future is #RiscV #Turris #Router), but unfortunatelly even #Iperf3 got only to 700Mbps with NAT (6.7.0 kernel, Firewalld on openSUSE). Well, time to reinstall it and get it back to being home server...
-
#OpenBSD's #iperf3 port now uses pledge(2)/unveil(2), depending on options significantly reduces or entirely drops filesystem access.
And it's been submitted upstream. Nice. :flan_thumbs:
https://marc.info/?l=openbsd-ports-cvs&m=169866800408635&w=2
-
This may be my most truly cursed #cli ever for graphing #network performance?
This one has everything, a hand rolled artisanal #iperf3, some #json feature extraction, and a spot of #awk for fixing rounding errors, oh and of course, some red hot #gnuplot on #linux #terminal action.
Enjoy! hehe. 😆
./src/iperf3 -c testhost -p 22222 -J | jq '.intervals[].sum.bits_per_second' | awk '{$1=sprintf("%2.2f",$1)}1' | gnuplot -p -e "set term dumb ; plot '< cat -' with lines"
/cc @climagic
-
I love how #Chainguard Images continues to patch security issues before there is even a #CVE issued.
- #CVE-2023-38403 (#iperf3): Patched same day as announcement (8 days before CVE)
- #CVE-2023-3446 (#openssl): Patched same day as announcement
- #CVE-2023-38408 (#openssh): Patched same day as announcementThat's the beauty of automation and testing.
-
Hm, this can actually be the #MacOS #Ventura 13.3.1 update, seems to have made networking quite funky. Between reboots right after another, I've seen:
* normal download / broke upload;
* half-speed download / normal upload;
* normal speed but retry-heavy download / normal-ish uploadOn WiFi, measured with #iperf3 to another server on the LAN. A bit weird one,, have to keep an eye out for it...
-
Continuation of my network problems between #Windows 10 and certain remote network behind a #Mikrotik. Funny fact - Linux client from same local network works fine. And today I've found out that #iperf3 running in parallel mode achieves proper speed as well - though streams are slow as before, but the sum is good. Now I wonder WTF is going on with single streams. And I'm talking about up to 60 Mbps/s, not Gigabits of bandwidth.
-
#Network gurus, any idea why would (#Windows 10?) throttle upload network bandwidth to a specific (#mikrotik) router? computer->mikrotik->5G->FTTH->mikrotik->server. It always throttles it to ~2Mb/s (it should be at least 10Mb/s). From all the combinations I tested, it seems happening only with this computer to that router. From Mac and phones it works as expected. Testing using #iperf3.
-
Ok, some more info. Decided to do some basic #benchmark. Run #iperf3 on it. I was able to get gigabit against my desktop. No routing, I have just one network card. But I tried #veth interfaces and benchmarked throughput between two namespaces and got to 7 gigabits. #cryptsetup benchmarks just #aes-cbc and claims 40MiB/s for 128b and 30MiB/s for 256b which sounds like no accelerator is used and support for other ciphers might be missing from the kernel. Still using official firmware - no time to reinstall yet.
