Knowledge base : Download Area > ByteBlower > Previous Releases > ByteBlower GUI

64-bit Beta now also available for Mac!

We now fully support macOS version 11 Big Sur and newer.
Download the GUI from

Changelog 2.15.0

  • Support for macOS version 11 Big Sur and newer. The GUI has been tested and approved for usage on Apple devices with an M1 processor. In addition, the GUI has also been approved for macOS Monterey.
  • To avoid confusion, project specific preferences are only enabled when there is a project open.
Bug Fixes
  • Fix in the CSV results, the correct PortName is now used in the TCP and HTTP results over time.
  • In CCDF graphs in HTML reports, incorrect latency values were displayed on the horizontal axis.
Known Issues
  • On Mac, the Dark Mode is not activated automatically at night.
  • Regenerating results fails in reports with TCP flows.
  • No ByteBlower CLT yet.

Changelog for ByteBlower Endpoint 2.20

The ByteBlower Endpoint can be downloaded through our setup pages: 

For Android, iOS and iPadOS, the app is also available through their respective app stores.

ByteBlower Endpoint Changelog for 2.20.0 


New features 

  • Adding latency histograms over time.  This can be used to visualise/verify the QeD performance of a specific application. 


  • Adding additional frameblasting interval statistics such as : 
    • When was the first frame sent or received 
    • When was time last frame sent or received 
    • Minimum and maximum size of the frames received 
  • Better latency measurements for cumulative snapshots.   
    -The Endpoint now keeps track of the cumulative data itself instead of delegating this to the MeetingPoint. 


  • Fixing crashes when a management/traffic interface was selected, but no IP address was available. 

Older versions


2.20.0  (2023-02-14)


Increased robustness of RFC-2544 for WEP

  • RFC2544 is a widely known benchmark. The ByteBlower GUI implements the throughput measurement.
  • In the past, tests would more likely fail due to the stress the test places on the network.
  • RFC-2544 places a heavy load on the system. For fail-safe tests it’s recommended to add route the WEP mgmt. traffic over a different interface like e.g., the golden client.

UI improvements in the ByteBlower server updater. 

When errors happen resuting in failed tests, we have implemented improved logging which makes the feedback of the server more visible.

  • Improved logging of error-cases from the ByteBlower Server.
  • More efficient debugging as as a result.
  • Some examples of error messages
    • Code
    • Improper license
    • Broken updater that was fixed in later releases.


Improved default TCP setting.

  • New default value for TCP Slow Start Threshold: 2147483647 (=Integer.MAX_VALUE) (=infinite). The old default was 65535 (=0xFFFF).
  • OS behaviour is closer to infinite value.

CCDF Graph

An empty CCDF graph is now drawn in the ByteBlower report when all packets are below the latency measurement range. This can happen due to negative latencies of a Wireless Endpoint. See also our Golden client KB article to perform such tests. 

TCP Restart

In the summer of 2018, we’ve introduced the option to automatically restart a broken TCP session. This feature provided continuous TCP traffic, even when the network itself encountered hiccups.
At that time, this feature was only available on the ByteBlower server ports. In this first major release of 2019, we are bringing this feature to ByteBlower Wireless Endpoints.
A big aid to test mobile devices even in difficult Wi-Fi environments.

Watch it in action in this short demonstration short demonstration video

Need a flexible NBASE-T test solution?

2019 will be the year of WiFi 6! With throughput rates rising beyond the magical 1 Gbit/s barrier, NBASE-T network connectivity will become much more common.
The NBASE-T add-on to ByteBlower gives you 2.5 and 5G test-capabilities in addition to your current system. This upgrade keeps you up to date with future developments to Ethernet connectivity without the expense of a whole new system.
Four different network technologies from just a single system!

What's coming next?

Meanwhile the next version is already being worked on, which is expected in the summer months. Some of the new features you can expect:

  • Interactive charts
  • Wi-Fi details ( RSSI/BSSID/...) in API where available
  • JSON reports preview


You can download this version of the GUI here:

Information on how to use the CLT version of the GUI: Introduction to ByteBlower CLT

Changelog 2.10.2 (27th of June 2019)

  • The ByteBLower-CLT prints out its version number on startup. This makes it easier to know which version you're using.
  • A cleaner handling of the command line arguments. Removed the stack-trace when the arguments are incomplete.
  • Fixed including the images in this changelog.

Changelog 2.10.0 (24th of April 2019)


  • Default TCP window scale is now 7. This is closer the most common value on the internet today. New TCP templates will use this value.
  • Easier solution text for Wireless Endpoints without IPv6 configuration.
  • We're now also generating a latency distribution chart is for broadcast flows.
  • The support-portal and tutorial site are now accessible through the help-menu ( Help->Support Portal | Help->Tutorials ) .
  • You can now create scenario's immediately from the Flow view. Select a couple flows and pick the last option in the right click menu.
  • Show the total burst duration in the middle info panel of the FrameBlasting View. This makes it easier to configure burst.
  • To make it easier working with many frames, the Frame view now shows you size and type of the frames.
  • The archive view additionally shows the size of the testresult database. This makes it easier to clean up the largest items.
  • The CLT creates the output and store directories if they woulnd't exist yet. That makes the CLT easier to use in scripts.
  • The Windows CLT now uses the console where it is started from, rather than opening a new window. This makes working with the Byteblower CLT much more easy. It has thus now the same behaviour as the eclispec.exe.
  • The GUI backups the project also when started with a batch.
  • Instead of 5 packets, discovery traffic is sent for the whole NATDiscovery period. The rate remains 10 pck/s. In total at most 200 packets will thus be sent out.
  • A Wireless Endpoint test will stop when the WE returns to reserved, even when the TCP flow fails to connect completely.
  • The duration column of a TCP flow will be colored red in the ByteBlower report when a TCP flow doesn't reach its configured duration.

