Welcome to the Excentis support portal. The requested article is not yet available to you. Please login with your credentials. If you don't have login credentials yet, please click here or contact us at support@excentis.com
Knowledge base

By default the XRA-31 system will use DHCP to get its management IP. In some lab-environments this is not wanted. This page explains you how you can configure a fixed IP on the management interface.

XRA-31 version 5.2 and higher

Since XRA-31 version 5.2, we have switched from the network manager wicd (unsupported as of Debian bullseye) to NetworkManager.

NetworkManager is considerably more flexible and allows you to configure both the MAN1 (device eno1) and MAN2 (device eno2) interfaces separately, both in IPv4 or IPv6 mode. Static wicd IPv4 configuration is automatically migrated during an XRA-31 system upgrade and is present in the connection profile "Migrated from wicd".

Right click on the networking icon in the system tray to configure the management IP address: first via clicking on "Edit Connections..." and configuring the settings of a connection profile, next by toggling the checkbox "Enable Networking" twice to disable/re-enable networking to forcefully apply the settings.

XRA-31 version 5.1 and lower

All the configuration is done by using the Wicd tool on the system.

Start the Wicd graphical UI from either the main menu

or via the network configuration icon on the bottom right on your screen

The main status and configuration window will open.
Click on "Properties" to change the configuration of the wired connection:

Select "Use Static IPs"
Configure the IPv4 address, netmask and gateway.

Configure DNS settings:

  • DNS domain: your domain name
  • (optional) Search domain: domains to search in when looking for a host name
  • DNS server: One or more DNS servers

Press "OK" to save the changes.

Disconnect + re-connect to apply the changes immediately.
Please note that existing network connections will be closed.

The connection will be established now with the new configuration:

Known issue

Up to XRA-31 version 3.1, there is a bug in Wicd Network Manager that causes connection problems for a static IP address (leading to "Not connected" status after clicking "Connect").

As a temporary workaround, please configure the static IP address settings as detailed above and perform the following additional steps after each system reboot.

  1. Close the Wicd Network Manager. Right click on the network configuration icon on the bottom right on your screen and click Quit.
  2. From the main menu, open a command line (LXTerminal) and execute   wicd-cli --wired -c
  3. Run the command  ip address show  to verify the network settings have been successfully applied.

A permanent patch will be included in XRA-31 version 4.0 and higher to make these steps unnecessary.

Are you looking to configure a fixed IP address or change the network configuration? Please take a look at this page.

Log in to you system

Using screen and keyboard, you can log in at the graphical desktop.

See also How to: Log in at the XRA-31 system for more details.

Check management IP address

Using the IP command line

From the main menu, open a command line (LXTerminal)

Use the ip command to obtain the current IPv4 and IPv6 addresses

ip address show

You can find all assigned IP addresses in the output

ByteBlower Server/Meeting Point Changelog - 2.21

The ByteBlower 2.21 release includes a mjor new feature for Endpont testing: Real-time results 

This allows users the option to receive results during the test in the realtime view in the GUI. 

In order to use this feature, the server, Endpoint and GUI must be updated to 2.21.

Furthermore, the Endpoint must be allowed to communicate with the MeetingPoint during the test by enabling the "Heartbeat" mode in the project settings.

Accessing them is the same as with a regular ByteBlower Port object.  Just call the Refresh() on the corresponding History objects. 

Important to note:

  • If you upgrade the server to 2.21, you will no longer be able to use ByteBlower Endpoint 2.16
  • Clients running the ByteBlower Endpoint application 2.19 are now deprecated
  • The 2.21 versions of the ByteBlower Server/MeetingPoint are the last versions to support these older versions of the Endpoint.

We highly recommend updating all ByteBlower features to the latest versions as this improves performance and reduces the probabiltiy of unusual behavior arising from different versions.


ByteBlower Version 2.21.2 ensure no more communication hiccups. Here are some release highlights:

Synchronised Reporting:
ByteBlower's latest release boasts enhanced clock synchronization by the MeetingPoint. Even in cases of significant clock differences, rest assured that you'll receive results that are both accurate and reliable.

