Setup the LANforge Ports so that they have valid IP addresses.

1. Go to the Port Manager

2. Modify port for Endpoint A (eth2)

3. Modify port for Endpoint B (eth3)

4. Verify the port configuration

For more information see LANforge User's Guide: Ports (Interfaces)

Create a Layer-3 Connection using the two configured ports.

1. Go to the Layer-3 tab

2. Create a new Cross-Connect

3. Verify the new Cross-Connect

For more information see LANforge User's Guide: Layer-3 Cross-Connects (FIRE)

Run traffic and observe results.

1. Select the cross-connect on the Layer-3 tab, click Start and then Display

2. View the Layer-3 cross-connect display

For more information see LANforge User's Guide: Layer-3 Cross-Connect Display

In this case, the overall throughput of the DUT is approximately 76Mbps. The Report Manager can also be used to record the throughput over time.

1. Select Report Manager from the Reporting pull-down menu

2. Choose a directory to save raw (.csv) data then click Start Saving. After desired test duration, click Stop Saving and Generate Report. NOTE: Your report will look cleaner if you stop traffic about 2 minutes before you stop saving data.

3. Choose a directory to save the HTML report, select the entities to be included, then click Generate Report

4. This window lists all the reports being generated. The last line indicates the location of the HTML report.

5. View the HTML report

For more information see LANforge User's Guide: Reporting

Setup the LANforge Ports so that they have valid IP addresses.

1. Go to the Port Manager

2. Modify port for Endpoint A (eth2). Set a valid network IP address and Gateway IP.

3. Modify port for Endpoint B (eth3). Set a valid network IP address and Gateway IP.

4. Verify the port configuration

For more information see LANforge User's Guide: Ports(Interfaces)

Create a Layer-3 Connection using the two configured ports.

1. Go to the Layer-3 tab

2. Create a new Cross-Connect

3. Verify the new Cross-Connect

For more information see LANforge User's Guid: Layer-3 Cross-Connects (FIRE)

Run traffic and determine router throughput.

1. Select the cross-connect on the Layer-3 tab, click Start and then Display

2. View the Layer-3 cross-connect display

For more information see LANforge User's Guid: Layer-3 Cross-Connect Display

For this example, a low performance router was used to illustrate poor throughput, variable latency, and dropped packets.

1. Go to the L3 Endps tab

2. Scroll to the right to view Latency and Dropped Packets

For more information see LANforge User's Guid: Layer-3 Endpoints (FIRE)

The UDP Throughput test will use a scripted Layer-3 connection to vary the rate and payload size to determine the bi-directional UDP throughput of the DUT across the scripted parameters.

1. On the Port Manager tab, setup the LANforge ports with valid IP addresses.

2. On the Layer-3 tab, create a UDP connection.
   

   1. Set Endpoint Side-A to use the DUT WAN port

   2. Set Endpoint Side-B to use the DUT LAN port

   3. Select CX Type LANforge UDP then select Apply.

3. Select the Script button to setup the scripting parameters.

   1. Setup the script to iterate over the rates

   2. Specify the payload sizes to be tested.

   For more information see LANforge FIRE Cookbook example: Scripted Layer-3 Test

4. Highlight the connection and select the Start button.

5. The final test report shows the results of the test run. Here we can see that the DUT has the best bi-directional throughput with 1460Byte payloads at 24.9Mbps.

   For more information see Full script report for the UDP test.

The TCP Concurrent Connections test will measure the maximum number of simultaneous TCP connections that the DUT can maintain at once.

1. On the Port Manager tab, create 5 MAC-VLANs on the LANforge Port connected to the DUT LAN port.

2. Verify that the MAC-VLANs have correct IP addresses.

3. Create a Layer-3 connection that has a low-speed rate with Multi-Conn set to 10000 on Endpoint Side-A. Multi-Conn should be set to 1 on Endpoint Side-B.

   1. Side-A will be one of the MAC-VLANs and Side-B will be the port connected to the DUT WAN port. This setup will initiate the TCP sessions from the LAN side of the DUT.

   2. Low-speed depends on the DUT, we could also set the rate to zero which would allow the TCP connections to be setup without payload data to be transmitted, but this would not give an accurate picture of the firewall performance. Here we are using 1Kbps connections with 1KB size payload.

   3. This is an iterative test, the number of TCP connections to use will depend on the DUT capabilities. Modify the number of connections as necessary to find the most accurate measurement.

   4. The DUT should be power-cycled to reset it before each test run.

