ByteBlower GUI version 1.8.32
Posted by Admin Kayako, Last modified by Wouter Debie on 29 June 2017 09:52 AM

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


Bugfix release history:

  • ByteBlower GUI version 1.8.22 (release May 14th) introduces the features and enhancements listed below. It has been superseded by several bugfix releases.
  • The changelog below contains the original 1.8.22 changes, with the bugfix release changes listed at the bottom.
  • We encourage everybody to update to the latest version!



  • Latency reporting
    • The ByteBlower GUI can now report latency measurements with nanoseconds precision. This comes with the 1.10.18 release of the ByteBlower 2100 server.
    • The latency unit and the amount of decimal numbers is configurable in the project preferences.
    • The range of the latency distribution graph is now configurable in the Preferences.
    • The default latency measurement range is now 0s->100ms instead of 0s->10s.
    • When hovering above the latency distribution graph, the amount of frames with that latency is now displayed.
    • The CSV report now also shows a latency unit column.
    • Microseconds in the latency range can now be entered as "us".
  • The columns of the CSV report are now the same ones as those in the HTML report.
  • The "Pause after DHCP" dialog now contains a checkbox to hide it.
  • The GUI now packages with and uses a bundled Java 7 JRE on Mac OS X, as was already the case on other platforms.
  • Unicast flows are now reported without displaying 100% loss.
  • Unicast destination IP addresses are now reported too.
  • The default DHCP retransmission policy is now "Fixed Timing". This makes DHCP fail quicker when there is no DHCP server.
  • Latency Distribution graphs are now bigger: 600x200px
  • After selecting a destination for a flow, the dialog now closes immediately, to reduce the number of required mouse clicks.


  • Fixed critical bug where TCP Aggregate throughput values in the report were not calculated correctly.
  • Fixed bug where TCP Aggregate duration values in the report included flows that could not be established, which may have led to negative durations in some situations.
  • Fixed bug where TCP flows that could not be established had 'finished' status (and 0 bytes sent/received) instead of timed out status.
  • Fixed a bug in the ByteBlower server where setting a growing frame size modifier could cause the server to crash in rare situations.
  • Fixed bug where deleting a Frame and selecting a Flow Template which contained that frame caused an error.
  • Fixed bug in the internal refresh algorithm of the project model, which caused some objects to display a wrong status. For example, after using the B2B Wizard, and then docking the ports, the first flow destination (incorrectly) showed an error state.
  • Fixed bug in the Throughput Wizard, when using the Increment Throughput option.
  • When an IPv6 port cannot be configured while a scenario is being initialized, it will now show up red in the report, as was the case for IPv4 ports.
  • Fixed bug where ByteBlower ports on which DHCP/SLAAC failed (and thus lacked an IP configuration), showed their old IP addresses (as previously configured in the Port View) in the report.
  • Unicast Flows are displayed again in the report.

Bugfixes 1.8.24

  • Fixed bug in the report generation that caused an error when a scenario was run with only TCP flows.
  • Resolved an issue on Ubuntu 14.04 where HTML reports could not be opened. Opening these HTML reports caused the GUI to crash sometimes.

Bugfixes 1.8.26

  • Resolved an issue on Windows where HTML reports were not opened automatically after running a scenario.

Bugfixes 1.8.28

  • Optimized scenario execution
    • If a port fails to initialize and ignore initialization errors is active, this initialization will no longer be repeated for subsequent flows in which the port participates. This ensures consistency within the scenario being executed and reduces configuration time.
    • Frame blasting receivers are now only created for unique frames within a Flow. This decreases the load on the server.
    • GUI uses a new API version (1.8.22) that improves server memory management.
  • Improved error handling for failing multi-destination flows (ignore initialization errors active).
    • Flows with a multicast or broadcast destination will now be run as soon as a single destination port can be initialized.
    • Eavesdropper ports of a flow that fail to initialize will no longer stop the flow from running.
  • Fixed issue where a latency distribution graph did not show up in some situations.

Bugfixes 1.8.30

  • Fixed bug that caused the GUI to crash on Mac OS X when executing scenarios with TCP flows.
  • The latency precision warning in the report is no longer shown when the measured values are zero, because increasing the report precision has no effect in that case.
  • Improved server memory management.

Bugfixes 1.8.32

  • Improved duplicate frame detection during scenario initialization.
  • The throughput wizard now generates frames which differ at the start of the payload instead of at the end of the payload. This allows latency and/or out-of-sequence, which overwrite the last bytes of frames, to be enabled on the throughput flows.
  • Fixed issue where error message did not show up when opening a project created with a newer version of the GUI than the one in use.
  • Fixed issue where GUI running on Mac OS X did not detect radio-button changes (in the Frame view).
  • The command-line tool (CLT) now correctly opens projects again.


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

(0 vote(s))
Not helpful

Comments (0)

We to help you!