Knowledge base : Download Area > ByteBlower

Signal quality has a large impact on Wi-Fi performance. Since 2.11.0 of the ByteBlower Server, ByteBlower API and the Wireless Endpoint, it is now possible to map the RSSI, WiFi channel and the BSSID on your throughput!

Watch it here in action!


The downloads for windows/macOS/Linux are found at following location: .For Android and iOS you will find the apps in the app stores.

Changelog 2.11.4 (2019-09-18)

(Linux, macOS X and Windows only)

  • [Linux] Added support for Debian 10 and Ubuntu 20.04
  • [Windows] Fixing GUI initialization, resolving the attribute warning in the console.

Changelog 2.11.2 (2019-03-05)

  • [Windows] On some systems an unknown battery level was reported as 100%. This affected mostly Windows.
  • [Android] We now support from Android 7 till Android 11. To enable logging ESSID/BSSID/RSSI we had to drop Android 6 support.
  • [All] We’ve revised the FrameBlasting transmit approach. The new algorithm is better able to match the configured duration and rate, especially when the configured rate exceeds the available bandwidth. This occurs regularly in low bandwidth Wi-Fi environments, the excess bandwidth is dropped in these moments.
  • [macOS] Matching Apple guidelines we only use the essential capability set. Where possible we only use coarse Location to be able to monitor ESSID/BSSID.
  • [all] Fixed an issue where the device was marked as Booting Device when the device type contained a quote

Changelog 2.11.0 (2019-12-04)

  • Added support to collect the WiFi interface parameters over time: SSID/BSSID/Channel/RSSI/TxRate on supported devices.

You can find the detailed installation instructions in our How to: Install the Wireless Endpoint on your device.

This page contains the changelog for version 2.11 of the ByteBlower. How to update your ByteBlower server is explained in following article:

2.11.8 (2020-06-25)


  • Fixed an issue where the performance of a 3x00 server dropped significantly on v2.11.6
  • Adding timestamps to the standard output / error logs for the ByteBlower and MeetingPoint
  • DHCP protocol implements the elapsed time value. DHCP servers which rely on this field for high availability will now work as expected.

2.11.6 (2020-04-15)


  • Improve the transmit time accuracy of Frame Blasting flows.
  • The "Port.Create" method now works again on the ByteBlower 1200 series.
  • The ByteBlowerPort's result history counters can now be consumed by multiple ByteBlowerPort objects (each ByteBlowerPort contains its own copy of the result history.)
  • Configurator: IPv4 address validation failed when configuring static IP addresses on a management interface

2.11.4 (2020-02-20)


  • Fixed a bug which used unicast addresses in the DHCP requests. This could confuse some bridging devices which dropped the requests.


  • To help our support engineers, we now add the server and meetingpoint version to the logs.

2.11.2 (2020-02-11)

This release primarily focusses on bugfixes.

One of the fixes changes the default behaviour of the DHCP client running on a ByteBlower Port.  The DHCP Client used the broadcast DHCP-technique to obtain its IPv4 address.  As some customers noticed, some devices flagged this DHCP traffic as a broadcast storm when performing DHCP on multiple ByteBlower Ports.  This change in the ByteBlower DHCP client changes the default DHCP technique to the unicast technique, working around the limitation imposed by these devices.  The DHCP technique (broadcast/unicast) can be configured using the ByteBlower API.


  • Server: Added the possibility for the DHCP client to disable the BROADCAST bit in the DHCP flags.  The ByteBlowerPort will then use unicast packets when possible.
    Please note that this is now the default behaviour.  Using our API it is possible to revert to the older broadcast technique when needed.
  • Server: Added extra DHCP timing statistics (timestamps when the DHCP discover/offer/request/ack, DHCPv6 solicit, advertise, request, reply are sent or received)
  • MeetingPoint: Android 10 is now added to the list of supported operating systems.


  • Server: Fixed a crash when a ByteBlowerPort was being destroyed and the IGMP or MLD protocols needed to transmit messages.
  • Server: Fixes for IGMPv1 and IGMPv2 where an incorrect back-off interval was used.
  • Server: Fixed an issue where IGMPv1 did check the group address too much.
  • Configurator: Fixed a crash when the network configuration reached an inconsistent state.
  • MeetingPoint: Fixed a crash when the process got an interrupt signal