4. Select the Batch-Create button to create 4 more copies of this connection each with a new MAC-VLAN port.

5. Highlight and Start each set of 10000 connections until the target max simultaneous connections are running.

6. On the Layer-3 Endpoints tab, highlight the Running A-Side Endpoints, then right-click and select Calculations.

7. The top line, Sum, is what we are interested in for Maximum Concurrent TCP Connections.

8. Scroll right to the CX Active and CX Established columns and select the Refresh button. This DUT can maintain a maximum of 41,864 simultaneous TCP connections.

   1. CX Active is the metric we are attempting to measure, Maximum Simultaneous TCP Connections. It will fluctuate with the DUT's ability to maintain the number of active TCP connections.

   2. CX Established is the number of TCP connections LANforge has established since the start of the test. It will continue to increase as the DUT closes the TCP connections it cannot maintain.

The TCP Connections per Second test will measure the rate of TCP connections that can be setup through the DUT.

1. Create a Layer-3 TCP connection with the Duration and IP Port set to zero.

2. Highlight and Start the connection.

3. View the Connections/second rate on the Layer-3 Endpoints tab. This DUT can setup about 120 Connections/second.

For more information see LANforge GUI User's Guide

Setup the LANforge Port so that it has a valid IP address.

1. Go to the Port Manager

2. Modify the port connected to the Web Server. Set a valid network IP address and Gateway IP.

3. Verify the port configuration

For more information see LANforge User's Guide: Ports (Interfaces)

Setup the URL requests.

1. Go to the Layer-4 tab

2. Create a Layer-4 Endpoint:

   1. Enter a name and select the port configured in the previous step

   2. URLs per 10m should be set to around 1,200,000 which is 2,000 URLs/second

   3. Leave the SSL Cert alone as we are not using it in this example

   4. UL/DL should be set to Download

   5. URL should be set to the Web Server's IP address and file that you wish to download. In this example, index.php is a small test file.

   6. File is the designated location that the downloaded file will be stored. In this example, we use /dev/null which will essentially throw the file away so that it does not slow down the LANforge system with writing files.

   7. Select the 'Allow-Reuse' checkbox to maximize the number of URL requests LANforge can make per connection

3. Repeat the above step to make 10 Layer-4 Endpoints:

   1. Each of the 10 Layer-4 Endpoints will attempt to generate 2000 URLs/second, effectively generating 20,000 URLs/second

For more information see LANforge User's Guide: Layer 4-7 Endpoints

Run traffic and determine Web Server performance.

1. On the Layer-4 tab, select one Layer-4 endpoint, click Start, then repeat for all 10 Layer-4 endpoints:

   1. As each endpoint is started, the rate of URLs/second will start to converge on a rate that the Web Server is capable of providing. Finding the final Web Server performance rate is a matter of adding up the rates of all running Layer-4 endpoints.

   2. Several Layer-4 endpoints (10 in this case) are used so each endpoint can make an independently large number of URL requests without having to wait for too many replies. Each URL request is waiting for a reply from the Web Server, so if only one Layer-4 endpoint was making requests, it would spend too much time waiting for replies instead of generating more requests. Spreading the URL requests over several endpoints allows each LANforge connection to the Web Server to maximize its rate of URL requests.

2. Layer-4 Endpoint Results:

   1. After starting all 10 endpoints, and letting them run for at least 1 minute, the overall URLs/second rate converges to around 17,000 URLs/second.

For more information see LANforge User's Guide: Layer 4-7 Endpoints

Configure eth1 to serve DHCP and TFTP.

1. Go to Status panel in LANforge GUI. Click 'Netsmith' button on the Resource.

2. Right-Click in empty space and create a new Virtual Router. Use default values and click OK.

3. Drag eth1 into the virtual router. Then double-click the virtual eth1 icon to configure DHCP. DHCP files for CMTS setups must be hand-written by the user. Configure LANforge to use this custom-dhcp config file.

