Knowledge base:
Wireless Endpoint: FrameBlasting flows requirements
Posted by Pieter Vandercammen, Last modified by Craig Godbold on 29 November 2023 11:56 AM
FrameBlasting flows on the the Wireless Endpoints have a number limitations. This article offers a short summary of those.

Req1. One Frame each Template

FrameBlasting templates for the Wireless Endpoint should have only a single frame.

Many projects already comply with this requirement. A common exception is applying a mix of frames sizes, in this case using multiple FrameBlasting templates can work around this requirement. This brings us to the following requirement.

Req2. Unique UDP ports

A Wireless Endpoint support same UDP port only once for transmission and once for receive. This requirement is of course only necessary within the same scenario. As soon as the scenario finishes, the UDP ports are also released and can be reused in the next start.

Digging deeper, when the same Wireless Endpoint is used multiple times during the same scenario, one needs to take care to avoid reusing the same frame within all templates in the same scenario.

ByteBlower server doesn't have this limitation. This same FrameBlasting template can thus be used in combination with different Wireless Endpoints.

As a work-around one can create new frames with different UDP ports and use those in a new FrameBlasting Template each.

Req3. Only average Latency for Rx

The wireless Endpoint can be used as the source of a latency flow. In this case the ByteBlower server is the receiving end, and all measurements are collected at this server. In this direction both Average and Latency distribution are possible. For long duration tests one should mind time synchronization between Wireless Endpoint and ByteBlower but even with NTP, the measured delay can become negative, this is explained in more detail in this article.

As destination of a latency flow, the wireless endpoint support only measuring the average latency.

Both requirements together result in the available options shown directly below.

Req4. No Out of sequence

The Wireless Endpoints doesn't support the Out-Of-Sequence measurements yet.

Req5. Essential UDP frame modification

Unlike the ByteBlower server, the Wireless Endpoint is limited by the Operating system. This also limits the fields one can configure in the FrameBlasting tab. The following can be modified:

  • Size (Layer 2 tab)
  • IPv4/IPv6 (Layer 2 tab)
  • TOS bits
  • UDP Source & Destination Ports
  • The unique Frame Modifier.

(0 vote(s))
Not helpful

Comments (0)

We to help you!