home.social

#iperf3 — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #iperf3, aggregated by home.social.

  1. Is #WiFI5 (802.11ac) usually around 117 Mbits/sec and #WiFi6 (802.11ax) around 331Mbits/sec? Just looking at some initial #iperf3 benchmarks.

  2. Is #WiFI5 (802.11ac) usually around 117 Mbits/sec and #WiFi6 (802.11ax) around 331Mbits/sec? Just looking at some initial #iperf3 benchmarks.

  3. Is #WiFI5 (802.11ac) usually around 117 Mbits/sec and #WiFi6 (802.11ax) around 331Mbits/sec? Just looking at some initial #iperf3 benchmarks.

  4. Is #WiFI5 (802.11ac) usually around 117 Mbits/sec and #WiFi6 (802.11ax) around 331Mbits/sec? Just looking at some initial #iperf3 benchmarks.

  5. Is #WiFI5 (802.11ac) usually around 117 Mbits/sec and #WiFi6 (802.11ax) around 331Mbits/sec? Just looking at some initial #iperf3 benchmarks.

  6. 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 😉

    #BashCore #Buildroot #Linux #Networking #iperf3 #FOSS

  7. 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 😉

    #BashCore #Buildroot #Linux #Networking #iperf3 #FOSS

  8. 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 😉

    #BashCore #Buildroot #Linux #Networking #iperf3 #FOSS

  9. 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 😉

    #BashCore #Buildroot #Linux #Networking #iperf3 #FOSS

  10. 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 😉

    #BashCore #Buildroot #Linux #Networking #iperf3 #FOSS

  11. ⚠️ 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: radar.offseq.com/threat/cve-20 #OffSeq #iperf3 #CVE202554351 #infosec

  12. ⚠️ 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: radar.offseq.com/threat/cve-20 #OffSeq #iperf3 #CVE202554351 #infosec

  13. ⚠️ 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: radar.offseq.com/threat/cve-20 #OffSeq #iperf3 #CVE202554351 #infosec

  14. ⚠️ 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: radar.offseq.com/threat/cve-20 #OffSeq #iperf3 #CVE202554351 #infosec

  15. ⚠️ 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: radar.offseq.com/threat/cve-20 #OffSeq #iperf3 #CVE202554351 #infosec

  16. Es que #WíreGuard está a otro nivel... Es un cable seguro "literal" 😆 #iperf3

  17. Es que #WíreGuard está a otro nivel... Es un cable seguro "literal" 😆 #iperf3

  18. Es que #WíreGuard está a otro nivel... Es un cable seguro "literal" 😆 #iperf3

  19. Hach, was so ne neue Firewall ausmacht. Da kommt die volle Brause daher. #Init7 #Fiber7 #iperf3

  20. Hach, was so ne neue Firewall ausmacht. Da kommt die volle Brause daher. #Init7 #Fiber7 #iperf3

  21. iPerf3 es una herramienta esencial para medir el rendimiento de tu red en macOS. Con comandos simples desde la Terminal, puedes evaluar ancho de banda, pérdidas y jitter en protocolos TCP/UDP. Instálalo con Homebrew y optimiza tus pruebas de red. #iPerf3 #macOS

  22. iPerf3 es una herramienta esencial para medir el rendimiento de tu red en macOS. Con comandos simples desde la Terminal, puedes evaluar ancho de banda, pérdidas y jitter en protocolos TCP/UDP. Instálalo con Homebrew y optimiza tus pruebas de red. #iPerf3 #macOS

  23. #raspberrypi #pi5 #iperf3

    me@pi5:~ $ iperf3 -4 -R -c server
    ...
    [ ID] Interval Transfer Bitrate Retr
    [ 5] 0.00-10.00 sec 1.08 GBytes 932 Mbits/sec

    Nice!

  24. #raspberrypi #pi5 #iperf3

    me@pi5:~ $ iperf3 -4 -R -c server
    ...
    [ ID] Interval Transfer Bitrate Retr
    [ 5] 0.00-10.00 sec 1.08 GBytes 932 Mbits/sec

    Nice!

  25. #raspberrypi #pi5 #iperf3

    me@pi5:~ $ iperf3 -4 -R -c server
    ...
    [ ID] Interval Transfer Bitrate Retr
    [ 5] 0.00-10.00 sec 1.08 GBytes 932 Mbits/sec

    Nice!

  26. #raspberrypi #pi5 #iperf3

    me@pi5:~ $ iperf3 -4 -R -c server
    ...
    [ ID] Interval Transfer Bitrate Retr
    [ 5] 0.00-10.00 sec 1.08 GBytes 932 Mbits/sec

    Nice!

  27. #raspberrypi #pi5 #iperf3

    me@pi5:~ $ iperf3 -4 -R -c server
    ...
    [ ID] Interval Transfer Bitrate Retr
    [ 5] 0.00-10.00 sec 1.08 GBytes 932 Mbits/sec

    Nice!

  28. 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 :/

  29. 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 :/

  30. ok, the udp was solved by specifying bigger `-b` , but single tcp connection remains clamped and only bandwidth use scales only with `-P` setting :/

  31. peculiar problem, #wireguard between #mikrotik #routeros and #netgate 2100 #pfsense. R->P is fully saturating the link ( 50Mbps ) while P-R is at its 1/100th ( link is 500Mbps ) and it barely does 5Mbps. Thats TCPv6. UDPv6 is only doing 1Mbps. Tests with #iperf3

  32. peculiar problem, #wireguard between #mikrotik #routeros and #netgate 2100 #pfsense. R->P is fully saturating the link ( 50Mbps ) while P-R is at its 1/100th ( link is 500Mbps ) and it barely does 5Mbps. Thats TCPv6. UDPv6 is only doing 1Mbps. Tests with #iperf3

  33. peculiar problem, between and 2100 . R->P is fully saturating the link ( 50Mbps ) while P-R is at its 1/100th ( link is 500Mbps ) and it barely does 5Mbps. Thats TCPv6. UDPv6 is only doing 1Mbps. Tests with

  34. 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 […]

    https://liliputing.com/?p=168164

    #iperf3 #networking #nttcp #wifi #wireless

  35. 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

    defined.net/blog/nebula-is-not

  36. 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

    defined.net/blog/nebula-is-not

  37. 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

    defined.net/blog/nebula-is-not