Endpoint Persistence Improved:
Experience uninterrupted testing! Our latest release guarantees that Endpoints stay active until every single result is gathered and processed. Say goodbye to disruptions during crucial testing phases and enjoy a seamless testing experience. We've addressed a scenario where Endpoints were erroneously marked as unavailable during lengthy test result processing. Stay seamlessly connected throughout extended test runs, ensuring a reliable and efficient testing environment.

SSH Upgrade Hassle Resolved:
Upgrade with confidence! We've tackled a troublesome issue where SSH configuration impeded ByteBlower 5100 series server upgrades. Now, enjoy the smooth and uninterrupted process of upgrading servers without any hitches.

Upgrade to ByteBlower Version 2.21.2 now and witness a new level of precision, reliability, and uninterrupted performance in your network testing endeavors!

Happy Testing!



Alongside the real-time Endpoint results, we have made further improvements to the server in terms of performance and configurability.


The out-of-sequence trigger now also provides counters for packet loss detection. This means that packet loss can be detected from one trigger without having to compare to a Tx stream.

In addition, the performance of Frame Blasting flows with out-of-sequence detection has been improved. 

Interval snapshot

When combined with a 2.21 ByteBlower Endpoint, the snapshot interval can now be configured.   For older endpoints, this remains fixed at 1 second.


The meeting point information handling has been improved by reducing the amount information reset when an Endpoint re-registers

TCP will now correctly send an ACK in response to TCP Keep-Alive messages even if they have no payload.



New Features:

  • Low Latency DOCSIS configuration settings (TLVs 91, 92, 93, 94)
  • DOCSIS 3.1 Synchronisation settings (TLVs 101 and 102)
  • Extra Service Flow Encodings (subTLVs 48 and 49)
  • Support for DOCSIS 4.0 (TLVs 96, 97, 103 and 104)


