ByteBlower Endpoint from the command line

Introduction

The ByteBlower Wireless Endpoint used to run only using a graphical user interface.  This is nice, but what about headless servers?
Since 1.1.22, the ByteBlower Wireless Endpoint supports a basic command line interface. This is of course only applicable to those running the app on Windows, Linux, or Mac.

This article will guide you through the options and behaviour. The good thing is the ByteBlower Endpoint executable can run both with a GUI and without.

Linux
  • Use no program arguments to start the graphical view
    # byteblower-wireless-endpoint
  • Add a MeetingPoint address for the command line mode
    # byteblower-wireless-endpoint 10.5.5.144

More help is available with the -h or --help arguments.

MacOS
  • Use no program arguments to start the graphical view
    # /Applications/ByteBlower Wireless Endpoint.app\
    /Contents/MacOS/byteblower-wireless-endpoint
    or double-click on the application
  • Add a MeetingPoint address for the command line mode
    #  /Applications/ByteBlower Wireless Endpoint.app\
    /Contents/MacOS/byteblower-wireless-endpoint 10.5.5.144

More help is available with the -h or --help arguments.

Windows
  • Use no program arguments to start the graphical view
    #  ByteBlowerWirelessEndpoint.exe
    or double-click on the application
  • Add a MeetingPoint address for the command line mode
    #  ByteBlowerWirelessEndpoint.exe 10.5.5.144


More help is available with the -h or --help arguments. You'll receive the text below:

# byteblower-wireless-endpoint --help
Usage: byteblower-wireless-endpoint [options] meetingpoint
Connect the wireless endpoint to the Byteblower MeetingPoint and it will serve as a traffic generator and monitor.

Options:
-h, --help Displays this help.
-v, --version Displays version information.

Arguments:
meetingpoint The IP address or resolving domain name of the meetingpoint

Output

When the app is connected to a meetingpoint, the output will be updated with periodically.

# byteblower-wireless-endpoint byteblower-tp-1300.lab.byteblower.excentis.com
 • Status: Registered || Rx: 0.00 Mbps | Tx: 0.00 Mbps

What can be seen in this output?

  • The dot at the beginning of the line:
    The dot will blink with every heartbeat.  This is the application trying to communicate with the ByteBlower Meetingpoint.
  • Status:
    The status field shows the status of the application. 
    • Contacting: it tries to connect to the meetingpoint.
    • Registered: the application is idle and is waiting to receive a command from the ByteBlower
    • Armed: the application has received a command to run a scenario, it is waiting to start the actual traffic.
    • Running: Traffic is ongoing
  • Rx and Tx: 
    This is the throughput the app is receiving (Rx) and transmitting (Tx)