ByteBlower GUI 2.9
Posted by Wouter Debie, Last modified by Wouter Debie on 26 April 2019 01:36 PM
Version 2.9 of our popular ByteBlower® tool is ready to make IP testing faster and simpler than it already was! We’re on a constant quest to make ByteBlower more intuitive to deploy. So, we’ve added a range of new, practical features to the latest ByteBlower version. Your benefits? Faster, simpler and more efficient testing.

Download

You can download this version of the GUI from these locations:

With the ByteBlower CLT, you can start test scenarios created with the GUI, by executing one single command.
You can download the CLT Command Line Tool here :

Information on how to use it: Introduction to ByteBlower CLT

Changelog 2.9.8 (14th of Februari 2018)

  • RFC-2544 flows need to run for a minimum amount of time for decent results. Scenarios with less than the minimum will be marked faulty. In the solution view you'll find the suggested minimum time.

  • RFC-2544 flows in the report are now either black (good) or red (no results). The colour purple (result resolution) has been dropped, this warning wasn't very useful and couldn't be configured either way.

  • The total duration of RFC-2544 flows can be changed in the scenario view.

  • The FrameBlasting settings dialog has been made a bit smarter. It warns you of wrong burst configurations. Such an invalid config would make it impossible to edit the FrameBlasting template further.

  • ByteBlower ports can be docked again in the wizards. Whole tests can be created the wizards.

  • Fixed various edge cases while processing TCP flows. Especially the first and last results weren't always retrieved from the ByteBlower Server.

  • Corrected comments and headers in the CSV. The largest changes were in the TCP table and IPV4 ports sections.

  • Speed up generating reports with FrameBlasting flows on Wireless Endpoints. The MeetingPoint doesn't clear results, this caused for a lot of duplicate results requiring processing.

  • Configuring multiple TCP Flow templates with the same server port can trigger the PortAlreadyUsed exception. Due to an API change, this exception wasn't handled at the correct call.

  • To make it easier to debug test-runs, the message for a failed DHCP attempt now includes the ByteBlower interface where it goes wrong.

  • The decision whether a Wireless Endpoint has finished with its test is now delegated to the MeetingPoint. This helps especially when the test had no traffic or when it was aborted.

  • Added a fix for the case when only invalid latency packets are received.

Changelog 2.9.6 (14th of November 2018)

  • Fixed a nullpointer exception in the exception handling code. This error was triggered when sending multiple flows with undersized IPV6 frames.
  • Framesize modifiers now also work on ByteBlower Ports with an MTU smaller than 1500.

Changelog 2.9.4 (16th of October 2018)

  • In the CSV, jitter and invalid packetcount were added to the latency results over time. The documentation embedded in the CSV was spell-checked.

  • When the internal Eclipse browser isn't available, an external one is used. This helps Linux users who haven't yet installed webkitgtk-1.0-0.
     
  • The PCAP frame import wizard loads again. The code for this class wasn't loaded during startup.

  • Restarted TCP flows didn't stop after the right time. The TCP start/stop/reload code was simplified and debugged.

  • Corrected backwards compatibility for RFC-2544 flows. Projects created before 2.9.0 with now load with the corrected duration for this type of flows.

  • The CLT runs the complete batch again. A concurrency issue aborted the second scenario in the test.

Changelog 2.9.2 (19th of July 2018)

  • A fix for TCP flows with delayed start. The initial time to wait was not taken into account when aborting the flow.

Changelog 2.9.0 (3th of July 2018)

  • TCP test traffic is now restarted if it stops before its configured end. Reasons for such a restart are aborted TCP connections or no new received data. The reason is included in the warning section of the report. This behaviour is now enabled by default in new projects. But you can change this in the preferences.

  • You can control the way tables are sorted in the GUI. This is extremely useful in the Scenario view. By clicking on the column header, you can enable, disable or change the sorting order. The column used is shown in grey.

  • The scenario and batch view now include a duration column.

  • The status-line at the bottom of the GUI counts the selected items. This makes it easier to manage large ByteBlower projects.

  • Processing FrameBlasting results has been reworked. This new approach is faster resulting in a lower load on the client PC.

  • Starting the ByteBlower server from the right-click menu in the Server View includes its status now.

  • Wireless Endpoints on slow smart phones have a limited transmit timing accuracy. The report will show no warning anymore when less than one percent of all packets weren't transmitted.

  • The results over time require regular updates from the ByteBlower server. The report will notify you when not all intermediate results were processed in a large or long test. If the test is aborted early due to network connectivity issues, the report includes essential troubleshooting info.

  • The report includes a warning when a ByteBlower interface is asked to transmit more than physically feasible. In this statement you'll find which interface was overloaded.

  • The menu bar had an empty tab for custom wizards. This one has been removed, but ideas for new wizards are of course still welcome.

  • We currently don't support flows between two Wireless Endpoints. Such flows are now marked faulty and shown in the Solution View.

  • In the RFC-2544 wizard, a duration hint and additional info make the configuration much easier.

  • The RFC 2544 flow is editable now. Right-click and pick the jump to edit option.

  • Speedup of RFC-2544 benchmarks. They are now up to 2x faster than before. The main improvement was through better estimating of the final throughput.

  • For consistency, Auto HTTP method is renamed to Automatic HTTP method.

  • In the right click menu, Jump is renamed toJump to edit. The functionality remains the same, but we hope this name is more intuitive to new users.

  • We've updated the reporting engine (Jasper). This solves a number of rendering bugs in the library.

  • Fixed a couple rare null-pointer exceptions. One was due to a concurrency issue, the other was found in the UI logs.

  • Easier access to the system logs. You can open them with Window -> System info.

  • Projects created with 'Save As..' are now also found in the recent projects list in the File menu.

  • Some UI lag was noticeable when starting a test run. The root-cause was the Archive View. It is now faster and only updates the visible items.

  • Saved preferences weren't used in new projects. This bug has been fixed.

(0 vote(s))
Helpful
Not helpful

Comments (0)

We to help you!