ByteBlower GUI version 2.6
Posted by Tom Ghyselinck, Last modified by Pieter Vandercammen on 03 October 2017 09:52 AM

This release includes new features to the Wireless Endpoints. These support now Latency measurements (both directions) and IPv6 traffic. Next to this, finding past test runs has been made easier. We've added a search function to the Archive View and allow you to add tags to any test run.

Other improvements include a more detailed test report. It includes the TCP retransmissions over time. We've started adding suggestions based on measured results. In addition, the Archive and Server view have been made more user friendly.


This version isn't publicly available any-more. The latest GUI version is found in this article.

Contact If you do need this particular version.

Changelog 2.6.6 (2017-05-31)

  • Reporting

    • Reduced memory consumption. This makes multi-day tests with many Frame Blasting flows feasible.
      ByteBlower API
  • API

    • Scenarios with 100s of simultaneous flows had GUI crashes. This was caused by message corruption in the communication with the ByteBlower server. Proper synchronization fixed this issue.
    • The timeout when refreshing a MeetingPoint was longer than configured. This was caused by a conversion error. Now refreshing a ByteBlower Server or MeetingPoint takes at most 3 seconds.

Changelog 2.6.4 (2017-05-31)

  • Reporting

    • Fixed an error in drawing the Retransmission bar. This threw an exception when the Wireless Endpoint failed to prepare.
    • Report generation didn't take into account that a server might be unreachable. These servers are now listed with 'Unknown' as IPV4 address.
    • Corrected scaling of the retransmission bar in cancelled tests.

Changelog 2.6.2 (2017-04-21)

  • Wireless Endpoints

    • Increased delay for retrieving results on the Wireless Endpoint. This minimizes the chance on timeout exceptions when the device is not yet reachable.
    • Additionally clear the results over time after a test.
  • Reporting

    • Corrected the header of the TCP results over time in the CSV report.
    • The generated suggestions are added to the CSV report.
  • User Interface

    • Fixed bug in the Server View. The version info wasn't fetched correctly.
    • Tread-safe modifying the info in the Server View. This fixes a rare ConcurrentModificationException.

Changelog 2.6.0

  • Wireless Endpoints

    • With the new Wireless Endpoints (v1.1.0), it's now possible to include latency measurements. Both up- and downstream tests are supported. This can be configured in the flow view.
    • Also possible with new Wireless Endpoints is IPV6. Configuring such a test only requires docking an IPv6 port to a Wireless Endpoint.
  • Reporting

    • The info section of the report includes suggestions based on the test results. This makes it easier to debug your network.
    • The receive and congestion window have been merged into a single transmit window. This is the minimum of both, and is the value used by the TCP algorithm. This value is shown in a logarithmic scale.
    • The TCP retransmissions are shown at the bottom of the TCP results over time graph. As users note, drops of the transmit window and retransmissions often occur together.
    • The info section of the report includes the title of the test run and the used ByteBlower Servers and Meeting Points. This last detail includes their version and address.
    • The latency distribution additionally reports the relative amount of packets outside the measurement range.
  • Archive view and Run Title

    • The Run Title of each test is shown in the archive view. Right clicking a test allows one to change this title. Right clicking on a test-run allows one to change this title.
    • All reports of the same test run are stored in a folder with the name of the Run Title. This makes is easy to find all related tests. The reports are moved when changing the Run Title of a test.
    • The archive view includes a search field to quickly find previous tests results.
    • A number of tags are automatically inserted into each test run. As an example, there are tags inserted on tests with wireless endpoints, TCP and even latency measurements, or whether there was a significant amount of loss in the test. These tags give a quick overview of the test. They are displayed in the status bar at the bottom of the GUI. From the search field one can search on these tags. This makes it a piece of cake to find back your last latency test with a Wireless Endpoint.
    • Double-clicking a test opens the HTML report. This is a shortcut to immediately see its results.
    • The right-click menu in the Archive View allows one to delete tests or reports. This works both for single items and selections.
  • User interface

    • Reduced timeout when contacting a ByteBlower Server or Meeting Point. A refresh operation can also be canceled.
    • The available network interfaces are shown in the tooltip of a Wireless Endpoint.
    • A more fine-grained capability system has been added. This will block unsupported features, such as Out-Of-Sequence tests on an app.
    • Changed the interface to the result databases, It is now possible to have multiple GUIs open simultaneously.
    • The servers in the Server View are sorted on their configured address. Meeting Point and ByteBlower on the same server are now found together.
    • The TOS byte in the Frame View can be configured more easily through a number of preconfigured values. We have configurations for TOS, DiffServ(DSCP) and Wireless Media Extensions (WME)
    • The colouring of the Realtime View has been fine-tuned. This improves visibility on the throughput changes.
    • The ports section of the Realtime View includes more detail, especially for the Wireless Endpoints.
    • The right-click menu is a new, fast way to start a scenario or batch.
    • This welcome page includes a link to setting up your ByteBlower server (First steps, top)
  • Test Runtime

    • Recent apps (v1.1.0) support latency measurements. Outgoing tests support latency over time and latency distribution. A flow with an app as destination only allows latency over time.
    • Bugfixes to allow multiple ByteBlowers and MeetingPoints in a single test.



(0 vote(s))
Not helpful

Comments (0)

We to help you!