2.11.0 (2019-12-04)


  • The meetingpoint is aware of SSID, BSSID, RSSI, WiFi Channel and WiFi transmit rate on supported devices. To use these features you will also need to update the Wireless Endpoint on the device and the ByteBlower API installed  on your computer
  • The 24 port NBASE-T swtich for ByteBlower has been added to the byteblower-configurator. This makes it much easier tconfigure it.
  • Unsupported Operating Systems and devices can be registered at the MeetingPoint. This makes them available for test-runs. To make it clear that we've not yet tuned our code for the system we do add the 'unsupported' to the name of the device.


  • When requesting the result history on a Wireless Endpoint, all results were returned instead of only the new ones.  This resulted in growing histories (and thus memory usage) over time.
  • Improve TCP performance for flows that have a high number of packets in flight.
  • Fix packet duplication in Streams that have a small number of frames configured.

JSON reports: making it easy to process results in detail

You can now generate your ByteBlower reports in JSON format ! This is a beta feature, meaning that we are still actively developing it. We are already releasing this feature because we are convinced that it will bring you great benefits, even in its current state. Also, we 'd love to hear from you what you think of the JSON reports.

Enable the JSON results in the Preferences:

Remember, you can re-generate reports, using existing test data ! Click here to learn how to regenerate GUI reports

Interactive reports: getting a good grip on things

ByteBlower reports contain a lot of information. It may be difficult to interpret the graphs, especially in the case of large tests. Some plots appear to be stacked right over each other, hiding crucial info.

While we can't make your screen any larger, we can help you identify the events that matter.

This new release transforms all 6 results over time into interactive graphs. You can zoom in on them, hide plots you are not interested in and easily read the exact value at each point. An example of the new reports:

New tests use this interactive format by default, but we haven't forgotten your old results. Do you have an archived report you couldn't quite make sense of? You can regenerate it now in the report and inspect it in more depth.

Click here to see our Knowledge Base article about how to regenerate GUI reports.


When running tests, you often want a capture to investigate what is happening on your DUT/setup. You can now capture on the traffic ports through the GUI. Simply click to start the capture and all data is saved directly onto your hard drive; it's just a matter of opening Wireshark to start debugging. Below is an animated gif that shows how it's done:

Server Update Wizard

Updating your ByteBlower Server is now easier than ever! Even servers that have no direct connection with the internet can now be updated via the GUI. The new Server Update Wizard is available in the Server View. Here’s how it works:

Reports from a stopped CLT

Stopping the ByteBlower CLT used to be a tricky process. The only way to do it was through control-c, but this leaves you without a report. It is also annoying, especially when working with headless systems.
As of this release, you can now restart the ByteBlower-CLT with the regenerate option. The CLT will then regenerate the last report. It generates all available report types by default, but it also accepts a list of format types.

What's coming next?

The next version is already in the works and will be released in the next few months. Some of the new features you can expect:

  • 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.11.8

New Features

  • [Reporting] JSON reports.

Bug fixes

  • Initializing test-runs with many frames goes faster. The 'improving filter' requests less info from the ByteBlower server

Changelog 2.11.6

Bug fixes

  • The TCP goodput (or Layer 5) rate was handled differently than all other results over tine. This caused artifacts in the Report. Everything is the same now, thus fixing the artifacts.
  • Frames below the minimum 60 bytes are padded before transmitting.

New Features

  • [Reporting] JSON reports. (beta feature)

Changelog 2.11.4

