GitHub Projects - Frameblasting Modifiers
Posted by Craig Godbold, Last modified by Craig Godbold on 16 December 2021 02:04 PM
GitHub Projects - Frame Blasting Modifiers
Following the previous article (Insert Link), we are going to explore some modifications to the frame and frameblasting flows. This will enable us to utilize more of the GUI's features; in particular the time and frame-size modifiers. These features create variations in the throughput which simulate non-uniform traffic flows.
We will look at 3 scenarios:
Each one of the tests will run vs a default frame for comparison purposes.
Part 1. Docking the Ports
When you open the .bbp file you will see the following displayed:
1.1 Connect the Ports to the Trunk Interface.
Port 1 and Port 2 are set are configured for DHCP so they should be docked onto trunk interfaces compatible with DHCP.
You will see that Port_2 has been NAT enabled but this is not strictly necessary.
Part 2. Frame Modifiers
In this part we will look at the different frames and frame blasting flows with their modifications. Frames can be modified in terms of their size (number of bytes) as well as adding a modifier at the level 4 layer. This can mean adding a payload offset. Another feature is changing the UDP source and destination ports at the level 4 layer (see below).
2.2 Frame Blasting Flows
In this step, we will look at the different frame blasting flows and how they transmit the data frames. The settings of the 'Frame Blasting' tab enable the user to adjust the thoughput speed as well as change the uniformity of the throughput. A frame blasting flow will take the frame defined in the previous step and repeatedly 'blast' it from source to destination.
In this example:
The flow is the traffic that will be sent by the ByteBlower server. Here we can define the source and destination of the generated traffic.