Knowledge base
Physical connection with a Meeting Point
Posted by Dries Decock, Last modified by Pieter Vandercammen on 04 December 2018 12:07 PM

Introduction

In this knowledge base article, we describe how to setup your first test using ByteBlower and ByteBlower Wireless Endpoints. We assume the ByteBlower server is already configured and can run wired tests. A back simple to back test is good start.

The next step  is then testing the wireless network, such as an access point. For the ease of reading, we'll use the situation as shown below:

General topology

The upper left corner shows the host computer running either the ByteBlower GUI or API. This machine is able to connect with the ByteBlower server, running both the server software and Meeting Point. On the right you have a typical wireless setup: a wireless access point or home gateway including a wireless access point and one or more ByteBlower Wireless Endpoints installed on mobile devices or laptops, ….

Before you can use a ByteBlower Wireless Endpoint, you need to register the device at a Meeting Point. This article will give an overview of the possible configurations and solutions to configure a ByteBlower server and the implications for the Meeting Point and Wireless Endpoints.

Before we continue, it is important to understand the purpose of the ByteBlower Meeting Point. The Meeting Point is the glue between the ByteBlower GUI or API and the ByteBlower Wireless Endpoints. The GUI never talks directly to an endpoint, it goes through the Meeting Point. This is a daemon running on a ByteBlower server independent from the ByteBlower server daemon. It keeps a list of the available devices, the state of the devices and translates the command from the user to a device specific scenario. It will also collect the results after a run and present them to the user.

Connection through the management interface

Depending on your lab IP topology, it is possible to reach the management interface of the ByteBlower server from the Wireless Endpoints. By default, the Wireless Endpoint will also listen for incoming connections on that interface (TCP port 9002). In this case, the connection scheme would look like this:

Connect over the management network.

The GUI or API will communicate with the ByteBlower server and Meeting Point through the management network (green line). The Wireless Endpoints will communicate with the Meeting Point over the WAN interface of the gateway and the management interface of the ByteBlower server. (orange line)

Separate networks

Sometimes, the management network of a lab is completely separated from the networks under test. In that case, the above described solution will not work. The good news is that every ByteBlower server has spare network interfaces. The solution for this issue is to use one of those additional network interfaces on the server and connect it with the test network.

Connect over a separate network.

The GUI and API will communicate with the ByteBlower server and Endpoint through the management network (green line). The Wireless Endpoints will communicate with the Meeting Point over the WAN interface of the gateway and the test network (orange line). This might involve some routers. Be aware that there is no firewall available on the ByteBlower machine. If needed, use a firewall to prevent abuse of ByteBlower. This article  describes how you can configure such an additional management interface.

Lan only

Some cases prevent the use of a Meeting Point in different network segment. E.g. when a device is tested without an upstream link (so testing a gateway between LAN and WLAN, without an upstream path). The only solution then is to connect a secondary management interface to the LAN side of the gateway, as described here:

Connect over the LAN network.

In such a situation, both the management interface on the management network or an upstream interface on the test network are unreachable for the Wireless Endpoints, so the only option is to connect an interface with one of the available LAN ports of the device under test. This ByteBlower management interface should then be either configured to perform DHCP or use a static IP address.

(0 vote(s))
Helpful
Not helpful

Comments (0)

We to help you!