4. When Netsmith setup is complete, click Apply on the main Netsmith window to start up the DHCP service, etc. This screenshot was taken after the Layer-3 connections were set up.

Configure eth2-9 to use DHCP

1. Go to Port-Mgr tab, double-click each port, and make sure the DHCP option is selected. Apply changes.

Set up Layer-3 connections to generate the throughput tests.

1. Go to the Layer-3 tab, and click Create. Many cable modems are configured to do NAT and/or some firewalling, so normally you will need the connections to be TCP and to originate out from the client-side port. So, choose the LANforge/TCP connection type, and make the 'B' side eth1. Everything else can stay at the default values because we will use a script to automate the settings.

2. Create 8 similar connections, always with B side port of eth1, and use A side ports eth2-eth9. In the Create/Modify window you can just change the name, change the port, and press apply. This will make copies of the connections.

Create Test-Group to control the 8 Layer-3 TCP connections.

1. Go to the Test Group tab, and click Create. Select the 8 Layer-3 TCP connections you just created in the previous step and add those to the Test Group. Click Apply and make sure the new group shows up in the Test Group table.

2. We need to add a script to automate the test. Click the Script button in the Test Group create/modify window. Choose RFC 2544 script type. In this scenario, we want to test each modem one at a time, so we select the Sequential option for Group Action. The rates sections determine the speeds for each iteration. In this case, the first iteration will send from B to A at 35Mbps. This is the download test. The next iteration will upload from A to B at 17Mbps. When the two iterations are complete, the script will repeat on the next Layer-3 connection.

Run the test

1. To start the test, select the Test Group in the table and click the Start button. You should see a script-report window pop up, and the state should go to running. To see a live report of throughput and other values, right-click on the Test Group table and select the Dynamic Report option

2. View the individual connectionsTo start the test, select the Test Group in the table and click the Start button. You should see a script-report window pop up, and the state should go to running.

Gather reports

1. When the script completes, a summary of each iteration will be shown in the Script Report window. The text may be converted to HTML, but for this particular script, the graphs are not useful because we are using Sequential mode, so just saving the text to a file or printing it is probably the best option. Note that some of these tests failed the constraints configured in the Script. In this case, it is because those modems were not capable of the requested speeds.

2. When the script completes, you could also pause the dynamic report and print it. For an electronic copy, use a PDF printer to create PDF files instead of printing to paper.

3. The Layer-3 tab will color-code the 8 connections, with red meaning fail, and green meaning pass. You can print the connections you are interested in by selecting them in the table and using right-click → Table Report. This report can be printed or otherwise saved.

Setup the LANforge port so that it has a valid IP address and IP mask.

1. Go to the Port Manager

2. Modify the port connected to the DSLAM. Set a valid network IP address and IP mask.

3. Verify the port configuration

For more information see LANforge User's Guide: Ports (Interfaces)

Setup virtual interfaces.

1. On the Port Mgr tab, select the port that will connect to the multi-port switch and will also be your VLAN trunk. This is the LF Edge part of the diagram.

2. Click the Create button:

   1. Select the 802.1Q-VLAN virtual interface type

   2. The VLAN ID should correspond to your multi-port switch VLAN configuration

   3. Enter Quantity (number of virtual interfaces to be created)

   4. Enter the appropriate IP address and IP mask

   5. Click OK or Apply to create the virtual interfaces

3. Verify that the virtual interfaces are created and have the correct IP assignments

4. Modify each port's MAC address for each virtual interface so that they are unique

   1. Select the Set MAC checkbox on the left to edit the MAC address field

5. Scroll to the right to verify that the MAC addresses are unique

For more information see LANforge User's Guide: Creating & Deleting Virtual Interfaces

Create Layer-3 connections.

1. Go to the Layer-3 tab

2. Click the Create button

   1. Fill in a connection name, select a connection type and set the report timer

   2. Make endpoint A the DSLAM upstream port or LF Core

   3. Make endpoint B the CPE downstream port or LF Edge

   4. You can make the TX/RX rates asymmetric for the connection to simulate how the connection would be used in a real-world scenario. Here we have about 5Mbps downstream (DSLAM to CPE) and 1Mbps upstream (CPE to DSLAM).

   5. Click Apply to create the connection

