Knowledge base

2.10.8 (2019-08-29)

Enhancement

  • Add support for ByteBlower 3200 Gen2

2.10.6 (2019-08-14)

Fixes

  • Unintended traffic on the management interface TCP port 9002 could cause the ByteBlower daemon to stop. We've made it robust against these packets
  • MLD Listening Reports could in some rare cases cause the ByteBlower to stop. This is resolved.
  • Some tools couldn't handle the lacking of a dongle. Now those tools report a correct error when the dongle is missing.

2.10.4 (2019-08-08)

Fixes - Configurator

  • The IPv4 gateway was already optional in the management interface configuration, due to an input validation bug, it seemed required
  • When adding a route, an error was thrown when looking for the correct interface to add the route on.

Fixes - ByteBlower

  • ByteBlower is now able to correctly handle fragmented IPv4 packets
  • Improved TCP performance when sending from 10G to 1G and the switch has small buffer sizes and latency is high

Fixes - Meetingpoint

  • New networkinterface on wireless devices was created over time. Info is now updated instead of creating a new interface

2.10.2 (2019-07-04)

Fixes

  • Server: TCP: Fix long performance drops that sometimes occurred in situations with high packet loss.
  • MeetingPoint: Add iOS 13 as supported device
  • Configurator: When the network configuration is corrupt, throw a more adequate error with more information instead of an obscure out_of_range.
  • Configurator: When a custom port configuration is used, the interface was not marked as trunking
  • Configurator: Fixed an issue when the ByteBlower interfaces could not be configured after a fresh install.

2.10.0 (2019-04-24)

Enhancements

ByteBlower

  • Adding support for NBase-T (2.5Gbit and 5GBit) interfaces.
  • Added an option to restart the TCP on a wireless endpoint. A TCP session will automatically restart if its been dropped by a bad Wi-Fi connection.
  • Multiclient TCP API [Beta]

Fixes

  • The server could crash when the FrameTag (Time/Sequence) was requested before the frame bytes were set.
  • Creating a frameblasting flow with ARP packets could cause the server to stop. This is fixed.
  • Restored our /legal directory which was lost in a previous release.

ByteBlower API 2.11.6 (2020-04-15)

Download

You can download the latest version at https://setup.byteblower.com/software.html.

Enhancements

  • Added support for python 3.7 and Windows 64 bits.

Fixes

  • The red 'evaluation license' message has been fixed. Due to a build error the (TCL) installers were created with an evaluation version of BitRock.

ByteBlower API 2.11.4

This API version was not released, this is a ByteBlower Server release only.

ByteBlower API 2.11.2 (2020-02-11)

Download

You can download the latest version at https://setup.byteblower.com/software.html.

Enhancements

  • Added the possibility to configure the BROADCAST/UNICAST DHCP flag.  The ByteBlower Port will use this in the DHCP Process
  • Added extra DHCP timing statistics (timestamps when the DHCP discover/offer/request/ack, DHCPv6 solicit, advertise, request, reply are sent or received)

Fixes

  • When Refresh was called on an OutOfSequence trigger, the result information was invalidated.  Accessing this information caused a crash of the API.
  • When the DHCPv6 Session Information was requested, the actual information was not requested on the server, thus needing an extra Refresh call.  This inconsistency with the other parts of the API is fixed.

ByteBlower API 2.11.0 (2019-12-04)

Download

You can download the latest version at https://setup.byteblower.com/software.html.

Enhancements

  • Added support for the Wireless Endpoint to collect network information over time.

Fixes

  • TCL: The signature for the deprecated method Pcap.Save on our Rx.Capture.Basic was wrong and resulted in an error.
  • TCL: The NetworkInfo object on a Wireless Endpoint can now be Refreshed.
  • Fixed an issue where it was impossible to fetch the Result History for a Frame configured on a Wireless Endpoint.

Misc

  • Our Python API (beta) is now available as a Python wheel instead of using a custom installer.  This gives us the possibility to release them later using PyPi

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.11.4 (2019-09-18)