Bug fixes

  • Filenames of the reports are now unique filenames. This fixes an edgecase where multiple tests finish within the same second.
  • More robust Archive view. Fixed nullpointer exception when no format was found.
  • The edit button in the Frame Blasting view is disabled when no project is open.
  • The 'open HTML' button will always open the HTML report and not the one currently selected.
  • Made the UI more robust. Fixed null-pointer exceptions found in the GUI logs.
  • The save-as view tried to update itself after canceling. This generated hidden exceptions in the log.
  • Fixed a couple exceptions that occur when closing of the ByteBlower GUI. These were found in the Eclipse log.
  • Fixed hidden Exception when clearing the initial receive window size value in the TCP view.
  • Restarted TCP sessions using the same TOS values, slow start threshold, maximum receive window as the original session"
  • Result gathering works subtly different between MeetingPoint and ByteBlower server. As a result the same values were stored multiple times in the result-database. This was corrected in the backend. This tends to happend when stopping the test early.
  • The First HTTP and TCP snapshots are now always retrieved. In the past they were occasionally lost.
  • Changes in how the results are stored has solved the duplicated results in the CSV report.
  • A run-title (top, action bar) with ending spaces caused issues during report generation. These spaces are now trimmed away.
  • The table at the right-bottom corner of the Multicast view is now cleared on startup. It was initialized with the wrong data.
  • Changing the ethertype of a frame in the Frame View didn't also clear all state. Checksums for instance were still calculated.
  • Fixed null-pointer exception that happened when selecting multiple reports in the archive view and pressing enter"
  • Cleanup statusbar-text of the hexeditor in the frame view.
  • Our test-database was the cause of a number of bugs. We've updated the library to the latest stable version. This new release is unaffected.
  • Deleting many scenarios in a single batch triggered concurrency issue. This bug has been solved.

Introducing Cumulative Latency Distribution Graphs

The ByteBlower GUI reports now contain CDF and CCDF latency graphs:

100 Gbit testing

The new ByteBlower 5100 model is specially designed to allow fast and easy testing on high-speed,
100 Gbit ethernet networks. It provides best-in-class latency measurements and 100 Gbit performance.

ByteBlower 5100


You can download this version of the GUI here: Download GUI

Information on how to use the CLT version of the GUI: Introduction to ByteBlower CLT

Changelog 2.12.4

This a bugfix release based on feedback received at All feedback is welcome.

Bug fixes

  • Comparing the cumulative TCP results to the results over time showed that the first data-point was sometimes missing. In the graphical reports this made a minor difference in the startup phase of the charts.
  • CSV reports now also list the cumulative TCP throughput for traffic transmitted by the Wireless Endpoints. The other direction was already calculated.
  • A fix in the the JSON reports: the current round trip time in the results over time of the TCP element now has the correct value.

Changelog 2.12.2

New features

  • [Reporting] Additional CDF and CCDF reporting. This is the main feature of this release.


  • [General] Updated TCP options in the TCP view.
    • The default congestion algorithm is now Sack + Cubic, similar to most modern Operating Systems.
    • Window scale values now range up to 12. The default value stays at 7, which is a commonly used one.
  • [General] Latency Distributions have been renamed to Latency Histograms.

Bug fixes

  • [General] To save time, NAT Discovery now skips flows where the source or destination failed to configure. These discoveries would fail either way but would require a long time to do so.
  • [Reporting] The TCP roundtrip element in the JSON report has now the correct value.

Changelog 2.12.0


  • [General] The GUI can now also control the new 100G ByteBlower 5100 server.
  • [Reporting] Improved JSON reports. Snapshots are ordered now.
  • [Reporting] Using milliseconds by default for latencies.
  • [Reporting] Using Mbps by default for throughputs.
  • [Reporting] Additional logging in the report browser. This will help debugging.
  • [Reporting] Less memory usage while generating JSON reports, by using a streaming approach.
  • [Reporting] Opening a report automatically after a scenario finished, but only when there are test results.
  • [UI] Showing help when relaunching a scenario that became invalid. Also opening the Solution View now.

Bug fixes

  • [General]: Adding a frame size filter for 60 byte frames also. This makes the filter more selective and avoids counting other large sized frames.

Known issues

  • [General]: The GUI is not yet fully compatible with macOS 11 Big Sur. Contact us to get a development version.

More info, less bytes in ByteBlower Captures

We are delighted that in this new release of ByteBlower GUI v2.13 the PCAP capture has been improved! This allows you to easily collect relevant network traffic.
The new features allow you to:
  • Filter traffic easily, keeping only the interesting packets
  • Truncate packets to the headers that matter