Bug fixes

  • [Meeting Point]: When a single Wireless Endpoint returns corrupt information, the MeetingPoint keeps refreshing now.
  • [UI]: The GUI is more lenient now regarding allowed IPv6 address format.
  • [Reporting]: The CSV report didn't always include the OOS results over time. They do now.
  • [Reporting]: Cleanup of the CSV format. Not all sections used the same title format (TCP Info, TCP results over time, HTTP Results overtime), added a newline as a separator between HTTP and TCP results over time.
  • [UI] Due to miscalculation, the IPv6 traffic class was limited to 0x80
  • [CLT] The CLT now uses up to 1Gbyte of heap-space, just the same the ByteBlower GUI. This avoids the CLT going out of memory where the GUI succeeds.
  • [UI] Only show valid battery levels.
  • [UI] You can now also use the support tool or update a ByteBlower server that isn't running.
  • [Reporting] The time-axis correctly counts the days in multiday tests
  • Fixed nullpointer exception that happened when a test was cancelled promptly after being started.
  • [Reporting] Fixed the Aggregate Tcp charts on MacOs. The embedded browser had difficulties with the minified script.
  • [Reporting] The first sample of the Latency distribution wasn't shown.
  • [Reporting] In the CSV output we've restored the headers and documentation of the "Out Of Sequence overview results table" and "Latency overview results table".

New Features

  • [UI] The GUI report lists the configured duration of a FrameBlasting flow.
  • [UI] The units are displayed on the time-axis in the graphical report
  • [UI] The title of the FrameBlasting charts now shows source and destination
  • [UI] The Hex text fields in the FrameView are easier to use. You don't need to fill in the leading zeros anymore.
  • [UI] The edit button in the FrameBlasting View is disabled when the template has no frames.
  • [Reporting] Reduced memory consumption when generating the HTML report.
  • [Reporting] The FrameBlasting tables show all frame sizes even when multiple sizes are configured.

Changelog 2.11.2

Bug fixes

  • [Reporting]: Fixed NullPointer exception while generating report of an RFC2544 test.
  • [Reporting]: Fixed Frame Blasting Throughput results over time in CSV reports.

Changelog 2.11.0

New Features

  • [Reporting]: Interactive graphs.
  • [Server View]: You can now capture network traffic from the popup menu in the Server View.
  • [Server View]: Updating a server is now easier than ever. We added a new wizard explaining what will be done. We made it more robust and usable in various lab networks.
  • [General]: The currently open project is saved regularly now. You can open the most recent project from the file menu.
  • [CLT]: Added an option to regenerate the report on the latest CLT run.


  • [Archive View]: When new reports are generated, they will now immediately become visible in the table.
  • [About box]: Third-party libraries used have been documented. You can find them in our legal info for ByteBlower plug-ins.
  • [General]: Reduced number of API calls to the ByteBlower Server for TCP tests. This will particularly benefit larger tests.
  • [General]: NAT entries are kept live until right before the start of the test.

Bug fixes

  • [General]: The scenario isn’t stopped when the same server or meeting point is accessed from multiple FQDNs.
  • [Archive View]: You can now regenerate multiple reports by selecting multiple tests.

Known issues

  • [Reporting]: For Linux users, interactive charts are only visible using an external browser.

ByteBlower API 2.11.6 (2020-04-15)


You can download the latest version at


  • Added support for python 3.7 and Windows 64 bits.


  • The red 'evaluation license' message has been fixed. Due to a build error the (TCL) installers were created with an evaluation version of BitRock.

ByteBlower API 2.11.4

This API version was not released, this is a ByteBlower Server release only.

ByteBlower API 2.11.2 (2020-02-11)


You can download the latest version at


  • Added the possibility to configure the BROADCAST/UNICAST DHCP flag.  The ByteBlower Port will use this in the DHCP Process
  • Added extra DHCP timing statistics (timestamps when the DHCP discover/offer/request/ack, DHCPv6 solicit, advertise, request, reply are sent or received)


  • When Refresh was called on an OutOfSequence trigger, the result information was invalidated.  Accessing this information caused a crash of the API.
  • When the DHCPv6 Session Information was requested, the actual information was not requested on the server, thus needing an extra Refresh call.  This inconsistency with the other parts of the API is fixed.

