ByteBlower GUI version 2.0
Posted by Admin Kayako, Last modified by Tom Ghyselinck on 21 October 2015 01:06 PM

We are pleased to announce the immediate release of the ByteBlower GUI 2.0.

This first installment of our 2.x GUI series brings highly anticipated features to ByteBlower and prepares our platform for the future. The most important features and functional changes from the 1.x series are listed below.

Please note that a 2.x GUI can only work with 2.x servers! Upgrading a server from 1.x to 2.x requires a reinstallation. This process is described on the 2.x server download page.

While the 2.0 GUI is not compatible with older 1.x servers, it is able to detect them. Furthermore, a 1.x and 2.x GUI can be installed side by side, so it is possible to work with all servers (old and new) from a single client device!


ByteBlower 2.0 brings a ton of changes to ByteBlower. The list below only contains the most important new features and the functional changes between the 1.x and 2.x GUI. Changelogs of the 2.0.x patch releases are listed at the bottom.


  • Test data gathering engine
    • Test results (such as periodic flow results) are now constantly gathered while a test is running.
    • Test data is stored in file-based databases (one per test). These databases are located in <home-directory>/byteblower/workspace_v2/TestData.
    • Test execution is thus decoupled from reporting, since the test data is persisted.
  • Project can be configured while test is executing
    • Before a test a deep copy of the complete project is taken.
    • User can work on opened project or open another project. The runtime component uses its own version.
  • Broadcast flow destination behaviour is changed
    • Broadcast destination now functions as a 'fixed' address, just like the unicast destination.
    • In addition, all ports (except the source port) in the project are implicitly added as flow eavesdroppers during scenario initialization.
  • Batches and batch items are now easier to use
    • Absolute start times are no longer supported. When opening an 1.x project file, all items with absolute timing are automatically converted to a relative time (i.e. after the previous scenario) of zero.
    • The initialization time property (which acted as a minimum initialization duration) of a batch item is removed.
  • Optimization of project model's internal refresh algorithm. GUI is more responsive and large-scale projects can be created more easily.
  • TCP default settings have changed
    • ServerDefault is removed as a TCP congestion avoidance algorithm. The new default value is SACK.
    • Window scaling is enabled by default with a default scaling value of 2.
  • Interoperability with 1.x servers: refreshed 1.x servers are shown as incompatible servers in the configuration view. They also show their (incompatible) 1.x version.
  • Server auto-detection service has been removed.

User interface

  • New Realtime view
    • Shows dynamic information about ports and flows, such as IP addresses obtained by DHCP.
    • Shows real-time flow results (throughput, frame rate, latency, ...)
  • Revamped archive view
    • Based on the test data gathering engine.
    • Allows new reports to be generated from old test data (e.g. after a GUI update with report bugfixes or enhancements).
  • Real-time port information is removed from the Port view; it is shown in the Realtime view instead.
  • The subpanels TCP and Frame Blasting of the Flow Template view have been separated into two views of their own.


  • New reporting engine
    • Reports are restyled but have a familiar structure.
    • Flexible reporting engine and test data stored in the database allows for future customization and enhancements.
  • Result over time charts
    • Show flow properties over its duration.
    • Charts available for throughput, latency and out of sequence.
  • Error and warning messages include a timestamp and are more verbose. For example, if some frames are indistinguishable or identical, these are listed in the warning message.

Known issues

  • General
    • Command-line tool is not yet available.
    • Latency on the 2100 still requires the user to set the UDP checksum to zero (see ‚ÄčKB article).
    • Pause after DHCP feature is disabled. Scenario will always be started immediately after initialization.
    • Runtime port properties (such as IP addresses) are retrieved immediately after a port is configured. In the case of DHCPv6, DCHPv6 may be ready before a Router Advertisement was received. This currently results in a :: (i.e. zero) gateway address.
    • The TCP congestion avoidance algorithm is only set on the HTTP client. For flows using HTTP GET (the default case), this means that setting a congestion avoidance algorithm has no effect, since the HTTP server is the source.
  • User interface
    • File menu: No recently opened projects.
    • File menu: No importing from or exporting to ByteBlower frame (.bbf) files. Importing from PCAP (.pcap) files is still possible.
    • Wizards: Not all Wizard content may be visible on some (Gnome-based) Linux operating systems, such as Fedora.
    • Log view is removed from the GUI. It may return in another form.
  • Reporting
    • Result over Time graphs are not aligned.
    • Aggregate results are missing.

