2.20.0  (2023-02-14)

Enhancements:

Increased robustness of RFC-2544 for WEP​

• ​RFC2544 is a widely known benchmark. The ByteBlower GUI implements the throughput measurement.
• In the past, tests would more likely fail due to the stress the test places on the network.
• RFC-2544 places a heavy load on the system. For fail-safe tests it’s recommended to add route the WEP mgmt. traffic over a different interface like e.g., the golden client.

UI improvements in the ByteBlower server updater. 

When errors happen resuting in failed tests, we have implemented improved logging which makes the feedback of the server more visible.

• Improved logging of error-cases from the ByteBlower Server.​
• More efficient debugging as as a result.
• Some examples of error messages​
  • Code​
  • Improper license​
  • Broken updater that was fixed in later releases.

Improved default TCP setting.

• New default value for TCP Slow Start Threshold: 2147483647 (=Integer.MAX_VALUE) (=infinite). The old default was 65535 (=0xFFFF).
• OS behaviour is closer to infinite value.

​

CCDF Graph

An empty CCDF graph is now drawn in the ByteBlower report when all packets are below the latency measurement range. This can happen due to negative latencies of a Wireless Endpoint. See also our Golden client KB article to perform such tests. 

Changelog for 2.20.0

New features 

• The server now provides latency histograms over time when using the latency distribution trigger. This allows to have latency histograms per configured measurement interval.   
  This feature is useful when measuring the QeD performance of a specific flow. 

Enhancements 

• The TPID (EtherType) of a VLAN tag can now be configured through the API. 
• Faster filtering for traffic containing multiple VLAN tags. 
• The ByteBlower 2100 and ByteBlower 4100 server series did not support 4 stacked VLAN tags as the other series did.  Now all systems have the same limit. 
• The MeetingPoint will now automatically query the ByteBlower Endpoint for the test results when the Endpoint returns after a test. 
• The MeetingPoint needed up to 5 seconds for initial registration of an Endpoint.  The MeetingPoint now temporarily lowers the communication interval so this procedure finishes earlier. 

• The MeetingPoint tagged unverified ByteBlower Endpoint platforms as “Unsupported”.  The tag is renamed to “Unverified”, which means Excentis did not have tested this platform. 

Bugs fixed 

• The MeetingPoint stopped accepting API calls when an “Unavailable” ByteBlower Endpoint was addressed.  This did not only influence the calling test, but also effected other tests and users with “Available” Endpoints.  The only remedy for this was restarting the ByteBlower MeetingPoint service on the ByteBlower server. 

Changelog for 2.20.0 

New features 

• Adding latency histograms over time.  This can be used to visualise/verify the QeD performance of a specific application. 

Enhancements 

• Adding additional frameblasting interval statistics such as : 

• When was the first frame sent or received 
• When was time last frame sent or received 
• Minimum and maximum size of the frames received 

• Better latency measurements for cumulative snapshots.   
  The Endpoint now keeps track of the cumulative data itself instead of delegating this to the MeetingPoint. 

Fixes 

• Fixing crashes when a management/traffic interface was selected, but no IP address was available. 

Changelog for ByteBlower Endpoint 2.19

The ByteBlower Endpoint can be downloaded through our setup pages: https://setup.byteblower.com/wirelessendpoints.html 

For Android, iOS and iPadOS, the app is also available through their respective app stores.

Changelog 2.19.0 (20/10/2022)

Highlights

The ByteBlower Endpoint can now be stopped from the ByteBlower GUI and the ByteBlower API.  
This feature allows the user to stop the ByteBlower Endpoint from the GUI the way it was already possible to stop a ByteBlower Port mid-test.  This new addition can be particularly useful if a longer duration test has been configured and needs to be terminated for any reason.

This feature requires a ByteBlower Server updated to ByteBlower 2.19.0 and a ByteBlower GUI on version 2.19.0.

New features

• The ByteBlower Endpoint can now continue communicating with the ByteBlower MeetingPoint during the test.  When enabled, this allows the user to stop the ByteBlower Endpoint through the ByteBlower API or the ByteBlower GUI when running a test.  A future use-case for this continuous communication is getting real-time results while the ByteBlower Endpoint test is running.
• Allowing the ByteBlower Endpoint to receive a stop command through the API.  Stopping the ByteBlower Endpoint through the API triggers the same behaviour as hitting the "Abort" button on the ByteBlower Endpoint user interface.
• Allowing the user to configure a dedicated management interface.  This interface will be used for all communication with the ByteBlower MeetingPoint and allows out-of-band communication with the ByteBlower MeetingPoint.

Improvements

• The ByteBlower Endpoint settings are now available through the very recognizable cog-wheel on the top-right of the start page. 
• The MeetingPoint information on the main page is now provided when available, no need to hit that Refresh link anymore.
• Adding support for Debian 11 (Bullseye) and Ubuntu 22.04 (Jammy) as a platform to run the ByteBlower Endpoint on.

Bug Fixes

• When using a dedicated traffic interface or dedicated management interface, the ByteBlower Endpoint could use the wrong local IPv6 address to reach the other side. 

Older versions

• ByteBlower Wireless Endpoint 2.16
• ByteBlower Wireless Endpoint 2.14
• ByteBlower Wireless Endpoint 2.13
• ByteBlower Wireless Endpoint 2.12

Download

The downloads for windows/macOS/Linux are found at following location: https://setup.byteblower.com/wirelessendpoints.html 

For Android and iOS you will find the apps in the app stores.

Changelog 2.16.0 (2022-04-11)

New features

• Allows the user to select the specfic interface of interest → Gives more control

           → This can be configured in the settings window accessible from the registration window.

Bugs fixed

You can find the detailed installation instructions in our How to: Install the Wireless Endpoint on your device.

Signal quality has a large impact on Wi-Fi performance. Since 2.11.0 of the ByteBlower Server, ByteBlower API and the Wireless Endpoint, it is now possible to map the RSSI, WiFi channel and the BSSID on your throughput!

Watch it here in action!

Download

The downloads for windows/macOS/Linux are found at following location: https://setup.byteblower.com/wirelessendpoints.html .For Android and iOS you will find the apps in the app stores.

Changelog 2.12.0 (2021-01-22)

(Linux, macOS X and Windows only)

• Fix an issue where a stream used the UDP destination port as the UDP source port.

You can find the detailed installation instructions in our How to: Install the Wireless Endpoint on your device.