ByteBlower API 2.11.0 (2019-12-04)


You can download the latest version at


  • Added support for the Wireless Endpoint to collect network information over time.


  • TCL: The signature for the deprecated method Pcap.Save on our Rx.Capture.Basic was wrong and resulted in an error.
  • TCL: The NetworkInfo object on a Wireless Endpoint can now be Refreshed.
  • Fixed an issue where it was impossible to fetch the Result History for a Frame configured on a Wireless Endpoint.


  • Our Python API (beta) is now available as a Python wheel instead of using a custom installer.  This gives us the possibility to release them later using PyPi

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 video


You can find the downloads for windows/macOS/Linux at following location: .The apps for Android and iOS are available in the app stores.

Changelog 2.10.4 (2019-10-08)

  • The Wireless Endpoint logged a lot of QML warnings in the console. Those are fixed now.
  • The Wireless Endpoint could report more frames to be transmitted than the actual number of frames transmitted in frameblasting flows. This can be detected by having loss in upstream UDP flows.  This issue is fixed now.
  • The Wireless Endpoint could report more frames being received than the actual number of frames received in frameblasting flows. This could be detected by having negative loss in downstream UDP flows.  This issue is now fixed.

Changelog 2.10.2 (2019-07-09)

  • Fixing performance issue where TCP did not perform well on some devices
  • Fixing issue where TCP Upstream did not restart well

Changelog 2.10.0 (2019-04-24)

  • Support for TCP-Restart
  • Reviewed the traffic generation program code. This led to faster code that is easier to maintain.

You can find the detailed installation instructions in our How to: Install the Wireless Endpoint on your device.

2.10.8 (2019-08-29)


  • Add support for ByteBlower 3200 Gen2

2.10.6 (2019-08-14)


  • Unintended traffic on the management interface TCP port 9002 could cause the ByteBlower daemon to stop. We've made it robust against these packets
  • MLD Listening Reports could in some rare cases cause the ByteBlower to stop. This is resolved.
  • Some tools couldn't handle the lacking of a dongle. Now those tools report a correct error when the dongle is missing.

2.10.4 (2019-08-08)

Fixes - Configurator

  • The IPv4 gateway was already optional in the management interface configuration, due to an input validation bug, it seemed required
  • When adding a route, an error was thrown when looking for the correct interface to add the route on.

Fixes - ByteBlower

  • ByteBlower is now able to correctly handle fragmented IPv4 packets
  • Improved TCP performance when sending from 10G to 1G and the switch has small buffer sizes and latency is high

Fixes - Meetingpoint

  • New networkinterface on wireless devices was created over time. Info is now updated instead of creating a new interface

2.10.2 (2019-07-04)


  • Server: TCP: Fix long performance drops that sometimes occurred in situations with high packet loss.
  • MeetingPoint: Add iOS 13 as supported device
  • Configurator: When the network configuration is corrupt, throw a more adequate error with more information instead of an obscure out_of_range.
  • Configurator: When a custom port configuration is used, the interface was not marked as trunking
  • Configurator: Fixed an issue when the ByteBlower interfaces could not be configured after a fresh install.

2.10.0 (2019-04-24)



  • Adding support for NBase-T (2.5Gbit and 5GBit) interfaces.
  • Added an option to restart the TCP on a wireless endpoint. A TCP session will automatically restart if its been dropped by a bad Wi-Fi connection.
  • Multiclient TCP API [Beta]


  • The server could crash when the FrameTag (Time/Sequence) was requested before the frame bytes were set.
  • Creating a frameblasting flow with ARP packets could cause the server to stop. This is fixed.
  • Restored our /legal directory which was lost in a previous release.

Changelog 2.10.0 (2019-04-24)