3. Create multiple connections

   1. Change the connection name and endpoint B to the next virtual interface then click Apply to create the next connection.

   2. Repeat until all five connections are created.

For more information see LANforge User's Guide: Layer-3 Endpoints (FIRE)

Run traffic.

1. Select the connections you want to start

2. Click the Start button

For more information see LANforge User's Guide: Layer-3 Endpoints (FIRE)

Setup the LANforge ports so that they have valid IP addresses and IP masks.

1. Go to the Port Manager

2. Modify eth2 and eth3 to set a valid network IP address and mask

   1. If your network has DHCP service, you can select the 'DHCP-IPv4' checkbox so that each port is a DHCP client and will acquire its IP address from your DHCP server

3. Verify the port configuration

For more information see LANforge User's Guide: Ports (Interfaces)

Setup Test 1, a Directed VoIP call.

1. Go to the VoIP/RTP tab

2. Click the Create button:

   1. Enter test-1 in the CX Name field

   2. Select the Multi-Call and Directed buttons

   3. Endpoint A is on Port eth2 in this example. If you have a PESQ licensed server available, you can select Record and Enable PESQ.

   4. Endpoint B is on Port eth2. If you are using PESQ, be sure to enter a Record file and the IP address and port of your PESQ licensed server. Be sure to select the Rcv Call checkbox for this endpoint to receive the call.

   5. Click OK to create the VoIP Directed call

3. Verify that the test call is created

For more information see LANforge User's Guide: VoIP Call Generator

Setup Test 2, a Gateway VoIP call.

1. Go to the VoIP/RTP tab

2. Click the Create button:

   1. Enter test-2 in the CX Name field

   2. Select the Multi-Call and Use Gateway buttons

   3. Endpoint A is on Port eth1 in this example. Be sure to enter the proper username and password for the endpoint so that it can authenticate with the VoIP Gateway if necessary.

   4. Endpoint B is on Port eth2. Be sure to select the Rcv Call checkbox for this endpoint to receive the call.

   5. Click OK to create the VoIP Gateway call

3. Verify that the test call is created

For more information see LANforge User's Guide: VoIP Call Generator

Run Test 1 and Test 2 individually.

1. Select Test-1 and click the Start button

2. Go to the VoIP/RTP Endps tab to see detailed results:

   1. The PESQ score will be reported after the first successful call is completed and updated after each subsequent call

   2. NOTE: Endpoints are Unregistered while the call is in progress because they are not calling through the VoIP gateway

3. Stop Test-1, select Test-2 and click Start

4. Go to the VoIP/RTP Endps tab to see detailed results:

   1. PESQ remains 0: 0 when it is disabled for the call in progress

   2. NOTE: Endpoints are Registered with the VoIP gateway while the call is in progress

   3. Calls Attempted, Calls Completed and Calls Failed can be viewed by scrolling to the right on the VoIP/RTP Endps tab

For more information see LANforge User's Guide: VoIP Call Generator

Configure the physical interfaces.

1. Go to the Port Manager and select ports eth2 and eth3

2. Modify ports eth2 and eth3:

   1. In this example, eth2 and eth3 are physically connected with a patch cable

3. Configure each port with a valid IP address, then click OK

For more information see LANforge User's Guide: Ports (Interfaces)

Create the Armageddon cross-connect.

1. On the Armageddon tab, click the Create button

2. Select ports eth2 and eth3 and enter the speed and packet size

   1. For this example, 10000pps at 1514byte packet size should generate about 121Mbps

   2. Click OK when finished

3. Verify that the Armageddon connection is created

For more information see LANforge User's Guide: Armageddon (Accelerated UDP)

Run the Armageddon cross-connect and view results.

1. Select the Armageddon connection then click Start

2. It will take a moment for the Armageddon traffic to stabilize and depending on the hardware, LANforge will settle on an actual rate which may differ from the requested rate

3. In this example, this server (3.2GHz Xeon with 4-port 10/100/1000 PCI-X) is capable of reaching 81,000pps with 1514byte packets or, an equivalent speed of about 981Mbps bi-directional.

   1. NOTE: Delay for Armageddon connections is measured in microseconds and in this example, the server experiences about 2900us of delay when sending to itself.

For more information see LANforge User's Guide: Armageddon (Accelerated UDP)

