TCP Restart
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 short demonstration video
Need a flexible NBASE-T test solution?
2019 will be the year of WiFi 6! With throughput rates rising beyond the magical 1 Gbit/s barrier, NBASE-T network connectivity will become much more common.
The NBASE-T add-on to ByteBlower gives you 2.5 and 5G test-capabilities in addition to your current system. This upgrade keeps you up to date with future developments to Ethernet connectivity without the expense of a whole new system.
Four different network technologies from just a single system!
What's coming next?
Meanwhile the next version is already being worked on, which is expected in the summer months. Some of the new features you can expect:
- Interactive charts
- Wi-Fi details ( RSSI/BSSID/...) in API where available
- JSON reports preview
Download
You can download this version of the GUI here: https://setup.byteblower.com/software.html#GUI
Information on how to use the CLT version of the GUI: Introduction to ByteBlower CLT
Changelog 2.10.2 (27th of June 2019)
- The ByteBLower-CLT prints out its version number on startup. This makes it easier to know which version you're using.
- A cleaner handling of the command line arguments. Removed the stack-trace when the arguments are incomplete.
- Fixed including the images in this changelog.
Changelog 2.10.0 (24th of April 2019)
Improvements
- Default TCP window scale is now 7. This is closer the most common value on the internet today. New TCP templates will use this value.
- Easier solution text for Wireless Endpoints without IPv6 configuration.
- We're now also generating a latency distribution chart is for broadcast flows.
- The support-portal and tutorial site are now accessible through the help-menu ( Help->Support Portal | Help->Tutorials ) .
- You can now create scenario's immediately from the Flow view. Select a couple flows and pick the last option in the right click menu.
- Show the total burst duration in the middle info panel of the FrameBlasting View. This makes it easier to configure burst.
- To make it easier working with many frames, the Frame view now shows you size and type of the frames.
- The archive view additionally shows the size of the testresult database. This makes it easier to clean up the largest items.
- The CLT creates the output and store directories if they woulnd't exist yet. That makes the CLT easier to use in scripts.
- The Windows CLT now uses the console where it is started from, rather than opening a new window. This makes working with the Byteblower CLT much more easy. It has thus now the same behaviour as the eclispec.exe.
- The GUI backups the project also when started with a batch.
- Instead of 5 packets, discovery traffic is sent for the whole NATDiscovery period. The rate remains 10 pck/s. In total at most 200 packets will thus be sent out.
- A Wireless Endpoint test will stop when the WE returns to reserved, even when the TCP flow fails to connect completely.
- The duration column of a TCP flow will be colored red in the ByteBlower report when a TCP flow doesn't reach its configured duration.
Bug fixes
- Filenames of the reports are now unique filenames. This fixes an edgecase where multiple tests finish within the same second.
- More robust Archive view. Fixed nullpointer exception when no format was found.
- The edit button in the Frame Blasting view is disabled when no project is open.
- The 'open HTML' button will always open the HTML report and not the one currently selected.
- Made the UI more robust. Fixed null-pointer exceptions found in the GUI logs.
- The save-as view tried to update itself after canceling. This generated hidden exceptions in the log.
- Fixed a couple exceptions that occur when closing of the ByteBlower GUI. These were found in the Eclipse log.
- Fixed hidden Exception when clearing the initial receive window size value in the TCP view.
- Restarted TCP sessions using the same TOS values, slow start threshold, maximum receive window as the original session"
- Result gathering works subtly different between MeetingPoint and ByteBlower server. As a result the same values were stored multiple times in the result-database. This was corrected in the backend. This tends to happend when stopping the test early.
- The First HTTP and TCP snapshots are now always retrieved. In the past they were occasionally lost.
- Changes in how the results are stored has solved the duplicated results in the CSV report.
- A run-title (top, action bar) with ending spaces caused issues during report generation. These spaces are now trimmed away.
- The table at the right-bottom corner of the Multicast view is now cleared on startup. It was initialized with the wrong data.
- Changing the ethertype of a frame in the Frame View didn't also clear all state. Checksums for instance were still calculated.
- Fixed null-pointer exception that happened when selecting multiple reports in the archive view and pressing enter"
- Cleanup statusbar-text of the hexeditor in the frame view.
- Our test-database was the cause of a number of bugs. We've updated the library to the latest stable version. This new release is unaffected.
- Deleting many scenarios in a single batch triggered concurrency issue. This bug has been solved.