You can download the latest version at


  • Added TCP-restart function for HTTP.Client.Mobile


  • Updated documentation (
  • Communication interruption between meetingpoint and API could cause the API to crash. This crash happens when you try to clean-up meetingpoint and releated objects. This has been fixed


  • ByteBlowerServerServiceInfo License.Get is now deprecated
  • MeetingpointServiceInfo License.Get is now deprecate

You can find the detailed installation instructions in our How to: Install the Wireless Endpoint on your device.


You can find the downloads at following location:

Changelog 1.1.28 (2019-04-03)

  • Fix issue with huge result-sets being communicated to the meetingpoint
  • Threads where created on the windows version and never destructed. This has been resolved
  • Abort button didn't work anymore under certain conditions. This is resolved and you now can abort again the app

Changelog 1.1.26 (2019-03-05)

  • Improvement on the core implementation. Prepared the code for TCP restart.
  • Improved heartbeat protocol. Where in previous versions, it could be so that your app stayed in contacting while there was WiFi or visa versa. This is now fixed and the app will handle much better the change between connected and disconnected.

Changelog 1.1.22 (2018-10-09)

Changelog 1.1.20 (2018-07-11)

  • Fix communication of all known networkinterfaces of Windows Wireless Endpoint to ByteBlower ( Invalid JSON format )

Changelog 1.1.18 (2018-06-01)

  • Some devices hanged when wifi-connection is lost. This has been resolved
  • Symantec blocked the TCP testing-traffic. TCP payload now is more realistic and symantic doesn't block the traffic anymore

Changelog 1.1.12 (2018-02-20)

  • Improve stability when channelhopping. Traffic was previously dropped
  • IPv6 UDP flows: Total transmitted/recieved bytes was incorrect. The calculation of the IP-header was wrong
  • Improving the re-connection. Sometimes The Wireless endpoint didn't reconnect when WiFi signal was lost.

Changelog 1.1.6 (2017-09-22)

  • Improve timings
  • Bugfixing

Changelog 1.1.4 (2017-05-30)

  • Improve stability of long tests

Changelog 1.1.2 (2017-04-12)

  • UDP upstream bugfix
  • Fix link to this Changelog

Changelog 1.1.0 (2017-04-06)

  • Improvements in UX and UI
    • Gauge for Tx
    • Gauge for Rx
    • Added device info
    • Added Network info containing the device interfaces and there IP's
    • Improved design for tablets
    • Added landscape mode
  • Added support for IPv6 traffic
  • Added support for latency measurements
  • Added support for bi-directional traffic

This installer will install the basic ByteBlower system.

For more information on how to install ByteBlower on your server, see this article.

We encourage everybody to update to the latest version!


  • This installer is generic for all ByteBlower versions.
  • Complete new ByteBlower update and restore implementation.
  • Version indepedent: after the install, the server will sync with our download server to retrieve the latest possible version.

Version 2.8.2

  • Update to updater version 3.6.11
  • Fix series detector for 1200 and 1300 systems

Version 2.3.2

  • Update to updater version 3.5.2

Version 2.3.0

  • Added IPv6 support
  • Update to updater version 3.5.0

Version 2.2.0

  • Update to kernel version 4.4.12-rt19
  • Update to updater version 3.3.0

Version 2.1.10

  • Boot time has been speed up.
  • Fixed some system boot order
  • Improved boot output
  • Fixed some error handling
  • Update to updater version 3.2.6

Version 2.1.6

  • Updated kernel: Add support for TPM modules

Version 2.1.4

  • Creating rock-ridge enabled ISO files.
  • Decreased disk size (use symbolic links instead of copies for series images)
  • Added support for 3100 series

Version 2.1.2

  • ByteBlower interfaces where not activated at boot

Version 2.1.0

  • Upgrade to latest ByteBlower updater
  • Better network card detection.


You can download this version of the Server Installer from this location:

[[SecureDownload:ByteBlower/Server/installer/byteblower-installer-disk-2.8.2-r201.iso:ByteBlower Server Generic Installer]]

If you are unsure whether you need complete re-installation of your system, please contact support!

More information on how to create your CD-rom or USB install disk, can be found in this article.

Get your CD-rom or stick

If you are unable to create the CD-rom or USB install disk, please request your copy by sending you message to:

You can find the detailed installation instructions in our How to: Install the Wireless Endpoint on your device.



You can download the Excentis Repository installation packages from these locations:

Debian 8

  • [[SecureDownload:ByteBlower/Repositories/1.0/Debian/8/excentis-repo_1.0-jessie46_amd64.deb:ByteBlower Repository]]

Ubuntu 14.04

  • [[SecureDownload:ByteBlower/Repositories/1.0/Ubuntu/14.04/excentis-repo_1.0-trusty46_amd64.deb:ByteBlower Repository]]

Ubuntu 16.04

  • [[SecureDownload:ByteBlower/Repositories/1.0/Ubuntu/16.04/excentis-repo_1.0-xenial46_amd64.deb:ByteBlower Repository]]

CentOS 7

Please note that both packages are required for installation and activation of the Excentis repositories.

  • [[SecureDownload:ByteBlower/Repositories/1.0/EL/7/excentis-repo-user-1.0-1.el7.centos.noarch.rpm:Base package for Excentis Repository]]
  • [[SecureDownload:ByteBlower/Repositories/1.0/EL/7/excentis-repo-1.0-1.el7.centos.noarch.rpm:Excentis Repository Configuration]]

Fedora 22

Please note that both packages are required for installation and activation of the Excentis repositories.

  • [[SecureDownload:ByteBlower/Repositories/1.0/Fedora/22/excentis-repo-user-1.0-1.fc22.noarch.rpm:Base package for Excentis Repository]]
  • [[SecureDownload:ByteBlower/Repositories/1.0/Fedora/22/excentis-repo-1.0-1.fc22.noarch.rpm:Excentis Repository Configuration]]

Fedora 23

Please note that both packages are required for installation and activation of the Excentis repositories.

  • [[SecureDownload:ByteBlower/Repositories/1.0/Fedora/23/excentis-repo-user-1.0-1.fc23.noarch.rpm:Base package for Excentis Repository]]
  • [[SecureDownload:ByteBlower/Repositories/1.0/Fedora/23/excentis-repo-1.0-1.fc23.noarch.rpm:Excentis Repository Configuration]]

Fedora 24

Please note that both packages are required for installation and activation of the Excentis repositories.

  • [[SecureDownload:ByteBlower/Repositories/1.0/Fedora/24/excentis-repo-user-1.0-1.fc24.noarch.rpm:Base package for Excentis Repository]]
  • [[SecureDownload:ByteBlower/Repositories/1.0/Fedora/24/excentis-repo-1.0-1.fc24.noarch.rpm:Excentis Repository Configuration]]

Fedora 25

Please note that both packages are required for installation and activation of the Excentis repositories.

  • [[SecureDownload:ByteBlower/Repositories/1.0/Fedora/25/excentis-repo-user-1.0-1.fc25.noarch.rpm:Base package for Excentis Repository]]
  • [[SecureDownload:ByteBlower/Repositories/1.0/Fedora/25/excentis-repo-1.0-1.fc25.noarch.rpm:Excentis Repository Configuration]]

Changelog 1.0-1

  • Initial release


We are pleased to announce the immediate release of a new version of the ByteBlower LabVIEW API.

Please note that the directory structure of the API has changed because (1) Tcl 8.5 is now included and (2) the directory structure has been reviewed and cleaned. Please contact ByteBlower support for more information on how to integrate the new API.



  • Update ByteBlower Tcl API to version 2.6.2
  • Update to Tcl version 8.5: Fixes hang of LabVIEW at exit.
  • Fixed performing DHCP
  • Streamlined directory structure
  • Added VIs for debugging purposes
    • Obtain textual description of given ByteBlower object (Tcl OID)


You can download this version of the LabVIEW API from these locations:

  • [[SecureDownload:ByteBlower/API/LabView/2.6.2/ for LabVIEW 8.5 on Windows]]

We to help you!