(Linux, macOS X and Windows only)

  • [Linux] Added support for Debian 10 and Ubuntu 20.04
  • [Windows] Fixing GUI initialization, resolving the attribute warning in the console.

Changelog 2.11.2 (2019-03-05)

  • [Windows] On some systems an unknown battery level was reported as 100%. This affected mostly Windows.
  • [Android] We now support from Android 7 till Android 11. To enable logging ESSID/BSSID/RSSI we had to drop Android 6 support.
  • [All] We’ve revised the FrameBlasting transmit approach. The new algorithm is better able to match the configured duration and rate, especially when the configured rate exceeds the available bandwidth. This occurs regularly in low bandwidth Wi-Fi environments, the excess bandwidth is dropped in these moments.
  • [macOS] Matching Apple guidelines we only use the essential capability set. Where possible we only use coarse Location to be able to monitor ESSID/BSSID.
  • [all] Fixed an issue where the device was marked as Booting Device when the device type contained a quote

Changelog 2.11.0 (2019-12-04)

  • Added support to collect the WiFi interface parameters over time: SSID/BSSID/Channel/RSSI/TxRate on supported devices.

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

This page contains the changelog for version 2.11 of the ByteBlower. How to update your ByteBlower server is explained in following article:

2.11.8 (2020-06-25)

Fixes

  • Fixed an issue where the performance of a 3x00 server dropped significantly on v2.11.6
  • Adding timestamps to the standard output / error logs for the ByteBlower and MeetingPoint
  • DHCP protocol implements the elapsed time value. DHCP servers which rely on this field for high availability will now work as expected.

2.11.6 (2020-04-15)

Fixes

  • Improve the transmit time accuracy of Frame Blasting flows.
  • The "Port.Create" method now works again on the ByteBlower 1200 series.
  • The ByteBlowerPort's result history counters can now be consumed by multiple ByteBlowerPort objects (each ByteBlowerPort contains its own copy of the result history.)
  • Configurator: IPv4 address validation failed when configuring static IP addresses on a management interface

2.11.4 (2020-02-20)

Fixes

  • Fixed a bug which used unicast addresses in the DHCP requests. This could confuse some bridging devices which dropped the requests.

Misc

  • To help our support engineers, we now add the server and meetingpoint version to the logs.

2.11.2 (2020-02-11)

This release primarily focusses on bugfixes.

One of the fixes changes the default behaviour of the DHCP client running on a ByteBlower Port.  The DHCP Client used the broadcast DHCP-technique to obtain its IPv4 address.  As some customers noticed, some devices flagged this DHCP traffic as a broadcast storm when performing DHCP on multiple ByteBlower Ports.  This change in the ByteBlower DHCP client changes the default DHCP technique to the unicast technique, working around the limitation imposed by these devices.  The DHCP technique (broadcast/unicast) can be configured using the ByteBlower API.

Enhancements

  • Server: Added the possibility for the DHCP client to disable the BROADCAST bit in the DHCP flags.  The ByteBlowerPort will then use unicast packets when possible.
    Please note that this is now the default behaviour.  Using our API it is possible to revert to the older broadcast technique when needed.
  • Server: Added extra DHCP timing statistics (timestamps when the DHCP discover/offer/request/ack, DHCPv6 solicit, advertise, request, reply are sent or received)
  • MeetingPoint: Android 10 is now added to the list of supported operating systems.

Fixes

  • Server: Fixed a crash when a ByteBlowerPort was being destroyed and the IGMP or MLD protocols needed to transmit messages.
  • Server: Fixes for IGMPv1 and IGMPv2 where an incorrect back-off interval was used.
  • Server: Fixed an issue where IGMPv1 did check the group address too much.
  • Configurator: Fixed a crash when the network configuration reached an inconsistent state.
  • MeetingPoint: Fixed a crash when the process got an interrupt signal

2.11.0 (2019-12-04)