Configure the physical interfaces.

1. Go to the Port Manager and select ports eth2 and eth3

2. Modify ports eth2 and eth3

   1. In this example, eth2 and eth3 are connected to another LANforge system running a WanLink so that the Armageddon traffic can be sniffed on the other machine's interface

3. Configure each port with a valid IP address, then click OK

   1. NOTE: Be sure that both ports are in Promiscuous mode by selecting the Set PROMISC and PROMISC checkboxes

For more information see LANforge User's Guide: Ports (Interfaces)

Create the Armageddon cross-connect.

1. On the Armageddon tab, click Create

2. Select ports eth2 and eth3 and enter the speed and packet size

3. Enter values for the Source and Destination MAC addresses and specify a MAC count

For more information see LANforge User's Guide: Armageddon (Accelerated UDP)

Run the Armageddon cross-connect and verify results with Wireshark.

1. Select the Armageddon connection then click Start

2. On the Port Mgr tab of the other LANforge system, select one of the physical interfaces in the Armageddon connection

3. Click Sniff Packets to launch Wireshark and begin sniffing traffic.

   1. Stop the Wireshark capture after a few seconds via the stop icon or pull-down menu (Capture>Stop)

4. Select several packets and note their MAC addresses

5. Verify that the MAC addresses for each packet are different

For more information see LANforge User's Guide: Armageddon (Accelerated UDP)

Create a Layer-3 connection.

For more information see Generating Traffic to a Switched Network

Modify the Layer-3 connection to add the script.

1. Highlight the Layer-3 connection and select Modify

2. Select the Script button on Endpoint A.

3. Select the Script Type, RFC-2544.

   1. Note: A default set of payload sizes are setup based on RFC-2544 but, can be changed by typing over the default values.

   2. Note: For Layer-3 UDP and TCP connections, 'payload size' refers to size of the payload being carried by the protocol and not the ethernet frame size.

Setup script options. For details refer to: LANforge User's Guide: Scripted Cross Connect

1. Select Symmetric for the script to run both endpoints for a bi-directional traffic test.

2. Set the Run and Pause Duration.

3. Note the total number of Script Iterations and Estimated Total Duration to help determine how long it will take to run this script.

4. Select OK to close the Add/Modify Script window.

5. The Script Type for Endpoint B is set to NONE because Endpoint A is controlling both ends of the connection in this symmetric script example.

6. Select OK to close the Create/Modify Cross Connect window.

Start the Scripted Layer-3 Cross Connect.

1. Highlight the Layer-3 connection and select Start.

2. A script report window will pop up and show the details of each iteration of the scripted connection as it is run.

3. At the conclusion of the script, the report window will display a summary of the entire scripted connection results. Full Script Report for this example:

   1. per iteration details

   2. raw CSV data for all iterations

   3. spreadsheet matrices for creating your own 3D graphs

   4. system information

Create an Armageddon connection.

For more information see Armageddon Testing (Accelerated UDP)

Modify the Armageddon connection to add the script.

1. Highlight the Armageddon connection and select Modify.

2. Select the Script button on Endpoint A.

3. Select the Script Type 'RFC-2544'.

   1. Note: A default set of payload sizes are setup based on RFC-2544 but, can be changed by typing over the default values.

   2. Note: For Armageddon UDP connections, 'payload size' refers to size of the ethernet frame size.

For more information see LANforge User's Guide: Scripted Armageddon Cross Connect

Setup script options.

1. Select Symmetric for the script to run both endpoints for a bi-directional traffic test.

2. Set the Run and Pause Duration, modify Rates and Payload Sizes as needed.

3. Note the total number of Script Iterations and Estimated Total Duration to help determine how long it will take to run this script.

4. Select OK to close the Add/Modify Script window.

5. The Script Type for Endpoint B is set to NONE because Endpoint A is controlling both ends of the connection in this symmetric script example.

6. Select OK to close the Create/Modify Cross Connect window.

For more information see LANforge User's Guide: Scripted Armageddon Cross Connect

Start the Scripted Armageddon Cross Connect.

1. Highlight the Armageddon connection and select Start.

2. A script report window will pop up and show the details of each iteration of the scripted connection as it is run.