2.0.8 changelog

  • User interface bugfixes
    • A compatibility error is shown when connecting from 2.0.x GUI to a 2.1.x (or higher) ByteBlower server, since minor compatibility breaks were needed between the two. This is backported into the 2.0.x software to remind te user to update the GUI application.

2.0.6 changelog

  • Execution bugfixes
    • Fixed important TCP window scaling issue, which caused TCP flows with different window scaling settings to all take the same settings. [requires server 2.0.6]
    • TCP window settings are now configured on both HTTP client and server. This makes sure HTTP servers (re)used in multiple flows as both sender (GET) and receiver (PUT) always contain the correct settings.
    • Identical and indistinguishable frame detection is now restricted to a single physical interface, so warnings only show up when appropriate.
    • Fixed minor DHCP issue that could cause failed DHCP attempts to be interpreted as timeout issues instead of initialization errors. [requires server 2.0.6]
  • User interface bugfixes
    • New-Delete-Cut-Copy-Paste actions are now correctly enabled and disabled in the expected situations throughout the GUI.
    • Fixed issue where the global undo/redo operations were not available in the Realtime view.
    • Server view is now updated whenever a port is renamed or its status (i.e. ok or error) changes.
    • Central part of the Server view can no longer be resized.
    • Zero MAC address are no longer supported and are marked as invalid.
  • Reporting bugfixes
    • Reports now correctly show 'Error' (instead of 'Executing') as test status when something went wrong unexpectedly during execution.

2.0.4 changelog

  • Execution bugfixes
    • Creating ByteBlower ports on 2100 or 4100 servers with more than one trunking interface should no longer gives an opaque error with message 'Technical error: map::at'. [requires server 2.0.4]
    • Fixed unexpected Identical Frames notification when multiple source ports are behind a NAT device.
  • User interface bugfixes
    • Fixed NullPointer issue that sometimes occured after a UI component is disposed.
    • Wizards: New servers can now be created from within the Wizards again.
    • Scenario view: Time Last Frame Sent value now shows '-' instead of an invalid value when a flow's duration is less than the interframe gap (and 0 packets are sent).

2.0.2 changelog

  • Execution bugfixes
    • Fixed issue where ByteBlower ports were sometimes created on a wrong server, when multiple servers were used in a single scenario.
    • DHCP client now always asks for default gateway and netmask values explicitly, through DHCP option 55 (Parameter Request List). Because of this, it now works with DHCP servers that don't provide these values by default. [requires server 2.0.2]
    • Fixed issue where server could crash when a scenario is canceled. [requires server 2.0.2]
  • User interface bugfixes
    • Run scenario and Run batch buttons now become enabled (resp. disabled) when the selected scenario or batch becomes valid (resp. invalid).
    • Starting a batch opens the Realtime and Progress views, just like when starting a scenario.
    • When changing the frame repeat value in the Frame Blasting view, the frame and byte weights are now updated immediately.
    • Realtime view correctly shows pending instead of connection as status when a scheduled TCP flow has not yet started.
    • Progress view takes start times of size-based TCP flows into account as well, when calculating the scenario duration.
    • Various fixes to copy down and copy down incrementing behavior (IPv4 vs. IPv6, multicast addresses vs. multicast source addresses, ...).
    • Improved the UI refresh algorithm. Fixes issue where views were not updated instantly on Windows and generally improves the GUI performance.
  • Reporting bugfixes
    • Generating a report for a flow with a fixed destiation no longer fails.
    • Multiple latency distribution charts in a single report will no longer overlap.
    • Reports now show the project version instead of the client software version. This version is no longer (incorrectly) 1.99.0.
    • Fixed styling of some fields in the report.
    • Configuring an MTU above the physical maximum now results in a friendlier error.


ByteBlower GUI 2.0 is no longer available for download. Please contact our support desk of you think you need this specific version.


(1 vote(s))
Not helpful

Comments (0)

We to help you!