Enhancements

  • The meetingpoint is aware of SSID, BSSID, RSSI, WiFi Channel and WiFi transmit rate on supported devices. To use these features you will also need to update the Wireless Endpoint on the device and the ByteBlower API installed  on your computer
  • The 24 port NBASE-T swtich for ByteBlower has been added to the byteblower-configurator. This makes it much easier tconfigure it.
  • Unsupported Operating Systems and devices can be registered at the MeetingPoint. This makes them available for test-runs. To make it clear that we've not yet tuned our code for the system we do add the 'unsupported' to the name of the device.

Fixes

  • When requesting the result history on a Wireless Endpoint, all results were returned instead of only the new ones.  This resulted in growing histories (and thus memory usage) over time.
  • Improve TCP performance for flows that have a high number of packets in flight.
  • Fix packet duplication in Streams that have a small number of frames configured.

ByteBlower API 2.12.12 (2021-04-28)

Download

You can download the latest version at https://setup.byteblower.com/software.html.

Fixes

  • Fix crash of the ByteBlower client that could happen when calling API methods on a broken RPC connection.

ByteBlower API 2.12.6-2.12.10

This API version was not released, this is a ByteBlower Server release only.

ByteBlower API 2.12.4 (2021-01-07)

Fixes

  • Fix potential crash of the ByteBlower client that could happen when calling "Members.Clear" on a ScheduleGroup.

Misc

  • Our TCL installer and remote capture tool are now signed with a valid code signing certificate.
  • Our Python API is now available for python 2.7, 3.5, 3.6, 3.7 and 3.8 across all platforms.

ByteBlower API 2.12.2

This API version was not released, this is a ByteBlower Server release only.

ByteBlower API 2.12.0

This API version was not released, this is a ByteBlower Server release only.

This page contains the changelog for version 2.12 of the ByteBlower. How to update your ByteBlower server is explained in following article:

2.12.14 (2021-05-19)

Fixes

  • The ByteBlower GUI was unable to use the Wireless Endpoint due to missing service-UUIDs on the server. (5100 series only)

2.12.12 (2021-04-28)

Enhancements

  • Adding new byteblower-support-tool with functionality for ByteBlower 5100 series

Fixes

  • Fix occasional spikes in latency measurements on the ByteBlower 4100.
  • Fix crash that occurred when running a HTTP flow with a maximum segment size of less than 12 bytes.
  • The ByteBlower Configurator could crash when a DNS server was configured on interface level.
  • The ByteBlower Configurator could crash when more trunking interfaces were configured than allowed by the license.

Misc

  • Adding console utilities so users can configure the keymap (5100 series only)
  • Updating kernel from 4.19.0-13 to 4.19.0-16 (5100 series only)

2.12.10 (2021-03-17)

Fixes

  • Fixes occasional crashes of the MeetingPoint related to checking the license. This was caused by a race condition while locking a Wireless Endpoint when the license was queried.

2.12.8 (2021-02-18)

Enhancements

  • Re-introducing the post-update mechanism.
    This provides the ByteBlower support team with the following information: the current license, the port configuration, the software version from which the update was initiated and the software version the ByteBlower server is updated to.
    This information will only be used for support purposes.

Fixes

  • Fixed TCP performance on the ByteBlower 4100 series' trunking interfaces.
  • The ByteBlower traffic generator tried to start before the network interfaces were up, this caused the traffic generator to crash. (5100 series only)
  • Improve accuracy of latency measurements on 5100 series

Misc

  • Updated Linux kernel from 4.19.0-9 to 4.19.0-13

2.12.6 (2021-01-22)

Enhancements

  • Adding more feedback to the user during initialization and validation operations. These can take a while.