3. At the conclusion of the script, the report window will display a summary of the entire scripted connection results.

   1. per iteration details

   2. raw CSV data for all iterations

   3. spreadsheet matrices for creating your own 3D graphs

   4. system information

   For more information see Full Script Report for this example.

Setup the LANforge ports so that they have valid IP addresses and IP masks.

1. Using the LANforge GUI, go to the Port Manager tab.

2. Assign IP addresses and masks to the two ports.

3. Verify the port configuration.

For more information see LANforge User's Guide: Ports (Interfaces)

Setup a Layer-3 Multi-Conn TCP connection.

1. Go to the Layer-3 tab, and select the Create button.

2. For Endpoint A, type in a name in the CX Name field, choose a CX Type of 'LANforge/TCP', choose the correct ports and set the Report Timer to '1000 ms'.

3. Set the Min Tx Rate and Max Tx Rate on both Endpoints A and B to '9.6Kbps'.

   1. NOTE: Higher speeds and/or bursty transmit rates will require more memory to process per connection.

4. Leave the Min Pkt Size and Max Pkt Size on both Endpoints A and B set to '1024B'.

   1. NOTE: Larger packet sizes will use more memory, smaller packet sizes will require more CPU processing time.

5. Leave the TCP Duration set to Forever, unless you want each of the multiple TCP connections to teardown and restart after a specified duration.

6. For Endpoint A, set the Multi-Conn to the desired number of multiple TCP connections.

   1. You can type in any value that your license allows here or choose one from the drop down box. The recommended approach is to create a new Multi-Conn connection for every 5000 connections.

7. For Endpoint B, set the Multi-Conn to one, then select OK to create the connection.

   1. Endpoint B is the 'server' side of the TCP connection, therefore it is only necessary to have one Multi-Conn setup on Endpoint B to reply to all of the Endpoint A TCP SYN packets when the 5000 connections are being established.

For more information see LANforge User's Guide: Creating & Modifying Cross Connects

Create 5 more Layer-3 Multi-Conn TCP connections.

1. On the Layer-3 tab, highlight the first connection created in the previous step and select Modify.

2. Select the Batch-Create button.

3. Set the Quantity to 5, and set Port Increment A and Port Increment B to 0

4. Select the Apply button.

5. Verify that six Multi-Conn TCP connections were created.

For more information see LANforge User's Guide: Layer-3 Endpoints (FIRE)

Run traffic and verify results.

1. Highlight all six connections.

2. Select the Start button

3. Go to the L3 Endps tab to verify that all 30,000 connections are running.

4. Or, go to the Port Mgr tab, and sniff one of the ports while the Multi-Conn TCP connections are running.

   1. NOTE: You will need a lot of memory to run a Wireshark capture on 30,000 connections. It is probably best to stop all connections, set up the Wireshark capture, start all connections and let them run for 30 seconds to 1 minute before stopping them all, then stop the Wireshark capture and wait for it to process all those packets!

5. After the Wireshark capture is complete, go to Statistics - Conversations to allow Wireshark to analyze the conversations and show that all 30,000 connections were captured. This will take some time to complete depending on the size of the capture.

For more information see LANforge User's Guide: Layer-3 Endpoints (FIRE)

Prep some ingredients.

1. Chop up some onions. One should be good enough.

2. Chop up some garlic. Just a few cloves.

Cook it all up

1. Brown some ground beef.

2. Heat up tomato sauce, kidney beans. 16oz of each is good.

3. Add garlic, onions, beef and spices such as cayenne, cumin, chili powder, salt and pepper.

4. Don't forget the beer!

   1. Note: The beer is for you, not the chili...unless of course you are experimenting!

5. Cornbread is also nice to have.

Enjoy!

1. Serve with additional chopped onions, corn chips and cheddar cheese.

Create the virtual wireless stations.
Note: All of its virtual stations will use the same wireless AP in this example, but each station may be configured for a different AP as long as all stations on the same radio use APs on the same channel.

1. Go to the Port Manager

2. Select port wiphy0 and click Create

3. Select the Wifi STA button, then enter MAC, Quantity, STA ID, and SSID. Select the DHCP-IPv4 checkbox:

   1. In this example, all 4 virtual stations will connect to the same access point

   2. If your access point can serve DHCP, you can select the 'DHCP-IPv4' checkbox here to enable each virtual station as a DHCP client

   3. If you choose to enter IP addresses manually, the create function will increment the last octet of the IP address for each virtual station created

   4. Click Apply when finished

