Endpoint 2.22


ByteBlower Endpoint Upgrades:

  • Streamlined UI Processing:
    • Enjoy smoother operation! Reduced UI processing requirements free up more processing power for executing additional tasks, enhancing overall performance.
  • Custom Device Names:
    • Personalize device recognition! Users can now override auto-detected names of ByteBlower Endpoints, ensuring unique identification in multi-device environments.
  • Enhanced Interface Details:
    • Stay informed at a glance! The UI now displays interface type (Ethernet/Wi-Fi) and state (Online/Offline) where applicable, offering improved device status monitoring.
  • Improved Desktop Experience:
    • Navigate effortlessly! Desktop platforms now feature a "Pointing Hand" mouse cursor, providing intuitive feedback when hovering over clickable items in the UI.
  • Android Compatibility Boost:
    • Stay up-to-date! ByteBlower Endpoint now supports the latest Android APIs, resulting in reduced processing time for detecting changes in monitored objects like network interfaces and battery levels.
    • Interface statistics are once again available on recent Android versions, ensuring comprehensive monitoring capabilities.


L4S TCP Prague Support:

Experience unparalleled efficiency in network testing with ByteBlower's latest support for L4S TCP Prague in the ByteBlower Endpoint. Discover the readiness and performance impact of L4S firsthand.


ByteBlower Endpoint now extends its support for testing L4S TCP Prague on the following operating systems:

  • Linux: Enjoy full support for both TCP Prague and Accurate ECN when utilizing the recommended Linux kernel. 
  • macOS: Limited to flows in the downlink direction as the macOS only supports Accurate ECN for now.

Stay tuned as we closely monitor the progress of other operating systems in implementing or improving their L4S support. Our commitment remains steadfast in delivering cutting-edge testing capabilities for the latest technologies.


To confirm the compatibility of your ByteBlower and Endpoints with this feature, you can query the Tcp.L4S capability via the API (See API 2.22)

Important: To initiate L4S testing with your Endpoint, it's essential to enable L4S TCP Prague on your device's operating system. Discover how to enable L4S on your endpoint device here: ðŸ“„ Enabling L4S on your Endpoint


Improvement and Fixes:

  • Resolved an issue where the application remained in Armed state during test execution.
  • Addressed an application hang that occurred when aborting a scenario.
  • Corrected the misidentification of IPv6 addresses as invalid or unusable.
  • Fixed an out-of-resources crash that occurred during the configuration of long (12h) tests.
  • Addressed a crash that occurred when fetching results while configuring the next scenario.