New Features:

  • Support for MacOS Catalina
  • Cheat mode is no longer required to open config files with eSafe TLVs


    • Fixed an issue where negative MIB value numbers were converted to their 2-complement positive number
    • Fixed erroneous constraint check for Guaranteed Grant Rate TLV


    New Features:

    •  added Low Latency DOCSIS support:
      • 70/71: new Aggregate Service Flow Subencodings, including
      • [70/71].42: Low Latency Aggregate Service Flow Encodings
      • 24: new Subencodings for Proactive Grant Service
      • [24/25].40: new Subencodings for AQM (including ImmediateAQM)


    • Fixed issue where Activity Detection parameters could not be added in Energy Management DLS mode



    • Removed frequency limitation checks that are not valid anymore for DOCSIS 3.1


    New Features:

    • new TLVs added:
      • 83: DTP Mode Configuration
      • 84: Diplexer Band Edge
      • 74.4: Energy Management DOCSIS Light Sleep Mode Encodings
      • 41: added channel type subtlvs for 3.1 (4.1.3 and 4.2.5)
      • Added generics for L2VPN encoding and DUT filtering
    • tooltip improvements
    • filename is displayed in titlebar


    • Encoding of CVC Chain is now a degenerate PKCS#7 structure
    • Refresh button caused saved check to fail
    • Extended CMTS MIC calculation is corrected
    • Service Flow traffic rates were limited to 2Gbps
    • wrong TLV number was displayed in case of parsing error
    • CMIM classifier was not recognized as valid classifier


    New Features:

    • new TLVs added (includes all 3.1 TLVs!):
      • 70: Upstream Aggregate Service Flow
      • 71: Downstream Aggregate Service Flow
      • 72: Metro Ethernet Service Profile
      • 73: Network Timing Profile
      • 76: CM Upstream AQM Disable
      • 79: UNI Control Encoding
      • 81: Manufacturer CVC Chain
      • 82: Co-signer CVC Chain
    • new service flow SubTLVs added:
      • 36: Aggregate Service Flow reference
      • 37: MESP reference
      • 39: Service Flow to IATC Profile Name Reference
      • 40: AQM Encodings
      • 41: Data Rate Unit Setting
    • added eSTB encodings
    • added cheat mode in CLI
    • updated installer with improved OSx JRE detection


    • Fixed adding Generic (Sub)TLV with high TLV numbers
    • Fixed Energy Management TLV location parsing issue
    • Fixed warning when adding TCP/UDP classifiers in an IPv6 classifier

    ByteBlower GUI Changelog 2.21

    Experience Enhanced Flexibility with ByteBlower GUI 2.21.

    Unlock a host of powerful features designed to enhance your testing experience. ByteBlower GUI 2.21 brings a range of improvements, especially for ByteBlower Endpoint users. It empowers you with Heartbeating mode, real-time results, flexible TPID configuration, ipv6 firewall traversal, and more!

    Important Note: For optimal performance and compatibility, we strongly advise using "ByteBlower GUI 2.21" in conjunction with "ByteBlower Server 2.21," "MeetingPoint 2.21," and "ByteBlower Endpoint 2.21."

    With the all new ByteBlower 2.21 release, you are all set to get your hands on these exciting new features

    Heartbeating Mode (Endpoint):

    Introducing Heartbeating Mode: Maintain seamless contact with ByteBlower Endpoints by sending regular heartbeats after specified intervalsthrough the duration of the test. Enable or disable this mode via "File" -> "Project Properties" -> "Scenario" -> "Wireless Endpoints" -> "Keep contact with each ByteBlower Endpoint".

    Note: Heartbeating Mode is enabled by default for new projects at a 5-second interval. Ensure manual activation for older project files.

    For more about “Heartbeating Mode” and its use in the ByteBlower API,  read here.

    Realtime Results (Endpoint):

    Experience real-time insights with ByteBlower Endpoint during active test scenarios. Ensure "Heartbeating Mode" is active before project execution for real-time ByteBlower Endpoint results.

    • For wireless endpoints, dive deeper into performance metrics on the 'Gateway' Monitor RSSI values, SSID, and BSSID in real-time, synchronized with the " Heartbeating" interval specified in settings.

    Stable Longer Duration Tests (Endpoint):

    Longer duration tests are now more robust than ever. Traditionally, these tests necessitated substantial data transmission towards the scenario's conclusion, often causing disruptions on less stable connections.

    However, with the introduction of "Heartbeating Mode," this issue is mitigated. Results from the endpoints are now transmitted at defined intervals throughout the test, significantly reducing data transmission near the end of scenarios. This enhancement assures heightened stability during extended tests, ensuring your results remain uninterrupted.

    Preserved Reporting (Endpoint):

    Forget the worry of losing data. "Heartbeating Mode" in ByteBlower 2.21 now offers partial result reporting. Even if a device drops out, results up to the last interval are preserved. Ensure "Heartbeating Mode" is enabled for this safeguard.

    Flexible TPID Configuration:

    Unlock the potential of Q-in-Q and diverse TPID configurations for your VLAN-tagged traffic plans. ByteBlower 2.21 now lets you effortlessly configure various common TPID types via the GUI. Ideal for scenarios involving distinct inner and outer VLANs with different TPIDs.




      • User selection of TPID is required.
      • Requires ByteBlower Server version 2.20 or later, with automatic project updates for older versions.

      IPv6 Firewall Traversal:

      Introducing the dedicated firewall option for IPv6 traffic, addressing challenges related to downstream traffic transmission.

      • Simple Activation: Easily enable the firewall within the Ports view by selecting "Yes" in the firewall column.
      • IPv4 Parity: The IPv6 firewall functionality mirrors the behavior of NAT in IPv4, ensuring a familiar and secure experience.

      Refreshed ByteBlower Reports:

      A refreshed reporting format awaits you right after running a new scenario. We've maintained the core features while ushering in a modern aesthetic.

      • Streamlined Unit Selection: Now, effortlessly customize your report by selecting throughput and latency units directly within the report interface, eliminating the need to navigate project settings.
      • Efficiency Boost: Beneath the surface, significant under-the-hood enhancements enhance reporting efficiency, paving the way for seamless future developments.