4. Verify that the virtual wireless stations are created

5. Scroll to the right to view each station's link quality and other interface details

For more information see LANforge User's Guide: Ports (Interfaces)

Create Layer-3 connections between the station interfaces.

1. Go to the Layer-3 tab and click Create

2. Create a station-to-station UDP speed test:

   1. Test 1: sta0-sta1, UDP, 100Mbps ↔ 56Kbps

3. Create a station-to-station TCP speed test:

   1. Test 1: sta0-sta1, TCP, 1.54Mbps bi-directional traffic

For more information see LANforge User's Guide: Layer-3 Cross-Connects (FIRE)

Run traffic tests concurrently, and view results.

1. The AP in this example has a weak signal strength, so it can do only about 35Mbps total throughput. The round-trip-time (RTT) is reasonable, and there is very little packet loss.

2. The Layer-3 Endpoints tab has more detail.

3. Select the cross-connects or endpoints and Right-Click → Dynamic Report on the L3 Endp or Layer-3 table to view a live report of the connections.

For more information see LANforge User's Guide: Layer-3 Endpoints (FIRE)

Create a virtual AP on wiphy1.

1. Go to the Port Manager

2. Select port wiphy1 and click Create

3. Select the Wifi VAP button, then enter MAC, Quantity, STA ID, and SSID. Enter IPv4 address info:

4. Configure the radio's channel (which will apply to the VAP that was just created). Select the wiphy1 interface in the Port-Mgr tab and click Modify. Select the channel, and optionally the country-code, and then press Ok.

For more information see LANforge User's Guide: Ports (Interfaces)

Use the Netsmith feature to create a virtual router and configure DHCP for the AP.

1. Go to the Status tab, and click the Netsmith button for Resource 1.

2. Drag the existing interfaces into a more pleasing layout.

3. Right-Click in empty space and create a new Virtual Router. Just click OK, using the default configuration.

4. Drag the VAP interface into the virtual router and click Apply at the bottom-right of the Netsmith window..

5. Double-lick the vap0 icon (which should now be green) to bring up the Create/Modify Connection window.

6. Select the DHCP option, and then fill in the Range Min and Range Max values appropriately.

7. Apply Netsmith again and the configuration should be done.

Use Batch-Modify to configure all of the existing WiFi stations to talk to the new AP.

1. Go to the Port-Mgr tab, select sta0, sta1, sta2, and sta3, and then click the Batch Modify button. Configure the SSID to match the AP, and then press OK

2. The station interfaces should now get DHCP addresses matching the new AP

Create Layer-3 connections between the station interfaces.

1. Go to the Layer-3 tab. If there are existing connections, stop and/or delete them, and then click Create. Give the test a name, select sta0 and sta1 for ports, set rate to 100M, and set payload size. When complete, press Apply to create the new CX.

2. Create a second UDP connection on sta2 and sta3 interfaces. Change name, change ports, and press OK.

For more information see LANforge User's Guide: Layer-3 Cross-Connects (FIRE)

Run traffic tests concurrently, and view results.

1. Select both CXs in the Layer-3 tab, and click the Start button.

2. Go to the Port-Mgr tab, scroll to the right, and confirm that the Activity for this channel reports a fairly high percentage.

3. Select the 4 station ports and Right-Click → Dynamic Report on the Port-Mgr table to view a live report of the ports.

For more information see LANforge User's Guide: Reporting

Create a virtual AP on wiphy1.

1. Go to the Port Manager

2. Select port wiphy1 and click Create

3. Select the Wifi VAP button, then enter MAC, Quantity, STA ID, and SSID:

4. Configure the radio's channel (which will apply to the VAP that was just created). Select the wiphy1 interface in the Port-Mgr tab and click Modify. Select the channel, and optionally the country-code, and then press Ok.

For more information see LANforge User's Guide: Ports (Interfaces)

Use the Netsmith feature to create a bridge device to hold the VAP and the Ethernet Port.

1. Go to the Status tab, and click the Netsmith button for Resource 1.

2. Drag the existing interfaces into a more pleasing layout and click Apply