Fixes

  • Fixed a bug that caused ICMP ping replies to sometimes be sent to the wrong destination. (Fixed for both IPv4 and IPv6.)
  • The ByteBlower configurator did not save the fixed network configuration  (1x00, 2x00, 3x00 and 4x00 series
  • The ByteBlower configurator did not save the DNS configuration when configured statically (1x00, 2x00, 3x00, 4x00 series)
  • The ByteBlower configurator did not apply the new DNS configuration when it was altered (1x00, 2x00, 3x00, 4x00 series)
  • When the server could not determine whether an update is available, the system was not able to generate the message of the day. This caused a crash in the ByteBlower configurator. (5100 series only)

Wireless Endpoint support

  • Testing was completed for iOS 14 and macOS Big Sur. The ByteBlower MeetingPoint will not mark these Wireless Endpoints as unsupported anymore

2.12.4 (2020-12-07)

Enhancements

  • The ByteBlower 5100 server can now also update from the console
  • The ByteBlower configurator will warn on an invalid port configurations. Such configurations are mostly encountered during installation of the system.
  • The ByteBlower configurator now also checks the port configuration against the Security license on the server. A warning is given in case of a mismatch, the ByteBlower Server software wouldn't run for such configs.

Fixes

  • Fixed an issue where the ByteBlower configurator did not start when using PTP as a time synchronisation source (2100 and 4100 series only)
  • Fixed an issue where the ByteBlower configurator did not start when an invalid ByteBlower port configuration was set.
  • The login banner (console/ssh) was never updated with the recent information (5100 only)
  • The login banner (console/ssh) was always showing that the updates couldn't be retrieved (5100 only)
  • The OS sometimes provisioned the traffic interfaces with an IP address, even when the configuration told not to. This is fixed (5100 only)


2.12.2 (2020-12-01)

Enhancements

  • The ByteBlower License now supports more than 255 ports on a trunking interface
  • Performance improvement on stateful TCP testing when using IPv6 ports.
  • Improved filtering performance for triggers with a BPF filter containing multiple payload content checks.

Fixes

  • An incorrect timezone configuration could crash the ByteBlower configurator
  • On recent ByteBlower 1300 series servers, ARP failed on trunking interfaces


2.12.0 (2020-11-04)

Warning: This release marks the ByteBlower 1200 server as end-of-life.  The last version supporting this server is 2.11.8

Enhancements

    • Added support for multiple trunking interfaces to the same ByteBlower switch. Please contact support if you're interested in this feature
    • First version with support for the new 100Gbit/s ByteBlower server (ByteBlower 5100)
    • Performance improvements
    • Default value for the ReceiveWindow Scaling Value has been changed from 3 to 8
    • Default value for the SlowStartThreshold has been changed from 65535 to 16776960
    • MeetingPoint: Marking Ubuntu 20.04 as a supported version

    This page contains the changelog for version 2.13 of the ByteBlower. How to update your ByteBlower server is explained in following article:

    Server 2.13.4  (2021-09-16)

    Fixes

    • The ByteBlower 5100 series update could hang due to incomplete configuration.
    • The DHCP header option list now starts with "Message Type" as the first option. This is more conventional and some users rely on it for their testing.

    Server 2.13.2 (2021-09-07)

    Enhancements

    • The speed of the nontrunk interface can now be configured in the port configuration. This will allow the ByteBlower server to match the transmission speed for specific ByteBlower Switches. As an example: The ByteBlower server can now limit a 100Gbit/s interface to 40Gbit/s when connected to a Netgear M4300 (40Gbit/s) switch.

    Fixes

    • Fixed a bug where a ByteBlower Stream did not always report "OutOfResources" when the hardware limit is exceeded.
    • The MeetingPoint did not push its version information to the WirelessEndpoint at registration. This could lead to backwards compatibility issues.
    • The MeetingPoint HeartBeat connections with the WirelessEndpoints now have a specific keep-alive option. Dead peers will now be cleaned up.
    • Fixed a PacketDump (capture) issue where data was received too slowly over the API when capturing specific frame sizes.

    2.13.0 (2021-06-30)

    Fixes

    • The Wireless Endpoint Stream and TriggerBasic Interval results did not have the TimestampFirst and TimestampLast available.
    • The Wireless Endpoint NetworkInfoResultHistory was missing intervals when using intervals not aligned to a second.
    • The MeetingPoint did not implement a stub for SamplingIntervalDurationSet for the supported triggers, stream and frame. This resulted in a Technical error while ConfigError is more appropiate.
    • Fix occasional spikes in latency measurements on the ByteBlower 4100. This completes the same bugfix in the previous version.
    • The TCP MSS (Maximum Segment Size) option in a SYN-ACK now advertises the maximum segment size the TCP can receive. It is no longer affected by the MSS option in the original SYN request it is replying to.

    Enhancements

    • The alpha implementation of the latency Distribution trigger for the Wireless Endpoint is now available.

    Operating System changes

    The machine-id of the system was the same for all systems, causing multiple ByteBlower servers obtain the same IP address through DHCP. It is now generated at first boot time, fixing the symptoms. (5100 only)

    Download

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

    ByteBlower API 2.14.2 (2022-01-25)

    Enhancements

    • Exposing the WiFi Receive rate on the NetworkInterface. When unavailable, -1 will be returned.

    On this page you find the changelog for version 2.14 of the ByteBlower server. How to upgrade to this version can be read in the following article:

    Server 2.14.2 (2022-01-25)

    Enhancements

    • MeetingPoint: marking Android 11, Android 12, iOS/iPadOS 15 and macOS 11 (Big Sur) as a supported WirelessEndpoint platform.
    • MeetingPoint: Next to the WiFi TxRate parameter, the RxRate is now available when supported by the WirelessEndpoint.

    Fixes

    • The ByteBlower configurator crashed while parsing the wget configuration file.
    • The MeetingPoint did not implement some API calls which are available through the API. This resulted in a "TechnicalError".
      Now the more correct "ConfigError" is thrown when a non-default value is set.

    Server 2.14.0  (2021-12-07)

    Enhancements

    Introduction of the new port configuration.

    • This configuration matches the physical ByteBlower topology much closer and doesn't require any changes for the ByteBlower client.

    • The advantage is that each interface shown in the ByteBlower GUI's server view will correspond to a switch attached to the ByteBlower.

    • The strength of this new solution is well visible in daisy-chaining and multi-trunk setups. Find more examples in this article.

    • The upgrade will automatically update the config file to be compatible, but it is impossible to guess the correct physical layout. It is still necessary to manually configure your server to benefit from the new port configurations if you have a non-standard configuration. Please contact support.byteblower@excentis.com if you want help in doing this.

    Fixes

    • 5100 update system: The update could fail when trying to install a prerequisite which was already installed.

    Misc

    • kernel update from 4.19.0-16 to 4.19.0-18 for the ByteBlower 5100 systems.
      This is routine maintenance of the OS. It has no impact on the traffic generation capabilities.

    Server 2.15.0  (2022-02-17)

    Fixes

    • Fixed a performance regression in HTTP flows between non-trunking interfaces on newer generations of the ByteBlower server hardware.

    Server 2.16.4  (2022-05-25)

    Enhancements

    • The ByteBlower support tool (byteblower-support-tool) now collects additional information to better investigate the ByteBlower update system.  The following items are now added:
      • The HTTP Proxy configuration of the ByteBlower server
      • Logging of the ByteBlower update system (ByteBlower 1300, 2100, 3100, 3200 and 4100 series servers)

    Fixes

    • The ByteBlower update system could not handle an empty HTTP Proxy configuration, resulting in a crash.
      • The ByteBlower Update system did not parse some old style version numbers correctly.  In this case the server was not able to update.
        This issue only occurs when such a specific version was installed on the server earlier on.
    • The ByteBlower Update system sometimes required updating twice.
    • The ByteBlower 5100 server series now allows having a trunking interface with less than 3 interfaces.

    Server 2.16.2  (2022-04-28)

    Fixes

    • Fixed a MeetingPoint crash when Wireless Endpoint results came in after the GUI cleaned up its resources.

    Server 2.16.0  (2022-04-11)

    Enhancements

    • Configuration of standard port configurations of the ByteBlower server has been made easier.

                → It is now possible to select the current interface and change it (Trunk ↔ Non-Trunk) and apply a preset.

                → This allows the user more control and flexibility in assigning interfaces and the view in the ByteBlower GUI.

    Fixes

    • Fixed a configurator crash when the interface link status could not be queried.
    • Fixed a configurator crash when the IP configuration of a management interface was being altered.
    • Fixed an issue where the pre-2.14.0 server configuration could not be converted automatically due to configuration errors.
    • Fixed a configurator crash when the ByteBlower license could not be read from the hardware key.
    • Fixed an issue where the configuration wrongfully warned about the configuration not being allowed by the server license.

    Changelog 2.19.0 (20/10/2022)

    Download

    You can download the latest version at https://setup.byteblower.com/software.html.

    Enhancements

      • The API now allows the user to configure continuous communication between the ByteBlower Endpoint and ByteBlower MeetingPoint.  Therefore 2 new methods are added to the WirelessEndpoint object:
        • ScenarioHeartbeatIntervalGet() which allows to read the currently configured Scenario Heartbeat interval.
        • ScenarioHeartbeatIntervalSet(nanoseconds) which allows to set the interval on which the ByteBlower Endpoint should try to communicate with the ByteBlower MeetingPoint.
          A value of 0 disables continuous communication between the ByteBlower Endpoint and the ByteBlower MeetingPoint, which is the behaviour as per pre 2.19.0.
      • The API can now stop a running test on the ByteBlower Endpoint. 
        Therefore one new method is added to the WirelessEndpoint object:
        • Stop().
          In order for this feature to work, the ScenarioHeartbeatInterval parameter must be set to a value other than 0 (disabled) and the ByteBlower Endpoint and ByteBlower MeetingPoint must be running software version 2.19.0 or higher.

      Fixes

      • The ByteBlower TCL API did not have Scenario.Duration.Set method available on the WirelessEndpoint object.

      Server 2.19.0 (20/10/2022)

      Highlights

      • The ByteBlower MeetingPoint now supports stopping a ByteBlower Endpoint from the ByteBlower API or ByteBlower GUI. 
        This feature allows the user to stop a ByteBlower Endpoint app in a way it was already possible with a classic ByteBlower Port.

      New Features

      • Adding support for ByteBlower Endpoints who keep communicating during the test.
      • Adding support to stop a ByteBlower Endpoint during the test.  In order for this feature to work, the ByteBlower API or ByteBlower GUI must be configured so the ByteBlower Endpoint keeps communicating during the test.  This feature requires a ByteBlower API or ByteBlower GUI updated to version 2.19.0 or higher and a ByteBlower Endpoint running at least 2.19.0.

      Improvements

      • Adding iPadOS 15 as a supported platform.
        Note: In order not to break existing scripts, iPadOS is announced as iOS towards the customer.

      Fixes

      • The ByteBlower MeetingPoint could crash when a ByteBlower API disconnected when a ByteBlower Endpoint was executing specific API calls. 
        These calls are used when:
        • Preparing a ByteBlower Endpoint for test execution
        • Starting a test on a ByteBlower Endpoint
        • Gathering results for an executed test.

      Misc

      • The ByteBlower 5100 Linux kernel is updated from Debian version 4.19.0-18 to 2.19.0-21
      • The ByteBlower 3100 and ByteBlower 3200 server network interface drivers are updated so they don't lose network connectivity under high traffic loads.
      • The ByteBlower 5100 system can now update the firmware for the used traffic interfaces.

      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

      • UI: Moved the MeetingPoint address up, so it doesn't get hidden by the on screen keyboard.

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

      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.14.2 (2022-02-18)

      Bugs fixed

      • [Android] In some cases the UI did not forward the MeetingPoint address to the application itself. This caused the application to stay in contacting.
      • The application could be unresponsive after the device went into deep sleep. This was caused by the application trying to catch up with the missed Heartbeats

      Changelog 2.14.0 (2022-01-24)

      New features

      • Support for Android 12

      Bugs fixed

      • Fixed the behavior for flows with a source or destination port which is already in use. The WEP will now ignore the flow and report 100% loss.
      • Fixed a resource leak on Windows when running multiple consecutive scenarios.
      • Fixed a parsing issue detecting zero values, leading to bad parsing of MAC addresses, BSSIDs, ....
      • Enhanced the hearbeat processing thus avoiding ResponseTimeout issues.

      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.

      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.13.2 (2021-12-08)

      New features

      • Android: The app now requests the permissions needed to query the WiFi statistics when starting for the first time. This is done using the familiar Android permissions pop up.
        These permissions are only required when the user is interested in the WiFi statistics. When denied, the "App Permissions" page in the Android settings can be used to grant these permissions afterwards.

      Bugs fixed

      • Heartbeats would fail if whitespace was given in front of, or, at the end of the MeetingPoint address.

      • The heartbeat protocol sometimes timed out before the full heartbeat was handled.
        Now the timeout is not triggered when the data is still going over the network. This fixes an issue where no results were available on slow and high-latency links.

      • The heartbeat protocol will now be less blocking when no network connection is available.

      • TCP Restart could reach a flapping state in slow/high-latency links, so the TCP Flow was restarted even before the TCP SYN/SYN-ACK/ACK mechanism finished.

      Misc

      • The Qt framework used in the UI is updated to the latest 5.15 version.
        For Linux distributions, the Qt release in the distributions software repository is used.

      Changelog 2.13.0 (2021-06-30)

      New features

      • Alpha support for Latency Histograms on incoming flows. Besides the latency histograms in the GUI and API, this will also support the CDF and CCDF graphs which were introduced in the previous GUI release!
      • The Graphical UI of the app now displays the Device UUID and the MeetingPoint version when connected. This enables users to quickly identify the correct device when using the API.

      Bugs fixed

      • Improved start time accuracy. The start time of each flow had a variation between 15 to 500 ms.
      • Under certain conditions, running TCP traffic in the downlink direction (the ByteBlower Server transmits the payload) could stall after about 5 seconds.
      • When sending at low rates, running TCP traffic in the uplink direction (the Wireless Endpoint application transmits the payload), traffic could be very bursty.
      • When the application was idle but connected to a MeetingPoint, the application could crash when pressing the Android Back button.
      • Windows 10 clients are now recognized as Windows 10 systems instead of Windows 8.1

      Misc

      • -Support for Debian 8, Ubuntu 14.04 and Ubuntu 16.04 has been dropped. 2.12.2 is the last supported version for these operating systems. Please contact us if you still require support for these operating systems.

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

      Changelog for ByteBlower Endpoint 2.20

      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.

      ByteBlower Endpoint 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. 

      Older versions

       

      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.

      Introducing Cumulative Latency Distribution Graphs

      The ByteBlower GUI reports now contain CDF and CCDF latency graphs:


      100 Gbit testing

      The new ByteBlower 5100 model is specially designed to allow fast and easy testing on high-speed,
      100 Gbit ethernet networks. It provides best-in-class latency measurements and 100 Gbit performance.

      ByteBlower 5100

      Download

      You can download this version of the GUI here: Download GUI

      Information on how to use the CLT version of the GUI: Introduction to ByteBlower CLT

      Changelog 2.12.4

      This a bugfix release based on feedback received at support.byteblower@excentis.com. All feedback is welcome.

      Bug fixes

      • Comparing the cumulative TCP results to the results over time showed that the first data-point was sometimes missing. In the graphical reports this made a minor difference in the startup phase of the charts.
      • CSV reports now also list the cumulative TCP throughput for traffic transmitted by the Wireless Endpoints. The other direction was already calculated.
      • A fix in the the JSON reports: the current round trip time in the results over time of the TCP element now has the correct value.

      Changelog 2.12.2

      New features

      • [Reporting] Additional CDF and CCDF reporting. This is the main feature of this release.

      Enhancements

      • [General] Updated TCP options in the TCP view.
        • The default congestion algorithm is now Sack + Cubic, similar to most modern Operating Systems.
        • Window scale values now range up to 12. The default value stays at 7, which is a commonly used one.
      • [General] Latency Distributions have been renamed to Latency Histograms.

      Bug fixes

      • [General] To save time, NAT Discovery now skips flows where the source or destination failed to configure. These discoveries would fail either way but would require a long time to do so.
      • [Reporting] The TCP roundtrip element in the JSON report has now the correct value.

      Changelog 2.12.0

      Improvements

      • [General] The GUI can now also control the new 100G ByteBlower 5100 server.
      • [Reporting] Improved JSON reports. Snapshots are ordered now.
      • [Reporting] Using milliseconds by default for latencies.
      • [Reporting] Using Mbps by default for throughputs.
      • [Reporting] Additional logging in the report browser. This will help debugging.
      • [Reporting] Less memory usage while generating JSON reports, by using a streaming approach.
      • [Reporting] Opening a report automatically after a scenario finished, but only when there are test results.
      • [UI] Showing help when relaunching a scenario that became invalid. Also opening the Solution View now.

      Bug fixes

      • [General]: Adding a frame size filter for 60 byte frames also. This makes the filter more selective and avoids counting other large sized frames.

      Known issues

      • [General]: The GUI is not yet fully compatible with macOS 11 Big Sur. Contact us to get a development version.

      More info, less bytes in ByteBlower Captures

      We are delighted that in this new release of ByteBlower GUI v2.13 the PCAP capture has been improved! This allows you to easily collect relevant network traffic.
      The new features allow you to:
      • Filter traffic easily, keeping only the interesting packets
      • Truncate packets to the headers that matter
       

      Changelog 2.13.0

      Bug fixes
      • String sanitizing when creating the report filename from the scenario name. Could have caused an error resulting in lost test results.
      • Improved algorithm to process HTTP test results over time. No more occasional duplicate snapshots.
      Enhancements
      • Added links to the ByteBlower Example GUI projects. These are available through the help button in the dialog to create new ByteBlower GUI projects. Clicking it opens the ByteBlower GUI examples in a new window.
      • A fresh help dialog for the Latency Histogram in the ByteBlower HTML Reports.
      • When a new server version is available, this is visualized more clearly in the Server View.
      • More configuration options for the Packet capture. File size can be kept to minimum with the BPF Filter and due to configurable truncation of the Packets. This is an advanced capture. Starting a capture immediately is still possible on ByteBlower Ports and interfaces.
      • Packet captures can be started on ByteBlower Ports.
      • The context menu of the ByteBlower Port view also has the option to start a capture.

      64-bit version for Windows

      The ByteBlower GUI is now available for Windows 64-bit. The biggest benefit is that the GUI can now access much more of the available memory.
      Download the 64-bit GUI from setup.byteblower.com

      Changelog 2.14.2

      Enhancements
      • Upgrade of the Log4j library to v2.16.0 This avoids potential vulnerabilities due to this library.
      • The GUI warns when the report browser is about to run out of memory due to the total size of open reports. Without memory to spare, crashes are likely to occur. This warning comes early for those using a 32 bit version, updating to 64 bit is strongly recommended.
      • PCAP import in the Frame view is also available for Windows 64 bit.

      Changelog 2.14.0

      Enhancements
      • The GUI is now also available for Windows x86_64.
      • The preferred data-rate unit (Kbps, Mbps, Gbps, ...) is now also applied when creating new Frame Blasting flows.
      • The warning icon is now orange instead of blue.
      Known Issues
      • The 64-bit version for Windows does not yet support the "PCAP Import" feature.
        This will become available with the next release.

      RSSI/SSID/BSSID in the ByteBlower Report

      The ByteBlower GUI now includes the RSSI/BSSID/SSID statistics in the reports. With these stats you'll gain a much clearer insight into the throughput and latency results of your Wi-Fi testruns.

      How do you configure this new report element? Great news - there is no need to! These stats are added automatically as soon as you use one of the Wireless Endpoints. These stats are supported since version 2.11 of the app. Of course by using the most recent version you'll avoid any of the early pitfalls.