3. Right-Click in empty space and chose the New Bridge option.

4. Enter Quantity 1, and give it a name such as br0, and then click Apply

5. Click Refresh in the Netsmith window and the br0 interface should appear.

6. Right-click on the br0 interface and select Modify Port. Add vap0 and eth1 to the bridge, click Apply, and then Sync.

7. Go back to the Netsmith window, and you should see the br0 device connected to vap0 and eth1 with purple lines. If you do not, try clicking once on the br0 icon to force a re-draw. You now have a VAP in bridge mode. Connect the upstream network to eth1, and stations associated with vap0 will be able to communicate with that upstream network.

Test TCP upload throughput with one station (Open)

1. Go to the Port Manager, select the wlan0 interface on the second system, and click Modify. Set the SSID to match the VAP on system 1.

2. Go to Layer-3 tab and click Create to build a TCP connection. Select the Protocol, ports, rates, PDU sizes, Send & Receive buffer sizes.

3. Start the test by selecting the tcp-se row and click Start. Right-click and select Dynamic Report to get a real-time graph of the throughput. We see about 250Mbps of TCP throughput.

Test TCP upload throughput with one station (WPA2)

1. Modify the VAP to use WPA2 instead of being open. Go to Port-Mgr tab, select vap0, and click Modify

2. Configure wlan0 to use the same settings so it can connect to the VAP using WPA2 authentication.

3. Go to the Layer-3 tab, start the tcp-se connection, right-click and select Dynamic Report to get a real-time graph of the throughput. We see about 43Mbps of TCP throughput. LANforge currently does the WPA encryption in software on the CPU, so it is much slower than un-encrypted traffic.

Test TCP throughput with 50 stations (Open)

1. Go to the Port-Mgr tab, select the existing wlan0 and vap0 interfaces, click Modify, un-select WPA2 on each of them, and click Apply. This changes wlan0 and vap0 back to Open mode.

2. Go to the Port-Mgr tab, select the wiphy0 interface on the second system, and click Create. Select Wifi STA, enter starting MAC, quantity of 49, select DHCP-IPv4, STA ID of 0, SSID, and Key/Phrase. When properly configured, click Apply

3. You should now see all 50 stations associated with IP addresses.

4. Go to the Layer-3 tab, modify the 'tcp-se' connection. Change the name to tcp-se-0001, and change the RX Endpoint side's port from wlan0 to sta0. Click OK to create the new connection.

5. Now, create 48 more copies. Modify the tcp-se-0001 connection and click Batch-Create. Set quantity to 48, and Port Increment A to 0. Click Apply to create the 48 TCP connections, one on each of the 48 stations.

6. Select all of the tcp-se connections and click Start. Each of the connections are configured for higher rates than the network can actually handle. This is OK, but it will give un-even throughput results on different stations. So, you may wish to change the rate to something lower. If so, go to the L3 Endps tab, make sure all of the tcp-se endpoints are selected, and click Batch Modify. Select B Only since we want to just modify one side of the connection. Set Min Tx Rate to 5Mbps, and click Apply

7. Go back to the Layer-3 tab and view the running connections.

8. Determine total throughput: Select all of the running connections and then Right-Click and select Calculations. In this scenario, we see about 230Mbps of total TCP throughput.

Test TCP upload throughput with 50 stations (WPA2)

1. Modify the VAP and stations to use WPA2 instead of being open. Go to Port-Mgr tab, select vap0, and all of the stations and click Modify. Change WPA2 to be 'ON' and enter password in the Key/Phrase box. Leave all othe values set to 'NA' so they are not changed.

2. Go back to the Layer-3 tab, select all of the connections, and click Clear to clear the counters. Right-Click and select Calculations to view the totals. In this scenario, we see about 50Mbps of TCP throughput.

Test TCP upload throughput with 128 stations

1. Use similar steps to those described above to create 78 more stations. In the Create VLANs window, use STA ID of 49 and Quantity of 78 this time (since stations 0-48 have already been created). When creating more TCP connections, you can click Modify on the tcp-se-0049 connection and click Batch Create.

2. In this scenario, we see about 36Mbps throughput with TCP in WPA2 mode, and 28Mbps to 40Mbps in Open mode.