CDRouter Performance Test Summaries (Full)

Test Case Descriptions

Modules: 16
Test Cases: 1826

Below is a full description of the testcases in each module

`perf.tcl`

IPv4 performance tests

Test	Name	Synopsis
`IPv4 TCP download throughput test WAN to LAN`	`perf_1`	IPv4 TCP download throughput test WAN to LAN



    step 1. Start a performance client on the LAN.
    step 2. Verify connectivity between the LAN performance client and its
            Gateway (the DUT). If the testvar perfPingEnable is set to **yes**,
            measure and record the round trip time (RTT).
    step 3. Start a performance server on the WAN using the address/port
            specified by the testvar perfWanIp and perfPort.
    step 4. Run a TCP download performance test over IPv4 using the performance
            settings in the configuration file.
    step 5. Verify that the measured throughout performance falls between the
            configured high and low thresholds specified by the testvars
            perfDownloadTcpHighThreshold and perfDownloadTcpLowThreshold,
            respectively. Also verify that the number of TCP retransmits is
            less then the value specified for perfDownloadTcpRetr, if it is set.
    step 6. Shutdown the performance client and server. Verify connectivity
            between LAN and WAN.

Test	Name	Synopsis
`IPv4 TCP upload throughput test LAN to WAN`	`perf_2`	IPv4 TCP upload throughput test LAN to WAN



    step 1. Start a performance client on the LAN.
    step 2. Verify connectivity between the LAN performance client and its
            Gateway (the DUT). If the testvar perfPingEnable is set to **yes**,
            measure and record the round trip time (RTT).
    step 3. Start a performance server on the WAN using the address/port
            specified by the testvar perfWanIp and perfPort.
    step 4. Run a TCP upload performance test over IPv4 using the performance
            settings in the configuration file.
    step 5. Verify that the measured throughout performance falls between the
            configured high and low thresholds specified by the testvars
            perfUploadTcpHighThreshold and perfUploadTcpLowThreshold,
            respectively. Also verify that the number of TCP retransmits is
            less then the value specified for perfUploadTcpRetr, if it is set.
    step 6. Shutdown the performance client and server. Verify connectivity
            between LAN and WAN.

Test	Name	Synopsis
`IPv4 UDP download throughput test WAN to LAN`	`perf_3`	IPv4 UDP download throughput test WAN to LAN



    step 1. Start a performance client on the LAN.
    step 2. Verify connectivity between the LAN performance client and its
            Gateway (the DUT). If the testvar perfPingEnable is set to **yes**,
            measure and record the round trip time (RTT).
    step 3. Start a performance server on the WAN using the address/port
            specified by the testvar perfWanIp and perfPort.
    step 4. Run a UDP download performance test over IPv4 using the performance
            settings in the configuration file.
    step 5. Verify that the measured throughout performance falls between the
            configured high and low thresholds specified by the testvars
            perfDownloadUdpHighThreshold and perfDownloadUdpLowThreshold,
            respectively.
    step 6. Shutdown the performance client and server. Verify connectivity
            between LAN and WAN.

Test	Name	Synopsis
`IPv4 UDP upload throughput test LAN to WAN`	`perf_4`	IPv4 UDP upload throughput test LAN to WAN



    step 1. Start a performance client on the LAN.
    step 2. Verify connectivity between the LAN performance client and its
            Gateway (the DUT). If the testvar perfPingEnable is set to **yes**,
            measure and record the round trip time (RTT).
    step 3. Start a performance server on the WAN using the address/port
            specified by the testvar perfWanIp and perfPort.
    step 4. Run a UDP upload performance test over IPv4 using the performance
            settings in the configuration file.
    step 5. Verify that the measured throughout performance falls between the
            configured high and low thresholds specified by the testvars
            perfUploadUdpHighThreshold and perfUploadUdpLowThreshold,
            respectively.
    step 6. Shutdown the performance client and server. Verify connectivity
            between LAN and WAN.

Test	Name	Synopsis
`IPv4 TCP bidirectional throughput test`	`perf_5`	IPv4 TCP bidirectional throughput test



    step 1. Start a performance client on the LAN.
    step 2. Verify connectivity between the LAN performance client and its
            Gateway (the DUT). If the testvar perfPingEnable is set to **yes**,
            measure and record the round trip time (RTT).
    step 3. Start a performance servers on the WAN using the address/ports
            specified by the testvar perfWanIp, perfPort, and perfPort2.
    step 4. Run a TCP bidirectional performance test over IPv4 using the
            performance settings in the configuration file.
    step 5. Verify that the measured performance falls between the configured
            high and low thresholds specified by the testvars
            perfDownloadTcpHighThreshold, perfDownloadTcpLowThreshold,
            perfUploadTcpHighThreshold, and perfUploadTcpLowThreshold,
            respectively. Also verify that the number of TCP retransmits is
            less then the value specified for both perfDownloadTcpRetr and
            perfUploadTcpRetr, if they are set.
    step 6. Shutdown the performance client and server. Verify connectivity
            between LAN and WAN.

Test	Name	Synopsis
`IPv4 UDP bidirectional throughput test`	`perf_6`	IPv4 UDP bidirectional throughput test



    step 1. Start a performance client on the LAN.
    step 2. Verify connectivity between the LAN performance client and its
            Gateway (the DUT). If the testvar perfPingEnable is set to **yes**,
            measure and record the round trip time (RTT).
    step 3. Start a performance servers on the WAN using the address/ports
            specified by the testvar perfWanIp, perfPort, and perfPort2.
    step 4. Run a TCP bidirectional performance test over IPv4 using the
            performance settings in the configuration file.
    step 5. Verify that the measured performance falls between the configured
            high and low thresholds specified by the testvars
            perfDownloadUdpHighThreshold, perfDownloadUdpLowThreshold,
            perfUploadUdpHighThreshold, and perfUploadUdpLowThreshold,
            respectively.
    step 6. Shutdown the performance client and server. Verify connectivity
            between LAN and WAN.

Test	Name	Synopsis
`IPv4 UDP download loss threshold test WAN to LAN`	`perf_7`	IPv4 UDP download loss threshold test WAN to LAN



    This test is designed to find the maximum UDP download bandwidth
    that results in the target loss specified by the testvar
    perfDownloadUdpLossPercentage.

    step 1. Start a performance client on the LAN. If the LAN interface is
            wireless, the wireless interface and existing LAN client will be
            restarted and used. If the LAN interface is ethernet a new LAN
            client will be created and used.
    step 2. Verify connectivity between the LAN performance client and its
            Gateway (the DUT).
    step 3. Start a performance server on the WAN using the address specified
            by the testvar perfWanIp.
    step 4. Run a download loss threshold performance test over IPv4 using the
            performance settings in the configuration file.
    step 5. Verify that the measured loss percentage does not exceed the value
            specified by the testvar perfDownloadUdpLossPercentage.
    step 6. Shutdown the performance client and server. If the LAN interface is
            wireless, restart the wireless interface and LAN client.

Test	Name	Synopsis
`IPv4 UDP upload loss threshold test LAN to WAN`	`perf_8`	IPv4 UDP upload loss threshold test LAN to WAN



    This test is designed to find the maximum UDP upload bandwidth
    that results in the target loss specified by the testvar
    perfUploadUdpLossPercentage.

    step 1. Start a performance client on the LAN. If the LAN interface is
            wireless, the wireless interface and existing LAN client will be
            restarted and used. If the LAN interface is ethernet a new LAN
            client will be created and used.
    step 2. Verify connectivity between the LAN performance client and its
            Gateway (the DUT).
    step 3. Start a performance server on the WAN using the address specified
            by the testvar perfWanIp.
    step 4. Run a upload loss threshold performance test over IPv4 using the
            performance settings in the configuration file.
    step 5. Verify that the measured loss percentage does not exceed the value
            specified by the testvar perfUploadUdpLossPercentage.
    step 6. Shutdown the performance client and server. If the LAN interface is
            wireless, restart the wireless interface and LAN client.

Test	Name	Synopsis
`IPv4 bidirectional latency test`	`perf_9`	IPv4 bidirectional latency test



    step 1. Start a performance client on the LAN. The existing LAN client
            will be used, regardless if the LAN interface is wired or
            wireless.
    step 2. Start a performance server by using the exsiting WAN client.
            The server port to send/receive traffic is defined by
            the tesevar defaultUdpEchoPort.
    step 3. Run a bidirectional latency performance test over IPv4 using the
            performance settings in the configuration file.
    step 4. Verify that the measured latencies do not exceed the values
            specified by the testvars perfDownloadMaxLatency and
            perfUploadMaxLatency.
    step 5. Shutdown the performance client and server.

Test	Name	Synopsis
`IPv4 DHCP renew latency test`	`perf_10`	IPv4 DHCP renew latency test



    step 1. Start a DHCP renew from the LAN.
    step 2. Measure the round trip latency of the DHCP response.
    step 3. Make multiple DHCP renew attempts and compute average latency.
    step 4. Verify that the measured latency does not exceed the value
            specified by the testvars perfDHCPRenewLatency.

Test	Name	Synopsis
`IPv4 DHCP restart latency test`	`perf_11`	IPv4 DHCP restart latency test



    step 1. Restart the DHCP client from the LAN.
    step 2. Measure the round trip latency of the DHCP response.
    step 3. Make multiple DHCP restart attempts and compute average latency.
    step 4. Verify that the measured latency does not exceed the value
            specified by the testvars perfDHCPRestartMaxLatency.

Test	Name	Synopsis
`IPv4 DNS query latency test`	`perf_12`	IPv4 DNS query latency test



    step 1. Start a DNS query from the LAN.
    step 2. Measure the round trip latency of the DNS response.
    step 3. Make multiple DNS queries to compute average latency.
    step 4. Verify that the measured latency does not exceed the value
            specified by the testvars perfDNSLatency.

`perf-v6.tcl`

IPv6 performance tests

Test	Name	Synopsis
`IPv6 TCP download throughput test WAN to LAN`	`ipv6_perf_1`	IPv6 TCP download throughput test WAN to LAN



    step 1. Start a performance client on the LAN.
    step 2. Verify connectivity between the LAN performance client and its
            Gateway (the DUT). If the testvar perfPingEnable is set to **yes**,
            measure and record the round trip time (RTT).
    step 3. Start a performance server on the WAN using the address/port
            specified by the testvar perfWanIpv6 and perfPort.
    step 4. Run a TCP download performance test over IPv6 using the performance
            settings in the configuration file.
    step 5. Verify that the measured throughout performance falls between the
            configured high and low thresholds specified by the testvars
            perfDownloadTcpHighThreshold and perfDownloadTcpLowThreshold,
            respectively.Also verify that the number of TCP retransmits is
            less then the value specified for perfDownloadTcpRetr, if it is set.
    step 6. Shutdown the performance client and server. Verify connectivity
            between LAN and WAN.

Test	Name	Synopsis
`IPv6 TCP upload throughput test LAN to WAN`	`ipv6_perf_2`	IPv6 TCP upload throughput test LAN to WAN



    step 1. Start a performance client on the LAN.
    step 2. Verify connectivity between the LAN performance client and its
            Gateway (the DUT). If the testvar perfPingEnable is set to **yes**,
            measure and record the round trip time (RTT).
    step 3. Start a performance server on the WAN using the address/port
            specified by the testvar perfWanIpiv6 and perfPort.
    step 4. Run a TCP download performance test over IPv6 using the performance
            settings in the configuration file.
    step 5. Verify that the measured throughout performance falls between the
            configured high and low thresholds specified by the testvars
            perfUploadTcpHighThreshold and perfUploadTcpLowThreshold,
            respectively. Also verify that the number of TCP retransmits is
            less then the value specified for perfUploadTcpRetr, if it is set.
    step 6. Shutdown the performance client and server. Verify connectivity
            between LAN and WAN.

Test	Name	Synopsis
`IPv6 UDP download throughput test WAN to LAN`	`ipv6_perf_3`	IPv6 UDP download throughput test WAN to LAN



    step 1. Start a performance client on the LAN.
    step 2. Verify connectivity between the LAN performance client and its
            Gateway (the DUT). If the testvar perfPingEnable is set to **yes**,
            measure and record the round trip time (RTT).
    step 3. Start a performance server on the WAN using the address/port
            specified by the testvar perfWanIav6p and perfPort.
    step 4. Run a TCP download performance test over IPv6 using the performance
            settings in the configuration file.
    step 5. Verify that the measured throughout performance falls between the
            configured high and low thresholds specified by the testvars
            perfDownloadUdpHighThreshold and perfDownloadUdpLowThreshold,
            respectively.
    step 6. Shutdown the performance client and server. Verify connectivity
            between LAN and WAN.

Test	Name	Synopsis
`IPv6 UDP upload throughput test LAN to WAN`	`ipv6_perf_4`	IPv6 UDP upload throughput test LAN to WAN



    step 1. Start a performance client on the LAN.
    step 2. Verify connectivity between the LAN performance client and its
            Gateway (the DUT). If the testvar perfPingEnable is set to **yes**,
            measure and record the round trip time (RTT).
    step 3. Start a performance server on the WAN using the address/port
            specified by the testvar perfWanIpv6 and perfPort.
    step 4. Run a TCP download performance test over IPv6 using the performance
            settings in the configuration file.
    step 5. Verify that the measured throughout performance falls between the
            configured high and low thresholds specified by the testvars
            perfUploadUdpHighThreshold and perfUploadUdpLowThreshold,
            respectively.
    step 6. Shutdown the performance client and server. Verify connectivity
            between LAN and WAN.

Test	Name	Synopsis
`IPv6 TCP bidirectional throughput test`	`ipv6_perf_5`	IPv6 TCP bidirectional throughput test



    step 1. Start a performance client on the LAN.
    step 2. Verify connectivity between the LAN performance client and its
            Gateway (the DUT). If the testvar perfPingEnable is set to **yes**,
            measure and record the round trip time (RTT).
    step 3. Start a performance servers on the WAN using the address/ports
            specified by the testvar perfWanIpv6, perfPort, and perfPort2.
    step 4. Run a TCP bidirectional performance test over IPv6 using the
            performance settings in the configuration file.
    step 5. Verify that the measured performance falls between the configured
            high and low thresholds specified by the testvars
            perfDownloadTcpHighThreshold, perfDownloadTcpLowThreshold,
            perfUploadTcpHighThreshold, and perfUploadTcpLowThreshold,
            respectively. Also verify that the number of TCP retransmits is
            less then the value specified for both perfDownloadTcpRetr and
            perfUploadTcpRetr, if they are set.
    step 6. Shutdown the performance client and server. Verify connectivity
            between LAN and WAN.

Test	Name	Synopsis
`IPv6 UDP bidirectional throughput test`	`ipv6_perf_6`	IPv6 UDP bidirectional throughput test



    step 1. Start a performance client on the LAN.
    step 2. Verify connectivity between the LAN performance client and its
            Gateway (the DUT). If the testvar perfPingEnable is set to **yes**,
            measure and record the round trip time (RTT).
    step 3. Start a performance servers on the WAN using the address/ports
            specified by the testvar perfWanIpv6, perfPort, and perfPort2.
    step 4. Run a TCP bidirectional performance test over IPv6 using the
            performance settings in the configuration file.
    step 5. Verify that the measured performance falls between the configured
            high and low thresholds specified by the testvars
            perfDownloadUdpHighThreshold, perfDownloadUdpLowThreshold,
            perfUploadUdpHighThreshold, and perfUploadUdpLowThreshold,
            respectively.
    step 6. Shutdown the performance client and server. Verify connectivity
            between LAN and WAN.

Test	Name	Synopsis
`IPv6 UDP download loss threshold test WAN to LAN`	`ipv6_perf_7`	IPv6 UDP download loss threshold test WAN to LAN



    This test is designed to find the maximum UDP download bandwidth
    that results in the target loss specified by the testvar
    perfDownloadUdpLossPercentage.

    step 1. Start a performance client on the LAN. If the LAN interface is
            wireless, the wireless interface and existing LAN client will be
            restarted and used. If the LAN interface is ethernet a new LAN
            client will be created and used.
    step 2. Verify connectivity between the LAN performance client and its
            Gateway (the DUT).
    step 3. Start a performance server on the WAN using the address specified
            by the testvar perfWanIpv6.
    step 4. Run a download loss threshold performance test over IPv6 using the
            performance settings in the configuration file. 
    step 5. Verify that the measured loss percentage does not exceed the value
            specified by the testvar perfDownloadUdpLossPercentage.
    step 6. Shutdown the performance client and server. If the LAN interface is
            wireless, restart the wireless interface and LAN client.

Test	Name	Synopsis
`IPv6 UDP upload loss threshold test LAN to WAN`	`ipv6_perf_8`	IPv6 UDP upload loss threshold test LAN to WAN



    This test is designed to find the maximum UDP upload bandwidth
    that results in the target loss specified by the testvar
    perfUploadUdpLossPercentage.

    step 1. Start a performance client on the LAN. If the LAN interface is
            wireless, the wireless interface and existing LAN client will be
            restarted and used. If the LAN interface is ethernet a new LAN
            client will be created and used.
    step 2. Verify connectivity between the LAN performance client and its
            Gateway (the DUT).
    step 3. Start a performance server on the WAN using the address specified
            by the testvar perfWanIpv6.
    step 4. Run a upload loss threshold performance test over IPv6 using the
            performance settings in the configuration file. 
    step 5. Verify that the measured loss percentage does not exceed the value
            specified by the testvar perfUploadUdpLossPercentage.
    step 6. Shutdown the performance client and server. If the LAN interface is
            wireless, restart the wireless interface and LAN client.

Test	Name	Synopsis
`IPv6 bidirectional latency test`	`ipv6_perf_9`	IPv6 bidirectional latency test



    step 1. Start a performance client on the LAN. The existing LAN client
            will be used, regardless if the LAN interface is wired or
            wireless.
    step 2. Start a performance server by using the exsiting WAN client.
            The server port to send/receive traffic is defined by
            the tesevar defaultUdpEchoPort.
    step 3. Run a bidirectional latency performance test over IPv6 using the
            performance settings in the configuration file.
    step 4. Verify that the measured latencies do not exceed the values
            specified by the testvars perfDownloadMaxLatency and
            perfUploadMaxLatency.
    step 5. Shutdown the performance client and server.

Test	Name	Synopsis
`IPv6 DHCPv6 renew latency test`	`ipv6_perf_10`	IPv6 DHCPv6 renew latency test



    step 1. Start a DHCPv6 renew from the LAN.
    step 2. Measure the round trip latency of the DHCPv6 response.
    step 3. Make multiple DHCPv6 renew attempts and compute average latency.
    step 4. Verify that the measured latency does not exceed the value
            specified by the testvars perfDHCPRenewLatency.

Test	Name	Synopsis
`IPv6 DHCPv6 restart latency test`	`ipv6_perf_11`	IPv6 DHCPv6 restart latency test



    step 1. Restart the DHCPv6 client from the LAN.
    step 2. Measure the round trip latency of the DHCPv6 response.
    step 3. Make multiple DHCPv6 restart attempts and compute average latency.
    step 4. Verify that the measured latency does not exceed the value
            specified by the testvars perfDHCPRestartMaxLatency.

Test	Name	Synopsis
`IPv6 DNS query latency test`	`ipv6_perf_12`	IPv6 DNS query latency test



    step 1. Start a DNS query from the LAN.
    step 2. Measure the round trip latency of the DNS response.
    step 3. Make multiple DNS queries to compute average latency.
    step 4. Verify that the measured latency does not exceed the value
            specified by the testvars perfDNSLatency.

`perf-lan.tcl`

IPv4 LAN to LAN performance tests

Test	Name	Synopsis
`IPv4 TCP 'download' throughput test LAN to LAN`	`perf_lan_1`	IPv4 TCP ‘download’ throughput test LAN to LAN



    step 1. Start a performance client on the LAN.
    step 2. Verify connectivity between the LAN performance client and its
            Gateway (the DUT). If the testvar perfPingEnable is set to **yes**,
            measure and record the round trip time (RTT).
    step 3. Start a performance server on a second LAN using the port
            specified by the testvar perfPort.
    step 4. Run a TCP download performance test over IPv4 using the performance
            settings in the configuration file.
    step 5. Verify that the measured throughout performance falls between the
            configured high and low thresholds specified by the testvars
            perfLantoLanTcpHighThreshold and perfLantoLanTcpLowThreshold,
            respectively. Also verify that the number of TCP retransmits is
            less then the value specified for perfLantoLanTcpRetr, if it is set.
    step 6. Shutdown the performance client and server. Verify connectivity
            between LAN and WAN.

Test	Name	Synopsis
`IPv4 TCP 'upload' throughput test LAN to LAN`	`perf_lan_2`	IPv4 TCP ‘upload’ throughput test LAN to LAN



    step 1. Start a performance client on the LAN.
    step 2. Verify connectivity between the LAN performance client and its
            Gateway (the DUT). If the testvar perfPingEnable is set to **yes**,
            measure and record the round trip time (RTT).
    step 3. Start a performance server on a second LAN using the port
            specified by the testvar perfPort.
    step 4. Run a TCP upload performance test over IPv4 using the performance
            settings in the configuration file.
    step 5. Verify that the measured throughout performance falls between the
            configured high and low thresholds specified by the testvars
            perfLantoLanTcpHighThreshold and perfLantoLanTcpLowThreshold,
            respectively. Also verify that the number of TCP retransmits is
            less then the value specified for perfLantoLanTcpRetr, if it is set.
    step 6. Shutdown the performance client and server. Verify connectivity
            between LAN and WAN.

Test	Name	Synopsis
`IPv4 UDP 'download' throughput test LAN to LAN`	`perf_lan_3`	IPv4 UDP ‘download’ throughput test LAN to LAN



    step 1. Start a performance client on the LAN.
    step 2. Verify connectivity between the LAN performance client and its
            Gateway (the DUT). If the testvar perfPingEnable is set to **yes**,
            measure and record the round trip time (RTT).
    step 3. Start a performance server on a second LAN using the port
            specified by the testvar perfPort.
    step 4. Run a UDP download performance test over IPv4 using the performance
            settings in the configuration file.
    step 5. Verify that the measured throughout performance falls between the
            configured high and low thresholds specified by the testvars
            perfLantoLanUdpHighThreshold and perfLantoLanUdpLowThreshold,
            respectively.
    step 6. Shutdown the performance client and server. Verify connectivity
            between LAN and WAN.

Test	Name	Synopsis
`IPv4 UDP 'upload' throughput test LAN to LAN`	`perf_lan_4`	IPv4 UDP ‘upload’ throughput test LAN to LAN



    step 1. Start a performance client on the LAN.
    step 2. Verify connectivity between the LAN performance client and its
            Gateway (the DUT). If the testvar perfPingEnable is set to **yes**,
            measure and record the round trip time (RTT).
    step 3. Start a performance server on a second LAN using the port
            specified by the testvar perfPort.
    step 4. Run a UDP upload performance test over IPv4 using the performance
            settings in the configuration file.
    step 5. Verify that the measured throughout performance falls between the
            configured high and low thresholds specified by the testvars
            perfLantoLanUdpHighThreshold and perfLantoLanUdpLowThreshold,
            respectively.
    step 6. Shutdown the performance client and server. Verify connectivity
            between LAN and WAN.

Test	Name	Synopsis
`IPv4 TCP bidirectional throughput test LAN to LAN`	`perf_lan_5`	IPv4 TCP bidirectional throughput test LAN to LAN



    step 1. Start a performance client on the LAN.
    step 2. Verify connectivity between the LAN performance client and its
            Gateway (the DUT). If the testvar perfPingEnable is set to **yes**,
            measure and record the round trip time (RTT).
    step 3. Start a performance servers on a second LAN using the ports
            specified by the testvar perfPort and perfPort2.
    step 4. Run a TCP bidirectional performance test over IPv4 using the
            performance settings in the configuration file.
    step 5. Verify that the measured performance falls between the configured
            high and low thresholds specified by the testvars
            perfLantoLanTcpHighThreshold, perfLantoLanTcpLowThreshold,
            perfLantoLanTcpHighThreshold, and perfLantoLanTcpLowThreshold,
            respectively. Also verify that the number of TCP retransmits is
            less then the value specified for both perfLantoLanTcpRetr and
            perfLantoLanTcpRetr, if they are set.
    step 6. Shutdown the performance client and server. Verify connectivity
            between LAN and WAN.

Test	Name	Synopsis
`IPv4 UDP bidirectional throughput test LAN to LAN`	`perf_lan_6`	IPv4 UDP bidirectional throughput test LAN to LAN



    step 1. Start a performance client on the LAN.
    step 2. Verify connectivity between the LAN performance client and its
            Gateway (the DUT). If the testvar perfPingEnable is set to **yes**,
            measure and record the round trip time (RTT).
    step 3. Start a performance servers on a second LAN using the ports
            specified by the testvar perfPort and perfPort2.
    step 4. Run a TCP bidirectional performance test over IPv4 using the
            performance settings in the configuration file.
    step 5. Verify that the measured performance falls between the configured
            high and low thresholds specified by the testvars
            perfLantoLanUdpHighThreshold, perfLantoLanUdpLowThreshold,
            perfLantoLanUdpHighThreshold, and perfLantoLanUdpLowThreshold,
            respectively.
    step 6. Shutdown the performance client and server. Verify connectivity
            between LAN and WAN.

Test	Name	Synopsis
`IPv4 UDP 'download' loss threshold test LAN to LAN`	`perf_lan_7`	IPv4 UDP ‘download’ loss threshold test LAN to LAN



    This test is designed to find the maximum UDP download bandwidth
    that results in the target loss specified by the testvar
    perfLantoLanUdpLossPercentage.

    step 1. Start a performance client on the LAN.
    step 2. Verify connectivity between the LAN performance client and its
            Gateway (the DUT).
    step 3. Start a performance server on a second LAN.
    step 4. Run a download loss threshold performance test over IPv4 using the
            performance settings in the configuration file.
    step 5. Verify that the measured loss percentage does not exceed the value
            specified by the testvar perfLantoLanUdpLossPercentage.
    step 6. Shutdown the performance client and server.

Test	Name	Synopsis
`IPv4 UDP 'upload' loss threshold LAN to LAN`	`perf_lan_8`	IPv4 UDP ‘upload’ loss threshold LAN to LAN



    This test is designed to find the maximum UDP upload bandwidth
    that results in the target loss specified by the testvar
    perfLantoLanUdpLossPercentage.

    step 1. Start a performance client on the LAN.
    step 2. Verify connectivity between the LAN performance client and its
            Gateway (the DUT).
    step 3. Start a performance server on a second LAN.
    step 4. Run a upload loss threshold performance test over IPv4 using the
            performance settings in the configuration file.
    step 5. Verify that the measured loss percentage does not exceed the value
            specified by the testvar perfLantoLanUdpLossPercentage.
    step 6. Shutdown the performance client and server.

Test	Name	Synopsis
`IPv4 bidirectional latency test LAN to LAN`	`perf_lan_9`	IPv4 bidirectional latency test LAN to LAN



    step 1. Start a performance client on the LAN.
    step 2. Start a performance server by using the exsiting LAN client.
            The server port to send/receive traffic is defined by
            the tesevar defaultUdpEchoPort.
    step 3. Run a bidirectional latency performance test over IPv4 using the
            performance settings in the configuration file.
    step 4. Verify that the measured latencies do not exceed the values
            specified by the testvars perfLantoLanMaxLatency and
            perfLantoLanMaxLatency.
    step 5. Shutdown the performance client and server.

`perf-lan-v6.tcl`

IPv6 LAN to LAN performance tests

Test	Name	Synopsis
`IPv6 TCP 'download' throughput test LAN to LAN`	`ipv6_perf_lan_1`	IPv6 TCP ‘download’ throughput test LAN to LAN



    step 1. Start a performance client on the LAN.
    step 2. Verify connectivity between the LAN performance client and its
            Gateway (the DUT). If the testvar perfPingEnable is set to **yes**,
            measure and record the round trip time (RTT).
    step 3. Start a performance server on a second LAN using the port
            specified by the testvar perfPort.
    step 4. Run a TCP download performance test over IPv6 using the performance
            settings in the configuration file.
    step 5. Verify that the measured throughout performance falls between the
            configured high and low thresholds specified by the testvars
            perfLantoLanTcpHighThreshold and perfLantoLanTcpLowThreshold,
            respectively. Also verify that the number of TCP retransmits is
            less then the value specified for perfLantoLanTcpRetr, if it is set.
    step 6. Shutdown the performance client and server. Verify connectivity
            between LAN and WAN.

Test	Name	Synopsis
`IPv6 TCP 'upload' throughput test LAN to LAN`	`ipv6_perf_lan_2`	IPv6 TCP ‘upload’ throughput test LAN to LAN



    step 1. Start a performance client on the LAN.
    step 2. Verify connectivity between the LAN performance client and its
            Gateway (the DUT). If the testvar perfPingEnable is set to **yes**,
            measure and record the round trip time (RTT).
    step 3. Start a performance server on a second LAN using the port
            specified by the testvar perfPort.
    step 4. Run a TCP upload performance test over IPv6 using the performance
            settings in the configuration file.
    step 5. Verify that the measured throughout performance falls between the
            configured high and low thresholds specified by the testvars
            perfLantoLanTcpHighThreshold and perfLantoLanTcpLowThreshold,
            respectively. Also verify that the number of TCP retransmits is
            less then the value specified for perfLantoLanTcpRetr, if it is set.
    step 6. Shutdown the performance client and server. Verify connectivity
            between LAN and WAN.

Test	Name	Synopsis
`IPv6 UDP 'download' throughput test LAN to LAN`	`ipv6_perf_lan_3`	IPv6 UDP ‘download’ throughput test LAN to LAN



    step 1. Start a performance client on the LAN.
    step 2. Verify connectivity between the LAN performance client and its
            Gateway (the DUT). If the testvar perfPingEnable is set to **yes**,
            measure and record the round trip time (RTT).
    step 3. Start a performance server on a second LAN using the port
            specified by the testvar perfPort.
    step 4. Run a UDP download performance test over IPv6 using the performance
            settings in the configuration file.
    step 5. Verify that the measured throughout performance falls between the
            configured high and low thresholds specified by the testvars
            perfLantoLanUdpHighThreshold and perfLantoLanUdpLowThreshold,
            respectively.
    step 6. Shutdown the performance client and server. Verify connectivity
            between LAN and WAN.

Test	Name	Synopsis
`IPv6 UDP 'upload' throughput test LAN to LAN`	`ipv6_perf_lan_4`	IPv6 UDP ‘upload’ throughput test LAN to LAN



    step 1. Start a performance client on the LAN.
    step 2. Verify connectivity between the LAN performance client and its
            Gateway (the DUT). If the testvar perfPingEnable is set to **yes**,
            measure and record the round trip time (RTT).
    step 3. Start a performance server on a second LAN using the port
            specified by the testvar perfPort.
    step 4. Run a UDP upload performance test over IPv6 using the performance
            settings in the configuration file.
    step 5. Verify that the measured throughout performance falls between the
            configured high and low thresholds specified by the testvars
            perfLantoLanUdpHighThreshold and perfLantoLanUdpLowThreshold,
            respectively.
    step 6. Shutdown the performance client and server. Verify connectivity
            between LAN and WAN.

Test	Name	Synopsis
`IPv6 TCP bidirectional throughput test LAN to LAN`	`ipv6_perf_lan_5`	IPv6 TCP bidirectional throughput test LAN to LAN



    step 1. Start a performance client on the LAN.
    step 2. Verify connectivity between the LAN performance client and its
            Gateway (the DUT). If the testvar perfPingEnable is set to **yes**,
            measure and record the round trip time (RTT).
    step 3. Start a performance servers on a second LAN using the ports
            specified by the testvar perfPort and perfPort2.
    step 4. Run a TCP bidirectional performance test over IPv6 using the
            performance settings in the configuration file.
    step 5. Verify that the measured performance falls between the configured
            high and low thresholds specified by the testvars
            perfLantoLanTcpHighThreshold, perfLantoLanTcpLowThreshold,
            perfLantoLanTcpHighThreshold, and perfLantoLanTcpLowThreshold,
            respectively. Also verify that the number of TCP retransmits is
            less then the value specified for both perfLantoLanTcpRetr and
            perfLantoLanTcpRetr, if they are set.
    step 6. Shutdown the performance client and server. Verify connectivity
            between LAN and WAN.

Test	Name	Synopsis
`IPv6 UDP bidirectional throughput test LAN to LAN`	`ipv6_perf_lan_6`	IPv6 UDP bidirectional throughput test LAN to LAN



    step 1. Start a performance client on the LAN.
    step 2. Verify connectivity between the LAN performance client and its
            Gateway (the DUT). If the testvar perfPingEnable is set to **yes**,
            measure and record the round trip time (RTT).
    step 3. Start a performance servers on a second LAN using the ports
            specified by the testvar perfPort and perfPort2.
    step 4. Run a TCP bidirectional performance test over IPv6 using the
            performance settings in the configuration file.
    step 5. Verify that the measured performance falls between the configured
            high and low thresholds specified by the testvars
            perfLantoLanUdpHighThreshold, perfLantoLanUdpLowThreshold,
            perfLantoLanUdpHighThreshold, and perfLantoLanUdpLowThreshold,
            respectively.
    step 6. Shutdown the performance client and server. Verify connectivity
            between LAN and WAN.

Test	Name	Synopsis
`IPv6 UDP 'download' loss threshold test LAN to LAN`	`ipv6_perf_lan_7`	IPv6 UDP ‘download’ loss threshold test LAN to LAN



    This test is designed to find the maximum UDP download bandwidth
    that results in the target loss specified by the testvar
    perfLantoLanUdpLossPercentage.

    step 1. Start a performance client on the LAN. If the LAN interface is
            wireless, the wireless interface and existing LAN client will be
            restarted and used. If the LAN interface is ethernet a new LAN
            client will be created and used.
    step 2. Verify connectivity between the LAN performance client and its
            Gateway (the DUT).
    step 3. Start a performance server on a second LAN.
    step 4. Run a download loss threshold performance test over IPv6 using the
            performance settings in the configuration file. 
    step 5. Verify that the measured loss percentage does not exceed the value
            specified by the testvar perfLantoLanUdpLossPercentage.
    step 6. Shutdown the performance client and server. If the LAN interface is
            wireless, restart the wireless interface and LAN client.

Test	Name	Synopsis
`IPv6 UDP 'upload' loss threshold test LAN to LAN`	`ipv6_perf_lan_8`	IPv6 UDP ‘upload’ loss threshold test LAN to LAN



    This test is designed to find the maximum UDP upload bandwidth
    that results in the target loss specified by the testvar
    perfLantoLanUdpLossPercentage.

    step 1. Start a performance client on the LAN. If the LAN interface is
            wireless, the wireless interface and existing LAN client will be
            restarted and used. If the LAN interface is ethernet a new LAN
            client will be created and used.
    step 2. Verify connectivity between the LAN performance client and its
            Gateway (the DUT).
    step 3. Start a performance server on a second LAN.
    step 4. Run a upload loss threshold performance test over IPv6 using the
            performance settings in the configuration file. 
    step 5. Verify that the measured loss percentage does not exceed the value
            specified by the testvar perfLantoLanUdpLossPercentage.
    step 6. Shutdown the performance client and server. If the LAN interface is
            wireless, restart the wireless interface and LAN client.

Test	Name	Synopsis
`IPv6 bidirectional latency test LAN to LAN`	`ipv6_perf_lan_9`	IPv6 bidirectional latency test LAN to LAN



    step 1. Start a performance client on the LAN. The existing LAN client
            will be used, regardless if the LAN interface is wired or
            wireless.
    step 2. Start a performance server by using the exsiting LAN client.
            The server port to send/receive traffic is defined by
            the tesevar defaultUdpEchoPort.
    step 3. Run a bidirectional latency performance test over IPv6 using the
            performance settings in the configuration file.
    step 4. Verify that the measured latencies do not exceed the values
            specified by the testvars perfLantoLanMaxLatency and
            perfLantoLanMaxLatency.
    step 5. Shutdown the performance client and server.

`perf-mcast.tcl`

IPv4 multicast performance tests

Test	Name	Synopsis
`IPv4 Multicast UDP download throughput test WAN to LAN`	`perf_mcast_1`	IPv4 Multicast UDP download throughput test WAN to LAN



    step 1. Start a performance client on the LAN.
    step 2. Verify connectivity between the LAN performance client and its
            Gateway (the DUT). If the testvar perfPingEnable is set to **yes**,
            measure and record the round trip time (RTT).
    step 3. Start a performance server on the WAN using the address/port
            specified by the testvar perfWanIp and perfPort.
    step 4. Run a UDP download performance test over IPv4 using the performance
            settings in the configuration file.
    step 5. Verify that the measured throughout performance falls between the
            configured high and low thresholds specified by the testvars
            perfDownloadUdpHighThreshold and perfDownloadUdpLowThreshold,
            respectively.
    step 6. Shutdown the performance client and server. Verify connectivity
            between LAN and WAN.

Test	Name	Synopsis
`IPv4 Multicast UDP upload throughput test LAN to WAN`	`perf_mcast_2`	IPv4 Multicast UDP upload throughput test LAN to WAN



    step 1. Start a performance client on the LAN.
    step 2. Verify connectivity between the LAN performance client and its
            Gateway (the DUT). If the testvar perfPingEnable is set to **yes**,
            measure and record the round trip time (RTT).
    step 3. Start a performance server on the WAN using the address/port
            specified by the testvar perfWanIp and perfPort.
    step 4. Run a UDP upload performance test over IPv4 using the performance
            settings in the configuration file.
    step 5. Verify that the measured throughout performance falls between the
            configured high and low thresholds specified by the testvars
            perfUploadUdpHighThreshold and perfUploadUdpLowThreshold,
            respectively.
    step 6. Shutdown the performance client and server. Verify connectivity
            between LAN and WAN.

`perf-mcast-v6.tcl`

IPv6 multicast performance tests

Test	Name	Synopsis
`IPv6 Multicast UDP download throughput test WAN to LAN`	`ipv6_perf_mcast_1`	IPv6 Multicast UDP download throughput test WAN to LAN



    step 1. Start a performance client on the LAN.
    step 2. Verify connectivity between the LAN performance client and its
            Gateway (the DUT). If the testvar perfPingEnable is set to **yes**,
            measure and record the round trip time (RTT).
    step 3. Start a performance server on the WAN using the address/port
            specified by the testvar perfWanIp and perfPort.
    step 4. Run a UDP download performance test over IPv4 using the performance
            settings in the configuration file.
    step 5. Verify that the measured throughout performance falls between the
            configured high and low thresholds specified by the testvars
            perfDownloadUdpHighThreshold and perfDownloadUdpLowThreshold,
            respectively.
    step 6. Shutdown the performance client and server. Verify connectivity
            between LAN and WAN.

Test	Name	Synopsis
`IPv6 Multicast UDP upload throughput test LAN to WAN`	`ipv6_perf_mcast_2`	IPv6 Multicast UDP upload throughput test LAN to WAN



    step 1. Start a performance client on the LAN.
    step 2. Verify connectivity between the LAN performance client and its
            Gateway (the DUT). If the testvar perfPingEnable is set to **yes**,
            measure and record the round trip time (RTT).
    step 3. Start a performance server on the WAN using the address/port
            specified by the testvar perfWanIp and perfPort.
    step 4. Run a UDP upload performance test over IPv4 using the performance
            settings in the configuration file.
    step 5. Verify that the measured throughout performance falls between the
            configured high and low thresholds specified by the testvars
            perfUploadUdpHighThreshold and perfUploadUdpLowThreshold,
            respectively.
    step 6. Shutdown the performance client and server. Verify connectivity
            between LAN and WAN.

`perf-mcast-lan.tcl`

IPv4 multicast LAN to LAN performance tests

Test	Name	Synopsis
`IPv4 Multicast UDP 'download' throughput test LAN to LAN`	`perf_mcast_lan_1`	IPv4 Multicast UDP ‘download’ throughput test LAN to LAN



    step 1. Start a performance client on the LAN.
    step 2. Verify connectivity between the LAN performance client and its
            Gateway (the DUT). If the testvar perfPingEnable is set to **yes**,
            measure and record the round trip time (RTT).
    step 3. Start a performance server on a second LAN using the port
            specified by the testvar perfPort.
    step 4. Run a UDP download performance test over IPv4 using the performance
            settings in the configuration file.
    step 5. Verify that the measured throughout performance falls between the
            configured high and low thresholds specified by the testvars
            perfDownloadUdpHighThreshold and perfDownloadUdpLowThreshold,
            respectively.
    step 6. Shutdown the performance client and server. Verify connectivity
            between LAN and WAN.

Test	Name	Synopsis
`IPv4 Multicast UDP 'upload' throughput test LAN to LAN`	`perf_mcast_lan_2`	IPv4 Multicast UDP ‘upload’ throughput test LAN to LAN



    step 1. Start a performance client on the LAN.
    step 2. Verify connectivity between the LAN performance client and its
            Gateway (the DUT). If the testvar perfPingEnable is set to **yes**,
            measure and record the round trip time (RTT).
    step 3. Start a performance server on a second LAN using the port
            specified by the testvar perfPort.
    step 4. Run a UDP upload performance test over IPv4 using the performance
            settings in the configuration file.
    step 5. Verify that the measured throughout performance falls between the
            configured high and low thresholds specified by the testvars
            perfUploadUdpHighThreshold and perfUploadUdpLowThreshold,
            respectively.
    step 6. Shutdown the performance client and server. Verify connectivity
            between LAN and WAN.

`perf-mcast-lan-v6.tcl`

IPv6 multicast LAN to LAN performance tests

Test	Name	Synopsis
`IPv6 Multicast UDP 'download' throughput test LAN to LAN`	`ipv6_perf_mcast_lan_1`	IPv6 Multicast UDP ‘download’ throughput test LAN to LAN



    step 1. Start a performance client on the LAN.
    step 2. Verify connectivity between the LAN performance client and its
            Gateway (the DUT). If the testvar perfPingEnable is set to **yes**,
            measure and record the round trip time (RTT).
    step 3. Start a performance server on a second LAN using the port
            specified by the testvar perfPort.
    step 4. Run a UDP download performance test over IPv6 using the performance
            settings in the configuration file.
    step 5. Verify that the measured throughout performance falls between the
            configured high and low thresholds specified by the testvars
            perfDownloadUdpHighThreshold and perfDownloadUdpLowThreshold,
            respectively.
    step 6. Shutdown the performance client and server. Verify connectivity
            between LAN and WAN.

Test	Name	Synopsis
`IPv6 Multicast UDP 'upload' throughput test LAN to LAN`	`ipv6_perf_mcast_lan_2`	IPv6 Multicast UDP ‘upload’ throughput test LAN to LAN



    step 1. Start a performance client on the LAN.
    step 2. Verify connectivity between the LAN performance client and its
            Gateway (the DUT). If the testvar perfPingEnable is set to **yes**,
            measure and record the round trip time (RTT).
    step 3. Start a performance server on a second LAN using the port
            specified by the testvar perfPort.
    step 4. Run a UDP upload performance test over IPv6 using the performance
            settings in the configuration file.
    step 5. Verify that the measured throughout performance falls between the
            configured high and low thresholds specified by the testvars
            perfUploadUdpHighThreshold and perfUploadUdpLowThreshold,
            respectively.
    step 6. Shutdown the performance client and server. Verify connectivity
            between LAN and WAN.

`perf-multi.tcl`

IPv4 multiple LAN client performance tests

Test	Name	Synopsis
`Multiple clients IPv4 TCP download throughput test WAN to LAN`	`perf_multi_1`	Multiple clients IPv4 TCP download throughput test WAN to LAN



    step 1. Start a performance client on the each LAN client
    step 2. Verify connectivity between the LAN performance client and its
            Gateway (the DUT).
    step 3. Start a performance server on the WAN starting the address/port
            specified by the testvar perfWanIp and perfPort.
    step 4. Run a TCP download performance test over IPv4 using the performance
            settings in the configuration file.
    step 5. Verify that the measured throughout performance falls between the
            configured high and low thresholds specified by the testvars
            perfDownloadTcpHighThreshold and perfDownloadTcpLowThreshold,
            respectively. Also verify that the number of TCP retransmits is
            less then the value specified for perfDownloadTcpRetr, if it is set.
    step 6. Shutdown the performance clients and servers.

Test	Name	Synopsis
`Multiple clients IPv4 TCP upload throughput test LAN to WAN`	`perf_multi_2`	Multiple clients IPv4 TCP upload throughput test LAN to WAN



    step 1. Start a performance client on the each LAN client
    step 2. Verify connectivity between the LAN performance client and its
            Gateway (the DUT).
    step 3. Start a performance server on the WAN starting the address/port
            specified by the testvar perfWanIp and perfPort.
    step 4. Run a TCP upload performance test over IPv4 using the performance
            settings in the configuration file.
    step 5. Verify that the measured throughout performance falls between the
            configured high and low thresholds specified by the testvars
            perfUploadTcpHighThreshold and perfUploadTcpLowThreshold,
            respectively. Also verify that the number of TCP retransmits is
            less then the value specified for perfUploadTcpRetr, if it is set.
    step 6. Shutdown the performance clients and servers.

Test	Name	Synopsis
`Multiple clients IPv4 UDP download throughput test WAN to LAN`	`perf_multi_3`	Multiple clients IPv4 UDP download throughput test WAN to LAN



    step 1. Start a performance client on the each LAN client
    step 2. Verify connectivity between the LAN performance client and its
            Gateway (the DUT).
    step 3. Start a performance server on the WAN starting the address/port
            specified by the testvar perfWanIp and perfPort.
    step 4. Run a UDP download performance test over IPv4 using the performance
            settings in the configuration file.
    step 5. Verify that the measured throughout performance falls between the
            configured high and low thresholds specified by the testvars
            perfDownloadUdpHighThreshold and perfDownloadUdpLowThreshold,
            respectively.
    step 6. Shutdown the performance clients and servers.

Test	Name	Synopsis
`Multiple clients IPv4 UDP upload throughput test LAN to WAN`	`perf_multi_4`	Multiple clients IPv4 UDP upload throughput test LAN to WAN



    step 1. Start a performance client on the each LAN client
    step 2. Verify connectivity between the LAN performance client and its
            Gateway (the DUT).
    step 3. Start a performance server on the WAN starting the address/port
            specified by the testvar perfWanIp and perfPort.
    step 4. Run a UDP upload performance test over IPv4 using the performance
            settings in the configuration file.
    step 5. Verify that the measured throughout performance falls between the
            configured high and low thresholds specified by the testvars
            perfUploadUdpHighThreshold and perfUploadUdpLowThreshold,
            respectively.
    step 6. Shutdown the performance clients and servers.

`perf-multi-v6.tcl`

IPv6 multiple LAN client performance tests

Test	Name	Synopsis
`Multiple clients IPv6 TCP download throughput test WAN to LAN`	`ipv6_perf_multi_1`	Multiple clients IPv6 TCP download throughput test WAN to LAN




    step 1. Start a performance client on the each LAN client
    step 2. Verify connectivity between the LAN performance client and its
            Gateway (the DUT). 
    step 3. Start a performance server on the WAN starting the address/port
            specified by the testvar perfWanIp and perfPort.
    step 4. Run a TCP download performance test over IPv6 using the performance
            settings in the configuration file.
    step 5. Verify that the measured throughout performance falls between the
            configured high and low thresholds specified by the testvars
            perfDownloadTcpHighThreshold and perfDownloadTcpLowThreshold,
            respectively. Also verify that the number of TCP retransmits is
            less then the value specified for perfDownloadTcpRetr, if it is set.
    step 6. Shutdown the performance clients and servers.

Test	Name	Synopsis
`Multiple clients IPv6 TCP upload throughput test LAN to WAN`	`ipv6_perf_multi_2`	Multiple clients IPv6 TCP upload throughput test LAN to WAN



    step 1. Start a performance client on the each LAN client
    step 2. Verify connectivity between the LAN performance client and its
            Gateway (the DUT). 
    step 3. Start a performance server on the WAN starting the address/port
            specified by the testvar perfWanIp and perfPort.
    step 4. Run a TCP upload performance test over IPv6 using the performance
            settings in the configuration file.
    step 5. Verify that the measured throughout performance falls between the
            configured high and low thresholds specified by the testvars
            perfUploadTcpHighThreshold and perfUploadTcpLowThreshold,
            respectively. Also verify that the number of TCP retransmits is
            less then the value specified for perfUploadTcpRetr, if it is set.
    step 6. Shutdown the performance clients and servers.

Test	Name	Synopsis
`Multiple clients IPv6 UDP download throughput test WAN to LAN`	`ipv6_perf_multi_3`	Multiple clients IPv6 UDP download throughput test WAN to LAN



    step 1. Start a performance client on the each LAN client
    step 2. Verify connectivity between the LAN performance client and its
            Gateway (the DUT). 
    step 3. Start a performance server on the WAN starting the address/port
            specified by the testvar perfWanIp and perfPort.
    step 4. Run a UDP download performance test over IPv6 using the performance
            settings in the configuration file.
    step 5. Verify that the measured throughout performance falls between the
            configured high and low thresholds specified by the testvars
            perfDownloadUdpHighThreshold and perfDownloadUdpLowThreshold,
            respectively.
    step 6. Shutdown the performance clients and servers.

Test	Name	Synopsis
`Multiple clients IPv6 UDP upload throughput test LAN to WAN`	`ipv6_perf_multi_4`	Multiple clients IPv6 UDP upload throughput test LAN to WAN



    step 1. Start a performance client on the each LAN client
    step 2. Verify connectivity between the LAN performance client and its
            Gateway (the DUT). 
    step 3. Start a performance server on the WAN starting the address/port
            specified by the testvar perfWanIp and perfPort.
    step 4. Run a UDP upload performance test over IPv6 using the performance
            settings in the configuration file.
    step 5. Verify that the measured throughout performance falls between the
            configured high and low thresholds specified by the testvars
            perfUploadUdpHighThreshold and perfUploadUdpLowThreshold,
            respectively.
    step 6. Shutdown the performance clients and servers.

`fixed-rate-perf.tcl`

IPv4 fixed rate performance tests, 0 to 1 Gbps

Test	Name	Synopsis
`20 Mbps IPv4 TCP download throughput test`	`perf_IPv4_TCP_download_20Mbps`	20 Mbps IPv4 TCP download throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a TCP download performance test over IPv4 using a target bandwidth
        of 20 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfDownloadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`40 Mbps IPv4 TCP download throughput test`	`perf_IPv4_TCP_download_40Mbps`	40 Mbps IPv4 TCP download throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a TCP download performance test over IPv4 using a target bandwidth
        of 40 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfDownloadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`60 Mbps IPv4 TCP download throughput test`	`perf_IPv4_TCP_download_60Mbps`	60 Mbps IPv4 TCP download throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a TCP download performance test over IPv4 using a target bandwidth
        of 60 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfDownloadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`80 Mbps IPv4 TCP download throughput test`	`perf_IPv4_TCP_download_80Mbps`	80 Mbps IPv4 TCP download throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a TCP download performance test over IPv4 using a target bandwidth
        of 80 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfDownloadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`100 Mbps IPv4 TCP download throughput test`	`perf_IPv4_TCP_download_100Mbps`	100 Mbps IPv4 TCP download throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a TCP download performance test over IPv4 using a target bandwidth
        of 100 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfDownloadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`120 Mbps IPv4 TCP download throughput test`	`perf_IPv4_TCP_download_120Mbps`	120 Mbps IPv4 TCP download throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a TCP download performance test over IPv4 using a target bandwidth
        of 120 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfDownloadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`140 Mbps IPv4 TCP download throughput test`	`perf_IPv4_TCP_download_140Mbps`	140 Mbps IPv4 TCP download throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a TCP download performance test over IPv4 using a target bandwidth
        of 140 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfDownloadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`160 Mbps IPv4 TCP download throughput test`	`perf_IPv4_TCP_download_160Mbps`	160 Mbps IPv4 TCP download throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a TCP download performance test over IPv4 using a target bandwidth
        of 160 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfDownloadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`180 Mbps IPv4 TCP download throughput test`	`perf_IPv4_TCP_download_180Mbps`	180 Mbps IPv4 TCP download throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a TCP download performance test over IPv4 using a target bandwidth
        of 180 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfDownloadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`200 Mbps IPv4 TCP download throughput test`	`perf_IPv4_TCP_download_200Mbps`	200 Mbps IPv4 TCP download throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a TCP download performance test over IPv4 using a target bandwidth
        of 200 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfDownloadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`220 Mbps IPv4 TCP download throughput test`	`perf_IPv4_TCP_download_220Mbps`	220 Mbps IPv4 TCP download throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a TCP download performance test over IPv4 using a target bandwidth
        of 220 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfDownloadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`240 Mbps IPv4 TCP download throughput test`	`perf_IPv4_TCP_download_240Mbps`	240 Mbps IPv4 TCP download throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a TCP download performance test over IPv4 using a target bandwidth
        of 240 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfDownloadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`260 Mbps IPv4 TCP download throughput test`	`perf_IPv4_TCP_download_260Mbps`	260 Mbps IPv4 TCP download throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a TCP download performance test over IPv4 using a target bandwidth
        of 260 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfDownloadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`280 Mbps IPv4 TCP download throughput test`	`perf_IPv4_TCP_download_280Mbps`	280 Mbps IPv4 TCP download throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a TCP download performance test over IPv4 using a target bandwidth
        of 280 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfDownloadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`300 Mbps IPv4 TCP download throughput test`	`perf_IPv4_TCP_download_300Mbps`	300 Mbps IPv4 TCP download throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a TCP download performance test over IPv4 using a target bandwidth
        of 300 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfDownloadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`320 Mbps IPv4 TCP download throughput test`	`perf_IPv4_TCP_download_320Mbps`	320 Mbps IPv4 TCP download throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a TCP download performance test over IPv4 using a target bandwidth
        of 320 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfDownloadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`340 Mbps IPv4 TCP download throughput test`	`perf_IPv4_TCP_download_340Mbps`	340 Mbps IPv4 TCP download throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a TCP download performance test over IPv4 using a target bandwidth
        of 340 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfDownloadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`360 Mbps IPv4 TCP download throughput test`	`perf_IPv4_TCP_download_360Mbps`	360 Mbps IPv4 TCP download throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a TCP download performance test over IPv4 using a target bandwidth
        of 360 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfDownloadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`380 Mbps IPv4 TCP download throughput test`	`perf_IPv4_TCP_download_380Mbps`	380 Mbps IPv4 TCP download throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a TCP download performance test over IPv4 using a target bandwidth
        of 380 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfDownloadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`400 Mbps IPv4 TCP download throughput test`	`perf_IPv4_TCP_download_400Mbps`	400 Mbps IPv4 TCP download throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a TCP download performance test over IPv4 using a target bandwidth
        of 400 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfDownloadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`420 Mbps IPv4 TCP download throughput test`	`perf_IPv4_TCP_download_420Mbps`	420 Mbps IPv4 TCP download throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a TCP download performance test over IPv4 using a target bandwidth
        of 420 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfDownloadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`440 Mbps IPv4 TCP download throughput test`	`perf_IPv4_TCP_download_440Mbps`	440 Mbps IPv4 TCP download throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a TCP download performance test over IPv4 using a target bandwidth
        of 440 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfDownloadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`460 Mbps IPv4 TCP download throughput test`	`perf_IPv4_TCP_download_460Mbps`	460 Mbps IPv4 TCP download throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a TCP download performance test over IPv4 using a target bandwidth
        of 460 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfDownloadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`480 Mbps IPv4 TCP download throughput test`	`perf_IPv4_TCP_download_480Mbps`	480 Mbps IPv4 TCP download throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a TCP download performance test over IPv4 using a target bandwidth
        of 480 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfDownloadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`500 Mbps IPv4 TCP download throughput test`	`perf_IPv4_TCP_download_500Mbps`	500 Mbps IPv4 TCP download throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a TCP download performance test over IPv4 using a target bandwidth
        of 500 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfDownloadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`520 Mbps IPv4 TCP download throughput test`	`perf_IPv4_TCP_download_520Mbps`	520 Mbps IPv4 TCP download throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a TCP download performance test over IPv4 using a target bandwidth
        of 520 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfDownloadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`540 Mbps IPv4 TCP download throughput test`	`perf_IPv4_TCP_download_540Mbps`	540 Mbps IPv4 TCP download throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a TCP download performance test over IPv4 using a target bandwidth
        of 540 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfDownloadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`560 Mbps IPv4 TCP download throughput test`	`perf_IPv4_TCP_download_560Mbps`	560 Mbps IPv4 TCP download throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a TCP download performance test over IPv4 using a target bandwidth
        of 560 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfDownloadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`580 Mbps IPv4 TCP download throughput test`	`perf_IPv4_TCP_download_580Mbps`	580 Mbps IPv4 TCP download throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a TCP download performance test over IPv4 using a target bandwidth
        of 580 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfDownloadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`600 Mbps IPv4 TCP download throughput test`	`perf_IPv4_TCP_download_600Mbps`	600 Mbps IPv4 TCP download throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a TCP download performance test over IPv4 using a target bandwidth
        of 600 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfDownloadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`620 Mbps IPv4 TCP download throughput test`	`perf_IPv4_TCP_download_620Mbps`	620 Mbps IPv4 TCP download throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a TCP download performance test over IPv4 using a target bandwidth
        of 620 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfDownloadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`640 Mbps IPv4 TCP download throughput test`	`perf_IPv4_TCP_download_640Mbps`	640 Mbps IPv4 TCP download throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a TCP download performance test over IPv4 using a target bandwidth
        of 640 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfDownloadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`660 Mbps IPv4 TCP download throughput test`	`perf_IPv4_TCP_download_660Mbps`	660 Mbps IPv4 TCP download throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a TCP download performance test over IPv4 using a target bandwidth
        of 660 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfDownloadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`680 Mbps IPv4 TCP download throughput test`	`perf_IPv4_TCP_download_680Mbps`	680 Mbps IPv4 TCP download throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a TCP download performance test over IPv4 using a target bandwidth
        of 680 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfDownloadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`700 Mbps IPv4 TCP download throughput test`	`perf_IPv4_TCP_download_700Mbps`	700 Mbps IPv4 TCP download throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a TCP download performance test over IPv4 using a target bandwidth
        of 700 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfDownloadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`720 Mbps IPv4 TCP download throughput test`	`perf_IPv4_TCP_download_720Mbps`	720 Mbps IPv4 TCP download throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a TCP download performance test over IPv4 using a target bandwidth
        of 720 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfDownloadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`740 Mbps IPv4 TCP download throughput test`	`perf_IPv4_TCP_download_740Mbps`	740 Mbps IPv4 TCP download throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a TCP download performance test over IPv4 using a target bandwidth
        of 740 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfDownloadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`760 Mbps IPv4 TCP download throughput test`	`perf_IPv4_TCP_download_760Mbps`	760 Mbps IPv4 TCP download throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a TCP download performance test over IPv4 using a target bandwidth
        of 760 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfDownloadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`780 Mbps IPv4 TCP download throughput test`	`perf_IPv4_TCP_download_780Mbps`	780 Mbps IPv4 TCP download throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a TCP download performance test over IPv4 using a target bandwidth
        of 780 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfDownloadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`800 Mbps IPv4 TCP download throughput test`	`perf_IPv4_TCP_download_800Mbps`	800 Mbps IPv4 TCP download throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a TCP download performance test over IPv4 using a target bandwidth
        of 800 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfDownloadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`820 Mbps IPv4 TCP download throughput test`	`perf_IPv4_TCP_download_820Mbps`	820 Mbps IPv4 TCP download throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a TCP download performance test over IPv4 using a target bandwidth
        of 820 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfDownloadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`840 Mbps IPv4 TCP download throughput test`	`perf_IPv4_TCP_download_840Mbps`	840 Mbps IPv4 TCP download throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a TCP download performance test over IPv4 using a target bandwidth
        of 840 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfDownloadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`860 Mbps IPv4 TCP download throughput test`	`perf_IPv4_TCP_download_860Mbps`	860 Mbps IPv4 TCP download throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a TCP download performance test over IPv4 using a target bandwidth
        of 860 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfDownloadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`880 Mbps IPv4 TCP download throughput test`	`perf_IPv4_TCP_download_880Mbps`	880 Mbps IPv4 TCP download throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a TCP download performance test over IPv4 using a target bandwidth
        of 880 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfDownloadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`900 Mbps IPv4 TCP download throughput test`	`perf_IPv4_TCP_download_900Mbps`	900 Mbps IPv4 TCP download throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a TCP download performance test over IPv4 using a target bandwidth
        of 900 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfDownloadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`920 Mbps IPv4 TCP download throughput test`	`perf_IPv4_TCP_download_920Mbps`	920 Mbps IPv4 TCP download throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a TCP download performance test over IPv4 using a target bandwidth
        of 920 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfDownloadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`940 Mbps IPv4 TCP download throughput test`	`perf_IPv4_TCP_download_940Mbps`	940 Mbps IPv4 TCP download throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a TCP download performance test over IPv4 using a target bandwidth
        of 940 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfDownloadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`960 Mbps IPv4 TCP download throughput test`	`perf_IPv4_TCP_download_960Mbps`	960 Mbps IPv4 TCP download throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a TCP download performance test over IPv4 using a target bandwidth
        of 960 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfDownloadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`20 Mbps IPv4 TCP upload throughput test`	`perf_IPv4_TCP_upload_20Mbps`	20 Mbps IPv4 TCP upload throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a TCP upload performance test over IPv4 using a target bandwidth
        of 20 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfUploadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`40 Mbps IPv4 TCP upload throughput test`	`perf_IPv4_TCP_upload_40Mbps`	40 Mbps IPv4 TCP upload throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a TCP upload performance test over IPv4 using a target bandwidth
        of 40 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfUploadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`60 Mbps IPv4 TCP upload throughput test`	`perf_IPv4_TCP_upload_60Mbps`	60 Mbps IPv4 TCP upload throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a TCP upload performance test over IPv4 using a target bandwidth
        of 60 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfUploadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`80 Mbps IPv4 TCP upload throughput test`	`perf_IPv4_TCP_upload_80Mbps`	80 Mbps IPv4 TCP upload throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a TCP upload performance test over IPv4 using a target bandwidth
        of 80 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfUploadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`100 Mbps IPv4 TCP upload throughput test`	`perf_IPv4_TCP_upload_100Mbps`	100 Mbps IPv4 TCP upload throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a TCP upload performance test over IPv4 using a target bandwidth
        of 100 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfUploadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`120 Mbps IPv4 TCP upload throughput test`	`perf_IPv4_TCP_upload_120Mbps`	120 Mbps IPv4 TCP upload throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a TCP upload performance test over IPv4 using a target bandwidth
        of 120 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfUploadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`140 Mbps IPv4 TCP upload throughput test`	`perf_IPv4_TCP_upload_140Mbps`	140 Mbps IPv4 TCP upload throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a TCP upload performance test over IPv4 using a target bandwidth
        of 140 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfUploadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`160 Mbps IPv4 TCP upload throughput test`	`perf_IPv4_TCP_upload_160Mbps`	160 Mbps IPv4 TCP upload throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a TCP upload performance test over IPv4 using a target bandwidth
        of 160 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfUploadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`180 Mbps IPv4 TCP upload throughput test`	`perf_IPv4_TCP_upload_180Mbps`	180 Mbps IPv4 TCP upload throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a TCP upload performance test over IPv4 using a target bandwidth
        of 180 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfUploadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`200 Mbps IPv4 TCP upload throughput test`	`perf_IPv4_TCP_upload_200Mbps`	200 Mbps IPv4 TCP upload throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a TCP upload performance test over IPv4 using a target bandwidth
        of 200 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfUploadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`220 Mbps IPv4 TCP upload throughput test`	`perf_IPv4_TCP_upload_220Mbps`	220 Mbps IPv4 TCP upload throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a TCP upload performance test over IPv4 using a target bandwidth
        of 220 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfUploadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`240 Mbps IPv4 TCP upload throughput test`	`perf_IPv4_TCP_upload_240Mbps`	240 Mbps IPv4 TCP upload throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a TCP upload performance test over IPv4 using a target bandwidth
        of 240 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfUploadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`260 Mbps IPv4 TCP upload throughput test`	`perf_IPv4_TCP_upload_260Mbps`	260 Mbps IPv4 TCP upload throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a TCP upload performance test over IPv4 using a target bandwidth
        of 260 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfUploadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`280 Mbps IPv4 TCP upload throughput test`	`perf_IPv4_TCP_upload_280Mbps`	280 Mbps IPv4 TCP upload throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a TCP upload performance test over IPv4 using a target bandwidth
        of 280 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfUploadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`300 Mbps IPv4 TCP upload throughput test`	`perf_IPv4_TCP_upload_300Mbps`	300 Mbps IPv4 TCP upload throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a TCP upload performance test over IPv4 using a target bandwidth
        of 300 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfUploadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`320 Mbps IPv4 TCP upload throughput test`	`perf_IPv4_TCP_upload_320Mbps`	320 Mbps IPv4 TCP upload throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a TCP upload performance test over IPv4 using a target bandwidth
        of 320 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfUploadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`340 Mbps IPv4 TCP upload throughput test`	`perf_IPv4_TCP_upload_340Mbps`	340 Mbps IPv4 TCP upload throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a TCP upload performance test over IPv4 using a target bandwidth
        of 340 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfUploadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`360 Mbps IPv4 TCP upload throughput test`	`perf_IPv4_TCP_upload_360Mbps`	360 Mbps IPv4 TCP upload throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a TCP upload performance test over IPv4 using a target bandwidth
        of 360 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfUploadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`380 Mbps IPv4 TCP upload throughput test`	`perf_IPv4_TCP_upload_380Mbps`	380 Mbps IPv4 TCP upload throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a TCP upload performance test over IPv4 using a target bandwidth
        of 380 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfUploadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`400 Mbps IPv4 TCP upload throughput test`	`perf_IPv4_TCP_upload_400Mbps`	400 Mbps IPv4 TCP upload throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a TCP upload performance test over IPv4 using a target bandwidth
        of 400 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfUploadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`420 Mbps IPv4 TCP upload throughput test`	`perf_IPv4_TCP_upload_420Mbps`	420 Mbps IPv4 TCP upload throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a TCP upload performance test over IPv4 using a target bandwidth
        of 420 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfUploadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`440 Mbps IPv4 TCP upload throughput test`	`perf_IPv4_TCP_upload_440Mbps`	440 Mbps IPv4 TCP upload throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a TCP upload performance test over IPv4 using a target bandwidth
        of 440 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfUploadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`460 Mbps IPv4 TCP upload throughput test`	`perf_IPv4_TCP_upload_460Mbps`	460 Mbps IPv4 TCP upload throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a TCP upload performance test over IPv4 using a target bandwidth
        of 460 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfUploadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`480 Mbps IPv4 TCP upload throughput test`	`perf_IPv4_TCP_upload_480Mbps`	480 Mbps IPv4 TCP upload throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a TCP upload performance test over IPv4 using a target bandwidth
        of 480 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfUploadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`500 Mbps IPv4 TCP upload throughput test`	`perf_IPv4_TCP_upload_500Mbps`	500 Mbps IPv4 TCP upload throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a TCP upload performance test over IPv4 using a target bandwidth
        of 500 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfUploadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`520 Mbps IPv4 TCP upload throughput test`	`perf_IPv4_TCP_upload_520Mbps`	520 Mbps IPv4 TCP upload throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a TCP upload performance test over IPv4 using a target bandwidth
        of 520 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfUploadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`540 Mbps IPv4 TCP upload throughput test`	`perf_IPv4_TCP_upload_540Mbps`	540 Mbps IPv4 TCP upload throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a TCP upload performance test over IPv4 using a target bandwidth
        of 540 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfUploadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`560 Mbps IPv4 TCP upload throughput test`	`perf_IPv4_TCP_upload_560Mbps`	560 Mbps IPv4 TCP upload throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a TCP upload performance test over IPv4 using a target bandwidth
        of 560 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfUploadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`580 Mbps IPv4 TCP upload throughput test`	`perf_IPv4_TCP_upload_580Mbps`	580 Mbps IPv4 TCP upload throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a TCP upload performance test over IPv4 using a target bandwidth
        of 580 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfUploadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`600 Mbps IPv4 TCP upload throughput test`	`perf_IPv4_TCP_upload_600Mbps`	600 Mbps IPv4 TCP upload throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a TCP upload performance test over IPv4 using a target bandwidth
        of 600 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfUploadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`620 Mbps IPv4 TCP upload throughput test`	`perf_IPv4_TCP_upload_620Mbps`	620 Mbps IPv4 TCP upload throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a TCP upload performance test over IPv4 using a target bandwidth
        of 620 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfUploadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`640 Mbps IPv4 TCP upload throughput test`	`perf_IPv4_TCP_upload_640Mbps`	640 Mbps IPv4 TCP upload throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a TCP upload performance test over IPv4 using a target bandwidth
        of 640 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfUploadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`660 Mbps IPv4 TCP upload throughput test`	`perf_IPv4_TCP_upload_660Mbps`	660 Mbps IPv4 TCP upload throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a TCP upload performance test over IPv4 using a target bandwidth
        of 660 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfUploadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`680 Mbps IPv4 TCP upload throughput test`	`perf_IPv4_TCP_upload_680Mbps`	680 Mbps IPv4 TCP upload throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a TCP upload performance test over IPv4 using a target bandwidth
        of 680 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfUploadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`700 Mbps IPv4 TCP upload throughput test`	`perf_IPv4_TCP_upload_700Mbps`	700 Mbps IPv4 TCP upload throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a TCP upload performance test over IPv4 using a target bandwidth
        of 700 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfUploadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`720 Mbps IPv4 TCP upload throughput test`	`perf_IPv4_TCP_upload_720Mbps`	720 Mbps IPv4 TCP upload throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a TCP upload performance test over IPv4 using a target bandwidth
        of 720 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfUploadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`740 Mbps IPv4 TCP upload throughput test`	`perf_IPv4_TCP_upload_740Mbps`	740 Mbps IPv4 TCP upload throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a TCP upload performance test over IPv4 using a target bandwidth
        of 740 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfUploadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`760 Mbps IPv4 TCP upload throughput test`	`perf_IPv4_TCP_upload_760Mbps`	760 Mbps IPv4 TCP upload throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a TCP upload performance test over IPv4 using a target bandwidth
        of 760 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfUploadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`780 Mbps IPv4 TCP upload throughput test`	`perf_IPv4_TCP_upload_780Mbps`	780 Mbps IPv4 TCP upload throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a TCP upload performance test over IPv4 using a target bandwidth
        of 780 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfUploadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`800 Mbps IPv4 TCP upload throughput test`	`perf_IPv4_TCP_upload_800Mbps`	800 Mbps IPv4 TCP upload throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a TCP upload performance test over IPv4 using a target bandwidth
        of 800 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfUploadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`820 Mbps IPv4 TCP upload throughput test`	`perf_IPv4_TCP_upload_820Mbps`	820 Mbps IPv4 TCP upload throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a TCP upload performance test over IPv4 using a target bandwidth
        of 820 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfUploadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`840 Mbps IPv4 TCP upload throughput test`	`perf_IPv4_TCP_upload_840Mbps`	840 Mbps IPv4 TCP upload throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a TCP upload performance test over IPv4 using a target bandwidth
        of 840 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfUploadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`860 Mbps IPv4 TCP upload throughput test`	`perf_IPv4_TCP_upload_860Mbps`	860 Mbps IPv4 TCP upload throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a TCP upload performance test over IPv4 using a target bandwidth
        of 860 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfUploadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`880 Mbps IPv4 TCP upload throughput test`	`perf_IPv4_TCP_upload_880Mbps`	880 Mbps IPv4 TCP upload throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a TCP upload performance test over IPv4 using a target bandwidth
        of 880 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfUploadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`900 Mbps IPv4 TCP upload throughput test`	`perf_IPv4_TCP_upload_900Mbps`	900 Mbps IPv4 TCP upload throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a TCP upload performance test over IPv4 using a target bandwidth
        of 900 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfUploadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`920 Mbps IPv4 TCP upload throughput test`	`perf_IPv4_TCP_upload_920Mbps`	920 Mbps IPv4 TCP upload throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a TCP upload performance test over IPv4 using a target bandwidth
        of 920 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfUploadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`940 Mbps IPv4 TCP upload throughput test`	`perf_IPv4_TCP_upload_940Mbps`	940 Mbps IPv4 TCP upload throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a TCP upload performance test over IPv4 using a target bandwidth
        of 940 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfUploadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`960 Mbps IPv4 TCP upload throughput test`	`perf_IPv4_TCP_upload_960Mbps`	960 Mbps IPv4 TCP upload throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a TCP upload performance test over IPv4 using a target bandwidth
        of 960 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfUploadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`20 Mbps IPv4 UDP download throughput test`	`perf_IPv4_UDP_download_20Mbps`	20 Mbps IPv4 UDP download throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a UDP download performance test over IPv4 using a target bandwidth
        of 20 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfDownloadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`40 Mbps IPv4 UDP download throughput test`	`perf_IPv4_UDP_download_40Mbps`	40 Mbps IPv4 UDP download throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a UDP download performance test over IPv4 using a target bandwidth
        of 40 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfDownloadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`60 Mbps IPv4 UDP download throughput test`	`perf_IPv4_UDP_download_60Mbps`	60 Mbps IPv4 UDP download throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a UDP download performance test over IPv4 using a target bandwidth
        of 60 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfDownloadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`80 Mbps IPv4 UDP download throughput test`	`perf_IPv4_UDP_download_80Mbps`	80 Mbps IPv4 UDP download throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a UDP download performance test over IPv4 using a target bandwidth
        of 80 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfDownloadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`100 Mbps IPv4 UDP download throughput test`	`perf_IPv4_UDP_download_100Mbps`	100 Mbps IPv4 UDP download throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a UDP download performance test over IPv4 using a target bandwidth
        of 100 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfDownloadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`120 Mbps IPv4 UDP download throughput test`	`perf_IPv4_UDP_download_120Mbps`	120 Mbps IPv4 UDP download throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a UDP download performance test over IPv4 using a target bandwidth
        of 120 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfDownloadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`140 Mbps IPv4 UDP download throughput test`	`perf_IPv4_UDP_download_140Mbps`	140 Mbps IPv4 UDP download throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a UDP download performance test over IPv4 using a target bandwidth
        of 140 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfDownloadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`160 Mbps IPv4 UDP download throughput test`	`perf_IPv4_UDP_download_160Mbps`	160 Mbps IPv4 UDP download throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a UDP download performance test over IPv4 using a target bandwidth
        of 160 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfDownloadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`180 Mbps IPv4 UDP download throughput test`	`perf_IPv4_UDP_download_180Mbps`	180 Mbps IPv4 UDP download throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a UDP download performance test over IPv4 using a target bandwidth
        of 180 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfDownloadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`200 Mbps IPv4 UDP download throughput test`	`perf_IPv4_UDP_download_200Mbps`	200 Mbps IPv4 UDP download throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a UDP download performance test over IPv4 using a target bandwidth
        of 200 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfDownloadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`220 Mbps IPv4 UDP download throughput test`	`perf_IPv4_UDP_download_220Mbps`	220 Mbps IPv4 UDP download throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a UDP download performance test over IPv4 using a target bandwidth
        of 220 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfDownloadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`240 Mbps IPv4 UDP download throughput test`	`perf_IPv4_UDP_download_240Mbps`	240 Mbps IPv4 UDP download throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a UDP download performance test over IPv4 using a target bandwidth
        of 240 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfDownloadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`260 Mbps IPv4 UDP download throughput test`	`perf_IPv4_UDP_download_260Mbps`	260 Mbps IPv4 UDP download throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a UDP download performance test over IPv4 using a target bandwidth
        of 260 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfDownloadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`280 Mbps IPv4 UDP download throughput test`	`perf_IPv4_UDP_download_280Mbps`	280 Mbps IPv4 UDP download throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a UDP download performance test over IPv4 using a target bandwidth
        of 280 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfDownloadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`300 Mbps IPv4 UDP download throughput test`	`perf_IPv4_UDP_download_300Mbps`	300 Mbps IPv4 UDP download throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a UDP download performance test over IPv4 using a target bandwidth
        of 300 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfDownloadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`320 Mbps IPv4 UDP download throughput test`	`perf_IPv4_UDP_download_320Mbps`	320 Mbps IPv4 UDP download throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a UDP download performance test over IPv4 using a target bandwidth
        of 320 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfDownloadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`340 Mbps IPv4 UDP download throughput test`	`perf_IPv4_UDP_download_340Mbps`	340 Mbps IPv4 UDP download throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a UDP download performance test over IPv4 using a target bandwidth
        of 340 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfDownloadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`360 Mbps IPv4 UDP download throughput test`	`perf_IPv4_UDP_download_360Mbps`	360 Mbps IPv4 UDP download throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a UDP download performance test over IPv4 using a target bandwidth
        of 360 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfDownloadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`380 Mbps IPv4 UDP download throughput test`	`perf_IPv4_UDP_download_380Mbps`	380 Mbps IPv4 UDP download throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a UDP download performance test over IPv4 using a target bandwidth
        of 380 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfDownloadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`400 Mbps IPv4 UDP download throughput test`	`perf_IPv4_UDP_download_400Mbps`	400 Mbps IPv4 UDP download throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a UDP download performance test over IPv4 using a target bandwidth
        of 400 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfDownloadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`420 Mbps IPv4 UDP download throughput test`	`perf_IPv4_UDP_download_420Mbps`	420 Mbps IPv4 UDP download throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a UDP download performance test over IPv4 using a target bandwidth
        of 420 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfDownloadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`440 Mbps IPv4 UDP download throughput test`	`perf_IPv4_UDP_download_440Mbps`	440 Mbps IPv4 UDP download throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a UDP download performance test over IPv4 using a target bandwidth
        of 440 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfDownloadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`460 Mbps IPv4 UDP download throughput test`	`perf_IPv4_UDP_download_460Mbps`	460 Mbps IPv4 UDP download throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a UDP download performance test over IPv4 using a target bandwidth
        of 460 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfDownloadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`480 Mbps IPv4 UDP download throughput test`	`perf_IPv4_UDP_download_480Mbps`	480 Mbps IPv4 UDP download throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a UDP download performance test over IPv4 using a target bandwidth
        of 480 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfDownloadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`500 Mbps IPv4 UDP download throughput test`	`perf_IPv4_UDP_download_500Mbps`	500 Mbps IPv4 UDP download throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a UDP download performance test over IPv4 using a target bandwidth
        of 500 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfDownloadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`520 Mbps IPv4 UDP download throughput test`	`perf_IPv4_UDP_download_520Mbps`	520 Mbps IPv4 UDP download throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a UDP download performance test over IPv4 using a target bandwidth
        of 520 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfDownloadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`540 Mbps IPv4 UDP download throughput test`	`perf_IPv4_UDP_download_540Mbps`	540 Mbps IPv4 UDP download throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a UDP download performance test over IPv4 using a target bandwidth
        of 540 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfDownloadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`560 Mbps IPv4 UDP download throughput test`	`perf_IPv4_UDP_download_560Mbps`	560 Mbps IPv4 UDP download throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a UDP download performance test over IPv4 using a target bandwidth
        of 560 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfDownloadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`580 Mbps IPv4 UDP download throughput test`	`perf_IPv4_UDP_download_580Mbps`	580 Mbps IPv4 UDP download throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a UDP download performance test over IPv4 using a target bandwidth
        of 580 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfDownloadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`600 Mbps IPv4 UDP download throughput test`	`perf_IPv4_UDP_download_600Mbps`	600 Mbps IPv4 UDP download throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a UDP download performance test over IPv4 using a target bandwidth
        of 600 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfDownloadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`620 Mbps IPv4 UDP download throughput test`	`perf_IPv4_UDP_download_620Mbps`	620 Mbps IPv4 UDP download throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a UDP download performance test over IPv4 using a target bandwidth
        of 620 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfDownloadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`640 Mbps IPv4 UDP download throughput test`	`perf_IPv4_UDP_download_640Mbps`	640 Mbps IPv4 UDP download throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a UDP download performance test over IPv4 using a target bandwidth
        of 640 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfDownloadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`660 Mbps IPv4 UDP download throughput test`	`perf_IPv4_UDP_download_660Mbps`	660 Mbps IPv4 UDP download throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a UDP download performance test over IPv4 using a target bandwidth
        of 660 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfDownloadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`680 Mbps IPv4 UDP download throughput test`	`perf_IPv4_UDP_download_680Mbps`	680 Mbps IPv4 UDP download throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a UDP download performance test over IPv4 using a target bandwidth
        of 680 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfDownloadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`700 Mbps IPv4 UDP download throughput test`	`perf_IPv4_UDP_download_700Mbps`	700 Mbps IPv4 UDP download throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a UDP download performance test over IPv4 using a target bandwidth
        of 700 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfDownloadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`720 Mbps IPv4 UDP download throughput test`	`perf_IPv4_UDP_download_720Mbps`	720 Mbps IPv4 UDP download throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a UDP download performance test over IPv4 using a target bandwidth
        of 720 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfDownloadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`740 Mbps IPv4 UDP download throughput test`	`perf_IPv4_UDP_download_740Mbps`	740 Mbps IPv4 UDP download throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a UDP download performance test over IPv4 using a target bandwidth
        of 740 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfDownloadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`760 Mbps IPv4 UDP download throughput test`	`perf_IPv4_UDP_download_760Mbps`	760 Mbps IPv4 UDP download throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a UDP download performance test over IPv4 using a target bandwidth
        of 760 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfDownloadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`780 Mbps IPv4 UDP download throughput test`	`perf_IPv4_UDP_download_780Mbps`	780 Mbps IPv4 UDP download throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a UDP download performance test over IPv4 using a target bandwidth
        of 780 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfDownloadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`800 Mbps IPv4 UDP download throughput test`	`perf_IPv4_UDP_download_800Mbps`	800 Mbps IPv4 UDP download throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a UDP download performance test over IPv4 using a target bandwidth
        of 800 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfDownloadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`820 Mbps IPv4 UDP download throughput test`	`perf_IPv4_UDP_download_820Mbps`	820 Mbps IPv4 UDP download throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a UDP download performance test over IPv4 using a target bandwidth
        of 820 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfDownloadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`840 Mbps IPv4 UDP download throughput test`	`perf_IPv4_UDP_download_840Mbps`	840 Mbps IPv4 UDP download throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a UDP download performance test over IPv4 using a target bandwidth
        of 840 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfDownloadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`860 Mbps IPv4 UDP download throughput test`	`perf_IPv4_UDP_download_860Mbps`	860 Mbps IPv4 UDP download throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a UDP download performance test over IPv4 using a target bandwidth
        of 860 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfDownloadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`880 Mbps IPv4 UDP download throughput test`	`perf_IPv4_UDP_download_880Mbps`	880 Mbps IPv4 UDP download throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a UDP download performance test over IPv4 using a target bandwidth
        of 880 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfDownloadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`900 Mbps IPv4 UDP download throughput test`	`perf_IPv4_UDP_download_900Mbps`	900 Mbps IPv4 UDP download throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a UDP download performance test over IPv4 using a target bandwidth
        of 900 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfDownloadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`920 Mbps IPv4 UDP download throughput test`	`perf_IPv4_UDP_download_920Mbps`	920 Mbps IPv4 UDP download throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a UDP download performance test over IPv4 using a target bandwidth
        of 920 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfDownloadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`940 Mbps IPv4 UDP download throughput test`	`perf_IPv4_UDP_download_940Mbps`	940 Mbps IPv4 UDP download throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a UDP download performance test over IPv4 using a target bandwidth
        of 940 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfDownloadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`960 Mbps IPv4 UDP download throughput test`	`perf_IPv4_UDP_download_960Mbps`	960 Mbps IPv4 UDP download throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a UDP download performance test over IPv4 using a target bandwidth
        of 960 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfDownloadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`20 Mbps IPv4 UDP upload throughput test`	`perf_IPv4_UDP_upload_20Mbps`	20 Mbps IPv4 UDP upload throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a UDP upload performance test over IPv4 using a target bandwidth
        of 20 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfUploadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`40 Mbps IPv4 UDP upload throughput test`	`perf_IPv4_UDP_upload_40Mbps`	40 Mbps IPv4 UDP upload throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a UDP upload performance test over IPv4 using a target bandwidth
        of 40 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfUploadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`60 Mbps IPv4 UDP upload throughput test`	`perf_IPv4_UDP_upload_60Mbps`	60 Mbps IPv4 UDP upload throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a UDP upload performance test over IPv4 using a target bandwidth
        of 60 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfUploadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`80 Mbps IPv4 UDP upload throughput test`	`perf_IPv4_UDP_upload_80Mbps`	80 Mbps IPv4 UDP upload throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a UDP upload performance test over IPv4 using a target bandwidth
        of 80 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfUploadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`100 Mbps IPv4 UDP upload throughput test`	`perf_IPv4_UDP_upload_100Mbps`	100 Mbps IPv4 UDP upload throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a UDP upload performance test over IPv4 using a target bandwidth
        of 100 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfUploadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`120 Mbps IPv4 UDP upload throughput test`	`perf_IPv4_UDP_upload_120Mbps`	120 Mbps IPv4 UDP upload throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a UDP upload performance test over IPv4 using a target bandwidth
        of 120 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfUploadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`140 Mbps IPv4 UDP upload throughput test`	`perf_IPv4_UDP_upload_140Mbps`	140 Mbps IPv4 UDP upload throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a UDP upload performance test over IPv4 using a target bandwidth
        of 140 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfUploadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`160 Mbps IPv4 UDP upload throughput test`	`perf_IPv4_UDP_upload_160Mbps`	160 Mbps IPv4 UDP upload throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a UDP upload performance test over IPv4 using a target bandwidth
        of 160 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfUploadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`180 Mbps IPv4 UDP upload throughput test`	`perf_IPv4_UDP_upload_180Mbps`	180 Mbps IPv4 UDP upload throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a UDP upload performance test over IPv4 using a target bandwidth
        of 180 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfUploadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`200 Mbps IPv4 UDP upload throughput test`	`perf_IPv4_UDP_upload_200Mbps`	200 Mbps IPv4 UDP upload throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a UDP upload performance test over IPv4 using a target bandwidth
        of 200 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfUploadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`220 Mbps IPv4 UDP upload throughput test`	`perf_IPv4_UDP_upload_220Mbps`	220 Mbps IPv4 UDP upload throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a UDP upload performance test over IPv4 using a target bandwidth
        of 220 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfUploadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`240 Mbps IPv4 UDP upload throughput test`	`perf_IPv4_UDP_upload_240Mbps`	240 Mbps IPv4 UDP upload throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a UDP upload performance test over IPv4 using a target bandwidth
        of 240 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfUploadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`260 Mbps IPv4 UDP upload throughput test`	`perf_IPv4_UDP_upload_260Mbps`	260 Mbps IPv4 UDP upload throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a UDP upload performance test over IPv4 using a target bandwidth
        of 260 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfUploadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`280 Mbps IPv4 UDP upload throughput test`	`perf_IPv4_UDP_upload_280Mbps`	280 Mbps IPv4 UDP upload throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a UDP upload performance test over IPv4 using a target bandwidth
        of 280 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfUploadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`300 Mbps IPv4 UDP upload throughput test`	`perf_IPv4_UDP_upload_300Mbps`	300 Mbps IPv4 UDP upload throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a UDP upload performance test over IPv4 using a target bandwidth
        of 300 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfUploadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`320 Mbps IPv4 UDP upload throughput test`	`perf_IPv4_UDP_upload_320Mbps`	320 Mbps IPv4 UDP upload throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a UDP upload performance test over IPv4 using a target bandwidth
        of 320 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfUploadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`340 Mbps IPv4 UDP upload throughput test`	`perf_IPv4_UDP_upload_340Mbps`	340 Mbps IPv4 UDP upload throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a UDP upload performance test over IPv4 using a target bandwidth
        of 340 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfUploadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`360 Mbps IPv4 UDP upload throughput test`	`perf_IPv4_UDP_upload_360Mbps`	360 Mbps IPv4 UDP upload throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a UDP upload performance test over IPv4 using a target bandwidth
        of 360 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfUploadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`380 Mbps IPv4 UDP upload throughput test`	`perf_IPv4_UDP_upload_380Mbps`	380 Mbps IPv4 UDP upload throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a UDP upload performance test over IPv4 using a target bandwidth
        of 380 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfUploadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`400 Mbps IPv4 UDP upload throughput test`	`perf_IPv4_UDP_upload_400Mbps`	400 Mbps IPv4 UDP upload throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a UDP upload performance test over IPv4 using a target bandwidth
        of 400 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfUploadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`420 Mbps IPv4 UDP upload throughput test`	`perf_IPv4_UDP_upload_420Mbps`	420 Mbps IPv4 UDP upload throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a UDP upload performance test over IPv4 using a target bandwidth
        of 420 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfUploadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`440 Mbps IPv4 UDP upload throughput test`	`perf_IPv4_UDP_upload_440Mbps`	440 Mbps IPv4 UDP upload throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a UDP upload performance test over IPv4 using a target bandwidth
        of 440 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfUploadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`460 Mbps IPv4 UDP upload throughput test`	`perf_IPv4_UDP_upload_460Mbps`	460 Mbps IPv4 UDP upload throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a UDP upload performance test over IPv4 using a target bandwidth
        of 460 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfUploadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`480 Mbps IPv4 UDP upload throughput test`	`perf_IPv4_UDP_upload_480Mbps`	480 Mbps IPv4 UDP upload throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a UDP upload performance test over IPv4 using a target bandwidth
        of 480 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfUploadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`500 Mbps IPv4 UDP upload throughput test`	`perf_IPv4_UDP_upload_500Mbps`	500 Mbps IPv4 UDP upload throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a UDP upload performance test over IPv4 using a target bandwidth
        of 500 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfUploadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`520 Mbps IPv4 UDP upload throughput test`	`perf_IPv4_UDP_upload_520Mbps`	520 Mbps IPv4 UDP upload throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a UDP upload performance test over IPv4 using a target bandwidth
        of 520 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfUploadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`540 Mbps IPv4 UDP upload throughput test`	`perf_IPv4_UDP_upload_540Mbps`	540 Mbps IPv4 UDP upload throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a UDP upload performance test over IPv4 using a target bandwidth
        of 540 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfUploadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`560 Mbps IPv4 UDP upload throughput test`	`perf_IPv4_UDP_upload_560Mbps`	560 Mbps IPv4 UDP upload throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a UDP upload performance test over IPv4 using a target bandwidth
        of 560 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfUploadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`580 Mbps IPv4 UDP upload throughput test`	`perf_IPv4_UDP_upload_580Mbps`	580 Mbps IPv4 UDP upload throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a UDP upload performance test over IPv4 using a target bandwidth
        of 580 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfUploadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`600 Mbps IPv4 UDP upload throughput test`	`perf_IPv4_UDP_upload_600Mbps`	600 Mbps IPv4 UDP upload throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a UDP upload performance test over IPv4 using a target bandwidth
        of 600 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfUploadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`620 Mbps IPv4 UDP upload throughput test`	`perf_IPv4_UDP_upload_620Mbps`	620 Mbps IPv4 UDP upload throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a UDP upload performance test over IPv4 using a target bandwidth
        of 620 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfUploadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`640 Mbps IPv4 UDP upload throughput test`	`perf_IPv4_UDP_upload_640Mbps`	640 Mbps IPv4 UDP upload throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a UDP upload performance test over IPv4 using a target bandwidth
        of 640 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfUploadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`660 Mbps IPv4 UDP upload throughput test`	`perf_IPv4_UDP_upload_660Mbps`	660 Mbps IPv4 UDP upload throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a UDP upload performance test over IPv4 using a target bandwidth
        of 660 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfUploadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`680 Mbps IPv4 UDP upload throughput test`	`perf_IPv4_UDP_upload_680Mbps`	680 Mbps IPv4 UDP upload throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a UDP upload performance test over IPv4 using a target bandwidth
        of 680 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfUploadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`700 Mbps IPv4 UDP upload throughput test`	`perf_IPv4_UDP_upload_700Mbps`	700 Mbps IPv4 UDP upload throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a UDP upload performance test over IPv4 using a target bandwidth
        of 700 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfUploadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`720 Mbps IPv4 UDP upload throughput test`	`perf_IPv4_UDP_upload_720Mbps`	720 Mbps IPv4 UDP upload throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a UDP upload performance test over IPv4 using a target bandwidth
        of 720 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfUploadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`740 Mbps IPv4 UDP upload throughput test`	`perf_IPv4_UDP_upload_740Mbps`	740 Mbps IPv4 UDP upload throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a UDP upload performance test over IPv4 using a target bandwidth
        of 740 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfUploadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`760 Mbps IPv4 UDP upload throughput test`	`perf_IPv4_UDP_upload_760Mbps`	760 Mbps IPv4 UDP upload throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a UDP upload performance test over IPv4 using a target bandwidth
        of 760 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfUploadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`780 Mbps IPv4 UDP upload throughput test`	`perf_IPv4_UDP_upload_780Mbps`	780 Mbps IPv4 UDP upload throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a UDP upload performance test over IPv4 using a target bandwidth
        of 780 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfUploadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`800 Mbps IPv4 UDP upload throughput test`	`perf_IPv4_UDP_upload_800Mbps`	800 Mbps IPv4 UDP upload throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a UDP upload performance test over IPv4 using a target bandwidth
        of 800 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfUploadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`820 Mbps IPv4 UDP upload throughput test`	`perf_IPv4_UDP_upload_820Mbps`	820 Mbps IPv4 UDP upload throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a UDP upload performance test over IPv4 using a target bandwidth
        of 820 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfUploadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`840 Mbps IPv4 UDP upload throughput test`	`perf_IPv4_UDP_upload_840Mbps`	840 Mbps IPv4 UDP upload throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a UDP upload performance test over IPv4 using a target bandwidth
        of 840 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfUploadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`860 Mbps IPv4 UDP upload throughput test`	`perf_IPv4_UDP_upload_860Mbps`	860 Mbps IPv4 UDP upload throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a UDP upload performance test over IPv4 using a target bandwidth
        of 860 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfUploadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`880 Mbps IPv4 UDP upload throughput test`	`perf_IPv4_UDP_upload_880Mbps`	880 Mbps IPv4 UDP upload throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a UDP upload performance test over IPv4 using a target bandwidth
        of 880 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfUploadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`900 Mbps IPv4 UDP upload throughput test`	`perf_IPv4_UDP_upload_900Mbps`	900 Mbps IPv4 UDP upload throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a UDP upload performance test over IPv4 using a target bandwidth
        of 900 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfUploadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`920 Mbps IPv4 UDP upload throughput test`	`perf_IPv4_UDP_upload_920Mbps`	920 Mbps IPv4 UDP upload throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a UDP upload performance test over IPv4 using a target bandwidth
        of 920 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfUploadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`940 Mbps IPv4 UDP upload throughput test`	`perf_IPv4_UDP_upload_940Mbps`	940 Mbps IPv4 UDP upload throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a UDP upload performance test over IPv4 using a target bandwidth
        of 940 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfUploadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`960 Mbps IPv4 UDP upload throughput test`	`perf_IPv4_UDP_upload_960Mbps`	960 Mbps IPv4 UDP upload throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a UDP upload performance test over IPv4 using a target bandwidth
        of 960 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfUploadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

`fixed-rate-perf-v6.tcl`

IPv6 fixed rate performance tests, 0 to 1 Gbps

Test	Name	Synopsis
`20 Mbps IPv6 TCP download throughput test`	`perf_IPv6_TCP_download_20Mbps`	20 Mbps IPv6 TCP download throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a TCP download performance test over IPv6 using a target bandwidth
        of 20 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfDownloadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`40 Mbps IPv6 TCP download throughput test`	`perf_IPv6_TCP_download_40Mbps`	40 Mbps IPv6 TCP download throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a TCP download performance test over IPv6 using a target bandwidth
        of 40 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfDownloadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`60 Mbps IPv6 TCP download throughput test`	`perf_IPv6_TCP_download_60Mbps`	60 Mbps IPv6 TCP download throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a TCP download performance test over IPv6 using a target bandwidth
        of 60 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfDownloadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`80 Mbps IPv6 TCP download throughput test`	`perf_IPv6_TCP_download_80Mbps`	80 Mbps IPv6 TCP download throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a TCP download performance test over IPv6 using a target bandwidth
        of 80 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfDownloadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`100 Mbps IPv6 TCP download throughput test`	`perf_IPv6_TCP_download_100Mbps`	100 Mbps IPv6 TCP download throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a TCP download performance test over IPv6 using a target bandwidth
        of 100 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfDownloadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`120 Mbps IPv6 TCP download throughput test`	`perf_IPv6_TCP_download_120Mbps`	120 Mbps IPv6 TCP download throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a TCP download performance test over IPv6 using a target bandwidth
        of 120 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfDownloadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`140 Mbps IPv6 TCP download throughput test`	`perf_IPv6_TCP_download_140Mbps`	140 Mbps IPv6 TCP download throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a TCP download performance test over IPv6 using a target bandwidth
        of 140 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfDownloadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`160 Mbps IPv6 TCP download throughput test`	`perf_IPv6_TCP_download_160Mbps`	160 Mbps IPv6 TCP download throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a TCP download performance test over IPv6 using a target bandwidth
        of 160 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfDownloadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`180 Mbps IPv6 TCP download throughput test`	`perf_IPv6_TCP_download_180Mbps`	180 Mbps IPv6 TCP download throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a TCP download performance test over IPv6 using a target bandwidth
        of 180 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfDownloadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`200 Mbps IPv6 TCP download throughput test`	`perf_IPv6_TCP_download_200Mbps`	200 Mbps IPv6 TCP download throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a TCP download performance test over IPv6 using a target bandwidth
        of 200 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfDownloadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`220 Mbps IPv6 TCP download throughput test`	`perf_IPv6_TCP_download_220Mbps`	220 Mbps IPv6 TCP download throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a TCP download performance test over IPv6 using a target bandwidth
        of 220 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfDownloadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`240 Mbps IPv6 TCP download throughput test`	`perf_IPv6_TCP_download_240Mbps`	240 Mbps IPv6 TCP download throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a TCP download performance test over IPv6 using a target bandwidth
        of 240 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfDownloadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`260 Mbps IPv6 TCP download throughput test`	`perf_IPv6_TCP_download_260Mbps`	260 Mbps IPv6 TCP download throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a TCP download performance test over IPv6 using a target bandwidth
        of 260 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfDownloadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`280 Mbps IPv6 TCP download throughput test`	`perf_IPv6_TCP_download_280Mbps`	280 Mbps IPv6 TCP download throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a TCP download performance test over IPv6 using a target bandwidth
        of 280 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfDownloadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`300 Mbps IPv6 TCP download throughput test`	`perf_IPv6_TCP_download_300Mbps`	300 Mbps IPv6 TCP download throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a TCP download performance test over IPv6 using a target bandwidth
        of 300 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfDownloadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`320 Mbps IPv6 TCP download throughput test`	`perf_IPv6_TCP_download_320Mbps`	320 Mbps IPv6 TCP download throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a TCP download performance test over IPv6 using a target bandwidth
        of 320 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfDownloadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`340 Mbps IPv6 TCP download throughput test`	`perf_IPv6_TCP_download_340Mbps`	340 Mbps IPv6 TCP download throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a TCP download performance test over IPv6 using a target bandwidth
        of 340 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfDownloadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`360 Mbps IPv6 TCP download throughput test`	`perf_IPv6_TCP_download_360Mbps`	360 Mbps IPv6 TCP download throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a TCP download performance test over IPv6 using a target bandwidth
        of 360 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfDownloadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`380 Mbps IPv6 TCP download throughput test`	`perf_IPv6_TCP_download_380Mbps`	380 Mbps IPv6 TCP download throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a TCP download performance test over IPv6 using a target bandwidth
        of 380 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfDownloadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`400 Mbps IPv6 TCP download throughput test`	`perf_IPv6_TCP_download_400Mbps`	400 Mbps IPv6 TCP download throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a TCP download performance test over IPv6 using a target bandwidth
        of 400 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfDownloadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`420 Mbps IPv6 TCP download throughput test`	`perf_IPv6_TCP_download_420Mbps`	420 Mbps IPv6 TCP download throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a TCP download performance test over IPv6 using a target bandwidth
        of 420 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfDownloadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`440 Mbps IPv6 TCP download throughput test`	`perf_IPv6_TCP_download_440Mbps`	440 Mbps IPv6 TCP download throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a TCP download performance test over IPv6 using a target bandwidth
        of 440 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfDownloadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`460 Mbps IPv6 TCP download throughput test`	`perf_IPv6_TCP_download_460Mbps`	460 Mbps IPv6 TCP download throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a TCP download performance test over IPv6 using a target bandwidth
        of 460 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfDownloadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`480 Mbps IPv6 TCP download throughput test`	`perf_IPv6_TCP_download_480Mbps`	480 Mbps IPv6 TCP download throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a TCP download performance test over IPv6 using a target bandwidth
        of 480 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfDownloadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`500 Mbps IPv6 TCP download throughput test`	`perf_IPv6_TCP_download_500Mbps`	500 Mbps IPv6 TCP download throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a TCP download performance test over IPv6 using a target bandwidth
        of 500 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfDownloadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`520 Mbps IPv6 TCP download throughput test`	`perf_IPv6_TCP_download_520Mbps`	520 Mbps IPv6 TCP download throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a TCP download performance test over IPv6 using a target bandwidth
        of 520 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfDownloadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`540 Mbps IPv6 TCP download throughput test`	`perf_IPv6_TCP_download_540Mbps`	540 Mbps IPv6 TCP download throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a TCP download performance test over IPv6 using a target bandwidth
        of 540 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfDownloadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`560 Mbps IPv6 TCP download throughput test`	`perf_IPv6_TCP_download_560Mbps`	560 Mbps IPv6 TCP download throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a TCP download performance test over IPv6 using a target bandwidth
        of 560 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfDownloadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`580 Mbps IPv6 TCP download throughput test`	`perf_IPv6_TCP_download_580Mbps`	580 Mbps IPv6 TCP download throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a TCP download performance test over IPv6 using a target bandwidth
        of 580 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfDownloadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`600 Mbps IPv6 TCP download throughput test`	`perf_IPv6_TCP_download_600Mbps`	600 Mbps IPv6 TCP download throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a TCP download performance test over IPv6 using a target bandwidth
        of 600 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfDownloadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`620 Mbps IPv6 TCP download throughput test`	`perf_IPv6_TCP_download_620Mbps`	620 Mbps IPv6 TCP download throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a TCP download performance test over IPv6 using a target bandwidth
        of 620 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfDownloadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`640 Mbps IPv6 TCP download throughput test`	`perf_IPv6_TCP_download_640Mbps`	640 Mbps IPv6 TCP download throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a TCP download performance test over IPv6 using a target bandwidth
        of 640 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfDownloadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`660 Mbps IPv6 TCP download throughput test`	`perf_IPv6_TCP_download_660Mbps`	660 Mbps IPv6 TCP download throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a TCP download performance test over IPv6 using a target bandwidth
        of 660 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfDownloadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`680 Mbps IPv6 TCP download throughput test`	`perf_IPv6_TCP_download_680Mbps`	680 Mbps IPv6 TCP download throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a TCP download performance test over IPv6 using a target bandwidth
        of 680 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfDownloadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`700 Mbps IPv6 TCP download throughput test`	`perf_IPv6_TCP_download_700Mbps`	700 Mbps IPv6 TCP download throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a TCP download performance test over IPv6 using a target bandwidth
        of 700 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfDownloadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`720 Mbps IPv6 TCP download throughput test`	`perf_IPv6_TCP_download_720Mbps`	720 Mbps IPv6 TCP download throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a TCP download performance test over IPv6 using a target bandwidth
        of 720 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfDownloadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`740 Mbps IPv6 TCP download throughput test`	`perf_IPv6_TCP_download_740Mbps`	740 Mbps IPv6 TCP download throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a TCP download performance test over IPv6 using a target bandwidth
        of 740 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfDownloadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`760 Mbps IPv6 TCP download throughput test`	`perf_IPv6_TCP_download_760Mbps`	760 Mbps IPv6 TCP download throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a TCP download performance test over IPv6 using a target bandwidth
        of 760 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfDownloadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`780 Mbps IPv6 TCP download throughput test`	`perf_IPv6_TCP_download_780Mbps`	780 Mbps IPv6 TCP download throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a TCP download performance test over IPv6 using a target bandwidth
        of 780 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfDownloadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`800 Mbps IPv6 TCP download throughput test`	`perf_IPv6_TCP_download_800Mbps`	800 Mbps IPv6 TCP download throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a TCP download performance test over IPv6 using a target bandwidth
        of 800 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfDownloadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`820 Mbps IPv6 TCP download throughput test`	`perf_IPv6_TCP_download_820Mbps`	820 Mbps IPv6 TCP download throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a TCP download performance test over IPv6 using a target bandwidth
        of 820 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfDownloadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`840 Mbps IPv6 TCP download throughput test`	`perf_IPv6_TCP_download_840Mbps`	840 Mbps IPv6 TCP download throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a TCP download performance test over IPv6 using a target bandwidth
        of 840 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfDownloadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`860 Mbps IPv6 TCP download throughput test`	`perf_IPv6_TCP_download_860Mbps`	860 Mbps IPv6 TCP download throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a TCP download performance test over IPv6 using a target bandwidth
        of 860 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfDownloadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`880 Mbps IPv6 TCP download throughput test`	`perf_IPv6_TCP_download_880Mbps`	880 Mbps IPv6 TCP download throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a TCP download performance test over IPv6 using a target bandwidth
        of 880 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfDownloadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`900 Mbps IPv6 TCP download throughput test`	`perf_IPv6_TCP_download_900Mbps`	900 Mbps IPv6 TCP download throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a TCP download performance test over IPv6 using a target bandwidth
        of 900 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfDownloadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`920 Mbps IPv6 TCP download throughput test`	`perf_IPv6_TCP_download_920Mbps`	920 Mbps IPv6 TCP download throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a TCP download performance test over IPv6 using a target bandwidth
        of 920 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfDownloadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`940 Mbps IPv6 TCP download throughput test`	`perf_IPv6_TCP_download_940Mbps`	940 Mbps IPv6 TCP download throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a TCP download performance test over IPv6 using a target bandwidth
        of 940 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfDownloadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`960 Mbps IPv6 TCP download throughput test`	`perf_IPv6_TCP_download_960Mbps`	960 Mbps IPv6 TCP download throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a TCP download performance test over IPv6 using a target bandwidth
        of 960 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfDownloadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`20 Mbps IPv6 TCP upload throughput test`	`perf_IPv6_TCP_upload_20Mbps`	20 Mbps IPv6 TCP upload throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a TCP upload performance test over IPv6 using a target bandwidth
        of 20 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfUploadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`40 Mbps IPv6 TCP upload throughput test`	`perf_IPv6_TCP_upload_40Mbps`	40 Mbps IPv6 TCP upload throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a TCP upload performance test over IPv6 using a target bandwidth
        of 40 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfUploadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`60 Mbps IPv6 TCP upload throughput test`	`perf_IPv6_TCP_upload_60Mbps`	60 Mbps IPv6 TCP upload throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a TCP upload performance test over IPv6 using a target bandwidth
        of 60 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfUploadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`80 Mbps IPv6 TCP upload throughput test`	`perf_IPv6_TCP_upload_80Mbps`	80 Mbps IPv6 TCP upload throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a TCP upload performance test over IPv6 using a target bandwidth
        of 80 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfUploadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`100 Mbps IPv6 TCP upload throughput test`	`perf_IPv6_TCP_upload_100Mbps`	100 Mbps IPv6 TCP upload throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a TCP upload performance test over IPv6 using a target bandwidth
        of 100 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfUploadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`120 Mbps IPv6 TCP upload throughput test`	`perf_IPv6_TCP_upload_120Mbps`	120 Mbps IPv6 TCP upload throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a TCP upload performance test over IPv6 using a target bandwidth
        of 120 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfUploadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`140 Mbps IPv6 TCP upload throughput test`	`perf_IPv6_TCP_upload_140Mbps`	140 Mbps IPv6 TCP upload throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a TCP upload performance test over IPv6 using a target bandwidth
        of 140 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfUploadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`160 Mbps IPv6 TCP upload throughput test`	`perf_IPv6_TCP_upload_160Mbps`	160 Mbps IPv6 TCP upload throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a TCP upload performance test over IPv6 using a target bandwidth
        of 160 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfUploadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`180 Mbps IPv6 TCP upload throughput test`	`perf_IPv6_TCP_upload_180Mbps`	180 Mbps IPv6 TCP upload throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a TCP upload performance test over IPv6 using a target bandwidth
        of 180 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfUploadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`200 Mbps IPv6 TCP upload throughput test`	`perf_IPv6_TCP_upload_200Mbps`	200 Mbps IPv6 TCP upload throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a TCP upload performance test over IPv6 using a target bandwidth
        of 200 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfUploadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`220 Mbps IPv6 TCP upload throughput test`	`perf_IPv6_TCP_upload_220Mbps`	220 Mbps IPv6 TCP upload throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a TCP upload performance test over IPv6 using a target bandwidth
        of 220 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfUploadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`240 Mbps IPv6 TCP upload throughput test`	`perf_IPv6_TCP_upload_240Mbps`	240 Mbps IPv6 TCP upload throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a TCP upload performance test over IPv6 using a target bandwidth
        of 240 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfUploadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`260 Mbps IPv6 TCP upload throughput test`	`perf_IPv6_TCP_upload_260Mbps`	260 Mbps IPv6 TCP upload throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a TCP upload performance test over IPv6 using a target bandwidth
        of 260 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfUploadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`280 Mbps IPv6 TCP upload throughput test`	`perf_IPv6_TCP_upload_280Mbps`	280 Mbps IPv6 TCP upload throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a TCP upload performance test over IPv6 using a target bandwidth
        of 280 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfUploadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`300 Mbps IPv6 TCP upload throughput test`	`perf_IPv6_TCP_upload_300Mbps`	300 Mbps IPv6 TCP upload throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a TCP upload performance test over IPv6 using a target bandwidth
        of 300 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfUploadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`320 Mbps IPv6 TCP upload throughput test`	`perf_IPv6_TCP_upload_320Mbps`	320 Mbps IPv6 TCP upload throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a TCP upload performance test over IPv6 using a target bandwidth
        of 320 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfUploadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`340 Mbps IPv6 TCP upload throughput test`	`perf_IPv6_TCP_upload_340Mbps`	340 Mbps IPv6 TCP upload throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a TCP upload performance test over IPv6 using a target bandwidth
        of 340 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfUploadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`360 Mbps IPv6 TCP upload throughput test`	`perf_IPv6_TCP_upload_360Mbps`	360 Mbps IPv6 TCP upload throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a TCP upload performance test over IPv6 using a target bandwidth
        of 360 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfUploadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`380 Mbps IPv6 TCP upload throughput test`	`perf_IPv6_TCP_upload_380Mbps`	380 Mbps IPv6 TCP upload throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a TCP upload performance test over IPv6 using a target bandwidth
        of 380 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfUploadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`400 Mbps IPv6 TCP upload throughput test`	`perf_IPv6_TCP_upload_400Mbps`	400 Mbps IPv6 TCP upload throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a TCP upload performance test over IPv6 using a target bandwidth
        of 400 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfUploadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`420 Mbps IPv6 TCP upload throughput test`	`perf_IPv6_TCP_upload_420Mbps`	420 Mbps IPv6 TCP upload throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a TCP upload performance test over IPv6 using a target bandwidth
        of 420 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfUploadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`440 Mbps IPv6 TCP upload throughput test`	`perf_IPv6_TCP_upload_440Mbps`	440 Mbps IPv6 TCP upload throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a TCP upload performance test over IPv6 using a target bandwidth
        of 440 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfUploadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`460 Mbps IPv6 TCP upload throughput test`	`perf_IPv6_TCP_upload_460Mbps`	460 Mbps IPv6 TCP upload throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a TCP upload performance test over IPv6 using a target bandwidth
        of 460 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfUploadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`480 Mbps IPv6 TCP upload throughput test`	`perf_IPv6_TCP_upload_480Mbps`	480 Mbps IPv6 TCP upload throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a TCP upload performance test over IPv6 using a target bandwidth
        of 480 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfUploadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`500 Mbps IPv6 TCP upload throughput test`	`perf_IPv6_TCP_upload_500Mbps`	500 Mbps IPv6 TCP upload throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a TCP upload performance test over IPv6 using a target bandwidth
        of 500 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfUploadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`520 Mbps IPv6 TCP upload throughput test`	`perf_IPv6_TCP_upload_520Mbps`	520 Mbps IPv6 TCP upload throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a TCP upload performance test over IPv6 using a target bandwidth
        of 520 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfUploadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`540 Mbps IPv6 TCP upload throughput test`	`perf_IPv6_TCP_upload_540Mbps`	540 Mbps IPv6 TCP upload throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a TCP upload performance test over IPv6 using a target bandwidth
        of 540 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfUploadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`560 Mbps IPv6 TCP upload throughput test`	`perf_IPv6_TCP_upload_560Mbps`	560 Mbps IPv6 TCP upload throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a TCP upload performance test over IPv6 using a target bandwidth
        of 560 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfUploadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`580 Mbps IPv6 TCP upload throughput test`	`perf_IPv6_TCP_upload_580Mbps`	580 Mbps IPv6 TCP upload throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a TCP upload performance test over IPv6 using a target bandwidth
        of 580 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfUploadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`600 Mbps IPv6 TCP upload throughput test`	`perf_IPv6_TCP_upload_600Mbps`	600 Mbps IPv6 TCP upload throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a TCP upload performance test over IPv6 using a target bandwidth
        of 600 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfUploadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`620 Mbps IPv6 TCP upload throughput test`	`perf_IPv6_TCP_upload_620Mbps`	620 Mbps IPv6 TCP upload throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a TCP upload performance test over IPv6 using a target bandwidth
        of 620 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfUploadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`640 Mbps IPv6 TCP upload throughput test`	`perf_IPv6_TCP_upload_640Mbps`	640 Mbps IPv6 TCP upload throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a TCP upload performance test over IPv6 using a target bandwidth
        of 640 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfUploadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`660 Mbps IPv6 TCP upload throughput test`	`perf_IPv6_TCP_upload_660Mbps`	660 Mbps IPv6 TCP upload throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a TCP upload performance test over IPv6 using a target bandwidth
        of 660 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfUploadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`680 Mbps IPv6 TCP upload throughput test`	`perf_IPv6_TCP_upload_680Mbps`	680 Mbps IPv6 TCP upload throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a TCP upload performance test over IPv6 using a target bandwidth
        of 680 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfUploadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`700 Mbps IPv6 TCP upload throughput test`	`perf_IPv6_TCP_upload_700Mbps`	700 Mbps IPv6 TCP upload throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a TCP upload performance test over IPv6 using a target bandwidth
        of 700 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfUploadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`720 Mbps IPv6 TCP upload throughput test`	`perf_IPv6_TCP_upload_720Mbps`	720 Mbps IPv6 TCP upload throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a TCP upload performance test over IPv6 using a target bandwidth
        of 720 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfUploadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`740 Mbps IPv6 TCP upload throughput test`	`perf_IPv6_TCP_upload_740Mbps`	740 Mbps IPv6 TCP upload throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a TCP upload performance test over IPv6 using a target bandwidth
        of 740 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfUploadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`760 Mbps IPv6 TCP upload throughput test`	`perf_IPv6_TCP_upload_760Mbps`	760 Mbps IPv6 TCP upload throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a TCP upload performance test over IPv6 using a target bandwidth
        of 760 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfUploadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`780 Mbps IPv6 TCP upload throughput test`	`perf_IPv6_TCP_upload_780Mbps`	780 Mbps IPv6 TCP upload throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a TCP upload performance test over IPv6 using a target bandwidth
        of 780 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfUploadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`800 Mbps IPv6 TCP upload throughput test`	`perf_IPv6_TCP_upload_800Mbps`	800 Mbps IPv6 TCP upload throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a TCP upload performance test over IPv6 using a target bandwidth
        of 800 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfUploadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`820 Mbps IPv6 TCP upload throughput test`	`perf_IPv6_TCP_upload_820Mbps`	820 Mbps IPv6 TCP upload throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a TCP upload performance test over IPv6 using a target bandwidth
        of 820 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfUploadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`840 Mbps IPv6 TCP upload throughput test`	`perf_IPv6_TCP_upload_840Mbps`	840 Mbps IPv6 TCP upload throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a TCP upload performance test over IPv6 using a target bandwidth
        of 840 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfUploadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`860 Mbps IPv6 TCP upload throughput test`	`perf_IPv6_TCP_upload_860Mbps`	860 Mbps IPv6 TCP upload throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a TCP upload performance test over IPv6 using a target bandwidth
        of 860 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfUploadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`880 Mbps IPv6 TCP upload throughput test`	`perf_IPv6_TCP_upload_880Mbps`	880 Mbps IPv6 TCP upload throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a TCP upload performance test over IPv6 using a target bandwidth
        of 880 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfUploadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`900 Mbps IPv6 TCP upload throughput test`	`perf_IPv6_TCP_upload_900Mbps`	900 Mbps IPv6 TCP upload throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a TCP upload performance test over IPv6 using a target bandwidth
        of 900 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfUploadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`920 Mbps IPv6 TCP upload throughput test`	`perf_IPv6_TCP_upload_920Mbps`	920 Mbps IPv6 TCP upload throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a TCP upload performance test over IPv6 using a target bandwidth
        of 920 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfUploadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`940 Mbps IPv6 TCP upload throughput test`	`perf_IPv6_TCP_upload_940Mbps`	940 Mbps IPv6 TCP upload throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a TCP upload performance test over IPv6 using a target bandwidth
        of 940 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfUploadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`960 Mbps IPv6 TCP upload throughput test`	`perf_IPv6_TCP_upload_960Mbps`	960 Mbps IPv6 TCP upload throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a TCP upload performance test over IPv6 using a target bandwidth
        of 960 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfUploadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`20 Mbps IPv6 UDP download throughput test`	`perf_IPv6_UDP_download_20Mbps`	20 Mbps IPv6 UDP download throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a UDP download performance test over IPv6 using a target bandwidth
        of 20 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfDownloadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`40 Mbps IPv6 UDP download throughput test`	`perf_IPv6_UDP_download_40Mbps`	40 Mbps IPv6 UDP download throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a UDP download performance test over IPv6 using a target bandwidth
        of 40 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfDownloadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`60 Mbps IPv6 UDP download throughput test`	`perf_IPv6_UDP_download_60Mbps`	60 Mbps IPv6 UDP download throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a UDP download performance test over IPv6 using a target bandwidth
        of 60 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfDownloadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`80 Mbps IPv6 UDP download throughput test`	`perf_IPv6_UDP_download_80Mbps`	80 Mbps IPv6 UDP download throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a UDP download performance test over IPv6 using a target bandwidth
        of 80 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfDownloadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`100 Mbps IPv6 UDP download throughput test`	`perf_IPv6_UDP_download_100Mbps`	100 Mbps IPv6 UDP download throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a UDP download performance test over IPv6 using a target bandwidth
        of 100 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfDownloadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`120 Mbps IPv6 UDP download throughput test`	`perf_IPv6_UDP_download_120Mbps`	120 Mbps IPv6 UDP download throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a UDP download performance test over IPv6 using a target bandwidth
        of 120 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfDownloadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`140 Mbps IPv6 UDP download throughput test`	`perf_IPv6_UDP_download_140Mbps`	140 Mbps IPv6 UDP download throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a UDP download performance test over IPv6 using a target bandwidth
        of 140 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfDownloadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`160 Mbps IPv6 UDP download throughput test`	`perf_IPv6_UDP_download_160Mbps`	160 Mbps IPv6 UDP download throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a UDP download performance test over IPv6 using a target bandwidth
        of 160 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfDownloadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`180 Mbps IPv6 UDP download throughput test`	`perf_IPv6_UDP_download_180Mbps`	180 Mbps IPv6 UDP download throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a UDP download performance test over IPv6 using a target bandwidth
        of 180 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfDownloadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`200 Mbps IPv6 UDP download throughput test`	`perf_IPv6_UDP_download_200Mbps`	200 Mbps IPv6 UDP download throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a UDP download performance test over IPv6 using a target bandwidth
        of 200 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfDownloadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`220 Mbps IPv6 UDP download throughput test`	`perf_IPv6_UDP_download_220Mbps`	220 Mbps IPv6 UDP download throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a UDP download performance test over IPv6 using a target bandwidth
        of 220 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfDownloadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`240 Mbps IPv6 UDP download throughput test`	`perf_IPv6_UDP_download_240Mbps`	240 Mbps IPv6 UDP download throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a UDP download performance test over IPv6 using a target bandwidth
        of 240 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfDownloadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`260 Mbps IPv6 UDP download throughput test`	`perf_IPv6_UDP_download_260Mbps`	260 Mbps IPv6 UDP download throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a UDP download performance test over IPv6 using a target bandwidth
        of 260 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfDownloadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`280 Mbps IPv6 UDP download throughput test`	`perf_IPv6_UDP_download_280Mbps`	280 Mbps IPv6 UDP download throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a UDP download performance test over IPv6 using a target bandwidth
        of 280 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfDownloadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`300 Mbps IPv6 UDP download throughput test`	`perf_IPv6_UDP_download_300Mbps`	300 Mbps IPv6 UDP download throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a UDP download performance test over IPv6 using a target bandwidth
        of 300 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfDownloadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`320 Mbps IPv6 UDP download throughput test`	`perf_IPv6_UDP_download_320Mbps`	320 Mbps IPv6 UDP download throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a UDP download performance test over IPv6 using a target bandwidth
        of 320 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfDownloadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`340 Mbps IPv6 UDP download throughput test`	`perf_IPv6_UDP_download_340Mbps`	340 Mbps IPv6 UDP download throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a UDP download performance test over IPv6 using a target bandwidth
        of 340 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfDownloadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`360 Mbps IPv6 UDP download throughput test`	`perf_IPv6_UDP_download_360Mbps`	360 Mbps IPv6 UDP download throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a UDP download performance test over IPv6 using a target bandwidth
        of 360 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfDownloadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`380 Mbps IPv6 UDP download throughput test`	`perf_IPv6_UDP_download_380Mbps`	380 Mbps IPv6 UDP download throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a UDP download performance test over IPv6 using a target bandwidth
        of 380 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfDownloadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`400 Mbps IPv6 UDP download throughput test`	`perf_IPv6_UDP_download_400Mbps`	400 Mbps IPv6 UDP download throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a UDP download performance test over IPv6 using a target bandwidth
        of 400 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfDownloadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`420 Mbps IPv6 UDP download throughput test`	`perf_IPv6_UDP_download_420Mbps`	420 Mbps IPv6 UDP download throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a UDP download performance test over IPv6 using a target bandwidth
        of 420 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfDownloadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`440 Mbps IPv6 UDP download throughput test`	`perf_IPv6_UDP_download_440Mbps`	440 Mbps IPv6 UDP download throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a UDP download performance test over IPv6 using a target bandwidth
        of 440 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfDownloadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`460 Mbps IPv6 UDP download throughput test`	`perf_IPv6_UDP_download_460Mbps`	460 Mbps IPv6 UDP download throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a UDP download performance test over IPv6 using a target bandwidth
        of 460 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfDownloadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`480 Mbps IPv6 UDP download throughput test`	`perf_IPv6_UDP_download_480Mbps`	480 Mbps IPv6 UDP download throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a UDP download performance test over IPv6 using a target bandwidth
        of 480 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfDownloadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`500 Mbps IPv6 UDP download throughput test`	`perf_IPv6_UDP_download_500Mbps`	500 Mbps IPv6 UDP download throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a UDP download performance test over IPv6 using a target bandwidth
        of 500 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfDownloadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`520 Mbps IPv6 UDP download throughput test`	`perf_IPv6_UDP_download_520Mbps`	520 Mbps IPv6 UDP download throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a UDP download performance test over IPv6 using a target bandwidth
        of 520 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfDownloadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`540 Mbps IPv6 UDP download throughput test`	`perf_IPv6_UDP_download_540Mbps`	540 Mbps IPv6 UDP download throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a UDP download performance test over IPv6 using a target bandwidth
        of 540 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfDownloadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`560 Mbps IPv6 UDP download throughput test`	`perf_IPv6_UDP_download_560Mbps`	560 Mbps IPv6 UDP download throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a UDP download performance test over IPv6 using a target bandwidth
        of 560 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfDownloadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`580 Mbps IPv6 UDP download throughput test`	`perf_IPv6_UDP_download_580Mbps`	580 Mbps IPv6 UDP download throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a UDP download performance test over IPv6 using a target bandwidth
        of 580 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfDownloadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`600 Mbps IPv6 UDP download throughput test`	`perf_IPv6_UDP_download_600Mbps`	600 Mbps IPv6 UDP download throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a UDP download performance test over IPv6 using a target bandwidth
        of 600 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfDownloadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`620 Mbps IPv6 UDP download throughput test`	`perf_IPv6_UDP_download_620Mbps`	620 Mbps IPv6 UDP download throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a UDP download performance test over IPv6 using a target bandwidth
        of 620 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfDownloadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`640 Mbps IPv6 UDP download throughput test`	`perf_IPv6_UDP_download_640Mbps`	640 Mbps IPv6 UDP download throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a UDP download performance test over IPv6 using a target bandwidth
        of 640 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfDownloadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`660 Mbps IPv6 UDP download throughput test`	`perf_IPv6_UDP_download_660Mbps`	660 Mbps IPv6 UDP download throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a UDP download performance test over IPv6 using a target bandwidth
        of 660 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfDownloadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`680 Mbps IPv6 UDP download throughput test`	`perf_IPv6_UDP_download_680Mbps`	680 Mbps IPv6 UDP download throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a UDP download performance test over IPv6 using a target bandwidth
        of 680 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfDownloadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`700 Mbps IPv6 UDP download throughput test`	`perf_IPv6_UDP_download_700Mbps`	700 Mbps IPv6 UDP download throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a UDP download performance test over IPv6 using a target bandwidth
        of 700 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfDownloadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`720 Mbps IPv6 UDP download throughput test`	`perf_IPv6_UDP_download_720Mbps`	720 Mbps IPv6 UDP download throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a UDP download performance test over IPv6 using a target bandwidth
        of 720 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfDownloadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`740 Mbps IPv6 UDP download throughput test`	`perf_IPv6_UDP_download_740Mbps`	740 Mbps IPv6 UDP download throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a UDP download performance test over IPv6 using a target bandwidth
        of 740 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfDownloadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`760 Mbps IPv6 UDP download throughput test`	`perf_IPv6_UDP_download_760Mbps`	760 Mbps IPv6 UDP download throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a UDP download performance test over IPv6 using a target bandwidth
        of 760 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfDownloadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`780 Mbps IPv6 UDP download throughput test`	`perf_IPv6_UDP_download_780Mbps`	780 Mbps IPv6 UDP download throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a UDP download performance test over IPv6 using a target bandwidth
        of 780 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfDownloadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`800 Mbps IPv6 UDP download throughput test`	`perf_IPv6_UDP_download_800Mbps`	800 Mbps IPv6 UDP download throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a UDP download performance test over IPv6 using a target bandwidth
        of 800 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfDownloadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`820 Mbps IPv6 UDP download throughput test`	`perf_IPv6_UDP_download_820Mbps`	820 Mbps IPv6 UDP download throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a UDP download performance test over IPv6 using a target bandwidth
        of 820 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfDownloadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`840 Mbps IPv6 UDP download throughput test`	`perf_IPv6_UDP_download_840Mbps`	840 Mbps IPv6 UDP download throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a UDP download performance test over IPv6 using a target bandwidth
        of 840 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfDownloadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`860 Mbps IPv6 UDP download throughput test`	`perf_IPv6_UDP_download_860Mbps`	860 Mbps IPv6 UDP download throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a UDP download performance test over IPv6 using a target bandwidth
        of 860 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfDownloadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`880 Mbps IPv6 UDP download throughput test`	`perf_IPv6_UDP_download_880Mbps`	880 Mbps IPv6 UDP download throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a UDP download performance test over IPv6 using a target bandwidth
        of 880 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfDownloadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`900 Mbps IPv6 UDP download throughput test`	`perf_IPv6_UDP_download_900Mbps`	900 Mbps IPv6 UDP download throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a UDP download performance test over IPv6 using a target bandwidth
        of 900 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfDownloadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`920 Mbps IPv6 UDP download throughput test`	`perf_IPv6_UDP_download_920Mbps`	920 Mbps IPv6 UDP download throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a UDP download performance test over IPv6 using a target bandwidth
        of 920 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfDownloadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`940 Mbps IPv6 UDP download throughput test`	`perf_IPv6_UDP_download_940Mbps`	940 Mbps IPv6 UDP download throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a UDP download performance test over IPv6 using a target bandwidth
        of 940 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfDownloadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`960 Mbps IPv6 UDP download throughput test`	`perf_IPv6_UDP_download_960Mbps`	960 Mbps IPv6 UDP download throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a UDP download performance test over IPv6 using a target bandwidth
        of 960 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfDownloadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`20 Mbps IPv6 UDP upload throughput test`	`perf_IPv6_UDP_upload_20Mbps`	20 Mbps IPv6 UDP upload throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a UDP upload performance test over IPv6 using a target bandwidth
        of 20 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfUploadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`40 Mbps IPv6 UDP upload throughput test`	`perf_IPv6_UDP_upload_40Mbps`	40 Mbps IPv6 UDP upload throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a UDP upload performance test over IPv6 using a target bandwidth
        of 40 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfUploadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`60 Mbps IPv6 UDP upload throughput test`	`perf_IPv6_UDP_upload_60Mbps`	60 Mbps IPv6 UDP upload throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a UDP upload performance test over IPv6 using a target bandwidth
        of 60 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfUploadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`80 Mbps IPv6 UDP upload throughput test`	`perf_IPv6_UDP_upload_80Mbps`	80 Mbps IPv6 UDP upload throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a UDP upload performance test over IPv6 using a target bandwidth
        of 80 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfUploadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`100 Mbps IPv6 UDP upload throughput test`	`perf_IPv6_UDP_upload_100Mbps`	100 Mbps IPv6 UDP upload throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a UDP upload performance test over IPv6 using a target bandwidth
        of 100 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfUploadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`120 Mbps IPv6 UDP upload throughput test`	`perf_IPv6_UDP_upload_120Mbps`	120 Mbps IPv6 UDP upload throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a UDP upload performance test over IPv6 using a target bandwidth
        of 120 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfUploadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`140 Mbps IPv6 UDP upload throughput test`	`perf_IPv6_UDP_upload_140Mbps`	140 Mbps IPv6 UDP upload throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a UDP upload performance test over IPv6 using a target bandwidth
        of 140 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfUploadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`160 Mbps IPv6 UDP upload throughput test`	`perf_IPv6_UDP_upload_160Mbps`	160 Mbps IPv6 UDP upload throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a UDP upload performance test over IPv6 using a target bandwidth
        of 160 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfUploadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`180 Mbps IPv6 UDP upload throughput test`	`perf_IPv6_UDP_upload_180Mbps`	180 Mbps IPv6 UDP upload throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a UDP upload performance test over IPv6 using a target bandwidth
        of 180 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfUploadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`200 Mbps IPv6 UDP upload throughput test`	`perf_IPv6_UDP_upload_200Mbps`	200 Mbps IPv6 UDP upload throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a UDP upload performance test over IPv6 using a target bandwidth
        of 200 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfUploadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`220 Mbps IPv6 UDP upload throughput test`	`perf_IPv6_UDP_upload_220Mbps`	220 Mbps IPv6 UDP upload throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a UDP upload performance test over IPv6 using a target bandwidth
        of 220 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfUploadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`240 Mbps IPv6 UDP upload throughput test`	`perf_IPv6_UDP_upload_240Mbps`	240 Mbps IPv6 UDP upload throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a UDP upload performance test over IPv6 using a target bandwidth
        of 240 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfUploadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`260 Mbps IPv6 UDP upload throughput test`	`perf_IPv6_UDP_upload_260Mbps`	260 Mbps IPv6 UDP upload throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a UDP upload performance test over IPv6 using a target bandwidth
        of 260 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfUploadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`280 Mbps IPv6 UDP upload throughput test`	`perf_IPv6_UDP_upload_280Mbps`	280 Mbps IPv6 UDP upload throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a UDP upload performance test over IPv6 using a target bandwidth
        of 280 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfUploadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`300 Mbps IPv6 UDP upload throughput test`	`perf_IPv6_UDP_upload_300Mbps`	300 Mbps IPv6 UDP upload throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a UDP upload performance test over IPv6 using a target bandwidth
        of 300 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfUploadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`320 Mbps IPv6 UDP upload throughput test`	`perf_IPv6_UDP_upload_320Mbps`	320 Mbps IPv6 UDP upload throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a UDP upload performance test over IPv6 using a target bandwidth
        of 320 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfUploadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`340 Mbps IPv6 UDP upload throughput test`	`perf_IPv6_UDP_upload_340Mbps`	340 Mbps IPv6 UDP upload throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a UDP upload performance test over IPv6 using a target bandwidth
        of 340 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfUploadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`360 Mbps IPv6 UDP upload throughput test`	`perf_IPv6_UDP_upload_360Mbps`	360 Mbps IPv6 UDP upload throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a UDP upload performance test over IPv6 using a target bandwidth
        of 360 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfUploadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`380 Mbps IPv6 UDP upload throughput test`	`perf_IPv6_UDP_upload_380Mbps`	380 Mbps IPv6 UDP upload throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a UDP upload performance test over IPv6 using a target bandwidth
        of 380 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfUploadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`400 Mbps IPv6 UDP upload throughput test`	`perf_IPv6_UDP_upload_400Mbps`	400 Mbps IPv6 UDP upload throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a UDP upload performance test over IPv6 using a target bandwidth
        of 400 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfUploadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`420 Mbps IPv6 UDP upload throughput test`	`perf_IPv6_UDP_upload_420Mbps`	420 Mbps IPv6 UDP upload throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a UDP upload performance test over IPv6 using a target bandwidth
        of 420 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfUploadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`440 Mbps IPv6 UDP upload throughput test`	`perf_IPv6_UDP_upload_440Mbps`	440 Mbps IPv6 UDP upload throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a UDP upload performance test over IPv6 using a target bandwidth
        of 440 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfUploadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`460 Mbps IPv6 UDP upload throughput test`	`perf_IPv6_UDP_upload_460Mbps`	460 Mbps IPv6 UDP upload throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a UDP upload performance test over IPv6 using a target bandwidth
        of 460 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfUploadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`480 Mbps IPv6 UDP upload throughput test`	`perf_IPv6_UDP_upload_480Mbps`	480 Mbps IPv6 UDP upload throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a UDP upload performance test over IPv6 using a target bandwidth
        of 480 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfUploadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`500 Mbps IPv6 UDP upload throughput test`	`perf_IPv6_UDP_upload_500Mbps`	500 Mbps IPv6 UDP upload throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a UDP upload performance test over IPv6 using a target bandwidth
        of 500 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfUploadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`520 Mbps IPv6 UDP upload throughput test`	`perf_IPv6_UDP_upload_520Mbps`	520 Mbps IPv6 UDP upload throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a UDP upload performance test over IPv6 using a target bandwidth
        of 520 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfUploadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`540 Mbps IPv6 UDP upload throughput test`	`perf_IPv6_UDP_upload_540Mbps`	540 Mbps IPv6 UDP upload throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a UDP upload performance test over IPv6 using a target bandwidth
        of 540 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfUploadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`560 Mbps IPv6 UDP upload throughput test`	`perf_IPv6_UDP_upload_560Mbps`	560 Mbps IPv6 UDP upload throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a UDP upload performance test over IPv6 using a target bandwidth
        of 560 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfUploadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`580 Mbps IPv6 UDP upload throughput test`	`perf_IPv6_UDP_upload_580Mbps`	580 Mbps IPv6 UDP upload throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a UDP upload performance test over IPv6 using a target bandwidth
        of 580 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfUploadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`600 Mbps IPv6 UDP upload throughput test`	`perf_IPv6_UDP_upload_600Mbps`	600 Mbps IPv6 UDP upload throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a UDP upload performance test over IPv6 using a target bandwidth
        of 600 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfUploadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`620 Mbps IPv6 UDP upload throughput test`	`perf_IPv6_UDP_upload_620Mbps`	620 Mbps IPv6 UDP upload throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a UDP upload performance test over IPv6 using a target bandwidth
        of 620 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfUploadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`640 Mbps IPv6 UDP upload throughput test`	`perf_IPv6_UDP_upload_640Mbps`	640 Mbps IPv6 UDP upload throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a UDP upload performance test over IPv6 using a target bandwidth
        of 640 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfUploadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`660 Mbps IPv6 UDP upload throughput test`	`perf_IPv6_UDP_upload_660Mbps`	660 Mbps IPv6 UDP upload throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a UDP upload performance test over IPv6 using a target bandwidth
        of 660 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfUploadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`680 Mbps IPv6 UDP upload throughput test`	`perf_IPv6_UDP_upload_680Mbps`	680 Mbps IPv6 UDP upload throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a UDP upload performance test over IPv6 using a target bandwidth
        of 680 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfUploadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`700 Mbps IPv6 UDP upload throughput test`	`perf_IPv6_UDP_upload_700Mbps`	700 Mbps IPv6 UDP upload throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a UDP upload performance test over IPv6 using a target bandwidth
        of 700 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfUploadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`720 Mbps IPv6 UDP upload throughput test`	`perf_IPv6_UDP_upload_720Mbps`	720 Mbps IPv6 UDP upload throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a UDP upload performance test over IPv6 using a target bandwidth
        of 720 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfUploadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`740 Mbps IPv6 UDP upload throughput test`	`perf_IPv6_UDP_upload_740Mbps`	740 Mbps IPv6 UDP upload throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a UDP upload performance test over IPv6 using a target bandwidth
        of 740 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfUploadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`760 Mbps IPv6 UDP upload throughput test`	`perf_IPv6_UDP_upload_760Mbps`	760 Mbps IPv6 UDP upload throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a UDP upload performance test over IPv6 using a target bandwidth
        of 760 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfUploadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`780 Mbps IPv6 UDP upload throughput test`	`perf_IPv6_UDP_upload_780Mbps`	780 Mbps IPv6 UDP upload throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a UDP upload performance test over IPv6 using a target bandwidth
        of 780 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfUploadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`800 Mbps IPv6 UDP upload throughput test`	`perf_IPv6_UDP_upload_800Mbps`	800 Mbps IPv6 UDP upload throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a UDP upload performance test over IPv6 using a target bandwidth
        of 800 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfUploadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`820 Mbps IPv6 UDP upload throughput test`	`perf_IPv6_UDP_upload_820Mbps`	820 Mbps IPv6 UDP upload throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a UDP upload performance test over IPv6 using a target bandwidth
        of 820 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfUploadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`840 Mbps IPv6 UDP upload throughput test`	`perf_IPv6_UDP_upload_840Mbps`	840 Mbps IPv6 UDP upload throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a UDP upload performance test over IPv6 using a target bandwidth
        of 840 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfUploadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`860 Mbps IPv6 UDP upload throughput test`	`perf_IPv6_UDP_upload_860Mbps`	860 Mbps IPv6 UDP upload throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a UDP upload performance test over IPv6 using a target bandwidth
        of 860 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfUploadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`880 Mbps IPv6 UDP upload throughput test`	`perf_IPv6_UDP_upload_880Mbps`	880 Mbps IPv6 UDP upload throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a UDP upload performance test over IPv6 using a target bandwidth
        of 880 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfUploadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`900 Mbps IPv6 UDP upload throughput test`	`perf_IPv6_UDP_upload_900Mbps`	900 Mbps IPv6 UDP upload throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a UDP upload performance test over IPv6 using a target bandwidth
        of 900 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfUploadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`920 Mbps IPv6 UDP upload throughput test`	`perf_IPv6_UDP_upload_920Mbps`	920 Mbps IPv6 UDP upload throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a UDP upload performance test over IPv6 using a target bandwidth
        of 920 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfUploadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`940 Mbps IPv6 UDP upload throughput test`	`perf_IPv6_UDP_upload_940Mbps`	940 Mbps IPv6 UDP upload throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a UDP upload performance test over IPv6 using a target bandwidth
        of 940 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfUploadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`960 Mbps IPv6 UDP upload throughput test`	`perf_IPv6_UDP_upload_960Mbps`	960 Mbps IPv6 UDP upload throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a UDP upload performance test over IPv6 using a target bandwidth
        of 960 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfUploadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

`fixed-rate-perf-2-5.tcl`

IPv4 fixed rate performance tests, 1 to 2.5 Gbps

Test	Name	Synopsis
`980 Mbps IPv4 TCP download throughput test`	`perf_IPv4_TCP_download_980Mbps`	980 Mbps IPv4 TCP download throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a TCP download performance test over IPv4 using a target bandwidth
        of 980 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfDownloadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`1000 Mbps IPv4 TCP download throughput test`	`perf_IPv4_TCP_download_1000Mbps`	1000 Mbps IPv4 TCP download throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a TCP download performance test over IPv4 using a target bandwidth
        of 1000 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfDownloadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`1020 Mbps IPv4 TCP download throughput test`	`perf_IPv4_TCP_download_1020Mbps`	1020 Mbps IPv4 TCP download throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a TCP download performance test over IPv4 using a target bandwidth
        of 1020 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfDownloadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`1040 Mbps IPv4 TCP download throughput test`	`perf_IPv4_TCP_download_1040Mbps`	1040 Mbps IPv4 TCP download throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a TCP download performance test over IPv4 using a target bandwidth
        of 1040 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfDownloadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`1060 Mbps IPv4 TCP download throughput test`	`perf_IPv4_TCP_download_1060Mbps`	1060 Mbps IPv4 TCP download throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a TCP download performance test over IPv4 using a target bandwidth
        of 1060 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfDownloadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`1080 Mbps IPv4 TCP download throughput test`	`perf_IPv4_TCP_download_1080Mbps`	1080 Mbps IPv4 TCP download throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a TCP download performance test over IPv4 using a target bandwidth
        of 1080 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfDownloadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`1100 Mbps IPv4 TCP download throughput test`	`perf_IPv4_TCP_download_1100Mbps`	1100 Mbps IPv4 TCP download throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a TCP download performance test over IPv4 using a target bandwidth
        of 1100 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfDownloadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`1120 Mbps IPv4 TCP download throughput test`	`perf_IPv4_TCP_download_1120Mbps`	1120 Mbps IPv4 TCP download throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a TCP download performance test over IPv4 using a target bandwidth
        of 1120 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfDownloadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`1140 Mbps IPv4 TCP download throughput test`	`perf_IPv4_TCP_download_1140Mbps`	1140 Mbps IPv4 TCP download throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a TCP download performance test over IPv4 using a target bandwidth
        of 1140 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfDownloadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`1160 Mbps IPv4 TCP download throughput test`	`perf_IPv4_TCP_download_1160Mbps`	1160 Mbps IPv4 TCP download throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a TCP download performance test over IPv4 using a target bandwidth
        of 1160 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfDownloadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`1180 Mbps IPv4 TCP download throughput test`	`perf_IPv4_TCP_download_1180Mbps`	1180 Mbps IPv4 TCP download throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a TCP download performance test over IPv4 using a target bandwidth
        of 1180 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfDownloadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`1200 Mbps IPv4 TCP download throughput test`	`perf_IPv4_TCP_download_1200Mbps`	1200 Mbps IPv4 TCP download throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a TCP download performance test over IPv4 using a target bandwidth
        of 1200 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfDownloadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`1220 Mbps IPv4 TCP download throughput test`	`perf_IPv4_TCP_download_1220Mbps`	1220 Mbps IPv4 TCP download throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a TCP download performance test over IPv4 using a target bandwidth
        of 1220 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfDownloadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`1240 Mbps IPv4 TCP download throughput test`	`perf_IPv4_TCP_download_1240Mbps`	1240 Mbps IPv4 TCP download throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a TCP download performance test over IPv4 using a target bandwidth
        of 1240 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfDownloadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`1260 Mbps IPv4 TCP download throughput test`	`perf_IPv4_TCP_download_1260Mbps`	1260 Mbps IPv4 TCP download throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a TCP download performance test over IPv4 using a target bandwidth
        of 1260 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfDownloadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`1280 Mbps IPv4 TCP download throughput test`	`perf_IPv4_TCP_download_1280Mbps`	1280 Mbps IPv4 TCP download throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a TCP download performance test over IPv4 using a target bandwidth
        of 1280 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfDownloadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`1300 Mbps IPv4 TCP download throughput test`	`perf_IPv4_TCP_download_1300Mbps`	1300 Mbps IPv4 TCP download throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a TCP download performance test over IPv4 using a target bandwidth
        of 1300 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfDownloadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`1320 Mbps IPv4 TCP download throughput test`	`perf_IPv4_TCP_download_1320Mbps`	1320 Mbps IPv4 TCP download throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a TCP download performance test over IPv4 using a target bandwidth
        of 1320 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfDownloadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`1340 Mbps IPv4 TCP download throughput test`	`perf_IPv4_TCP_download_1340Mbps`	1340 Mbps IPv4 TCP download throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a TCP download performance test over IPv4 using a target bandwidth
        of 1340 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfDownloadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`1360 Mbps IPv4 TCP download throughput test`	`perf_IPv4_TCP_download_1360Mbps`	1360 Mbps IPv4 TCP download throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a TCP download performance test over IPv4 using a target bandwidth
        of 1360 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfDownloadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`1380 Mbps IPv4 TCP download throughput test`	`perf_IPv4_TCP_download_1380Mbps`	1380 Mbps IPv4 TCP download throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a TCP download performance test over IPv4 using a target bandwidth
        of 1380 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfDownloadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`1400 Mbps IPv4 TCP download throughput test`	`perf_IPv4_TCP_download_1400Mbps`	1400 Mbps IPv4 TCP download throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a TCP download performance test over IPv4 using a target bandwidth
        of 1400 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfDownloadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`1420 Mbps IPv4 TCP download throughput test`	`perf_IPv4_TCP_download_1420Mbps`	1420 Mbps IPv4 TCP download throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a TCP download performance test over IPv4 using a target bandwidth
        of 1420 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfDownloadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`1440 Mbps IPv4 TCP download throughput test`	`perf_IPv4_TCP_download_1440Mbps`	1440 Mbps IPv4 TCP download throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a TCP download performance test over IPv4 using a target bandwidth
        of 1440 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfDownloadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`1460 Mbps IPv4 TCP download throughput test`	`perf_IPv4_TCP_download_1460Mbps`	1460 Mbps IPv4 TCP download throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a TCP download performance test over IPv4 using a target bandwidth
        of 1460 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfDownloadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`1480 Mbps IPv4 TCP download throughput test`	`perf_IPv4_TCP_download_1480Mbps`	1480 Mbps IPv4 TCP download throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a TCP download performance test over IPv4 using a target bandwidth
        of 1480 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfDownloadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`1500 Mbps IPv4 TCP download throughput test`	`perf_IPv4_TCP_download_1500Mbps`	1500 Mbps IPv4 TCP download throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a TCP download performance test over IPv4 using a target bandwidth
        of 1500 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfDownloadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`1520 Mbps IPv4 TCP download throughput test`	`perf_IPv4_TCP_download_1520Mbps`	1520 Mbps IPv4 TCP download throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a TCP download performance test over IPv4 using a target bandwidth
        of 1520 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfDownloadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`1540 Mbps IPv4 TCP download throughput test`	`perf_IPv4_TCP_download_1540Mbps`	1540 Mbps IPv4 TCP download throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a TCP download performance test over IPv4 using a target bandwidth
        of 1540 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfDownloadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`1560 Mbps IPv4 TCP download throughput test`	`perf_IPv4_TCP_download_1560Mbps`	1560 Mbps IPv4 TCP download throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a TCP download performance test over IPv4 using a target bandwidth
        of 1560 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfDownloadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`1580 Mbps IPv4 TCP download throughput test`	`perf_IPv4_TCP_download_1580Mbps`	1580 Mbps IPv4 TCP download throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a TCP download performance test over IPv4 using a target bandwidth
        of 1580 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfDownloadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`1600 Mbps IPv4 TCP download throughput test`	`perf_IPv4_TCP_download_1600Mbps`	1600 Mbps IPv4 TCP download throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a TCP download performance test over IPv4 using a target bandwidth
        of 1600 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfDownloadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`1620 Mbps IPv4 TCP download throughput test`	`perf_IPv4_TCP_download_1620Mbps`	1620 Mbps IPv4 TCP download throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a TCP download performance test over IPv4 using a target bandwidth
        of 1620 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfDownloadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`1640 Mbps IPv4 TCP download throughput test`	`perf_IPv4_TCP_download_1640Mbps`	1640 Mbps IPv4 TCP download throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a TCP download performance test over IPv4 using a target bandwidth
        of 1640 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfDownloadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`1660 Mbps IPv4 TCP download throughput test`	`perf_IPv4_TCP_download_1660Mbps`	1660 Mbps IPv4 TCP download throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a TCP download performance test over IPv4 using a target bandwidth
        of 1660 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfDownloadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`1680 Mbps IPv4 TCP download throughput test`	`perf_IPv4_TCP_download_1680Mbps`	1680 Mbps IPv4 TCP download throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a TCP download performance test over IPv4 using a target bandwidth
        of 1680 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfDownloadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`1700 Mbps IPv4 TCP download throughput test`	`perf_IPv4_TCP_download_1700Mbps`	1700 Mbps IPv4 TCP download throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, measure and
        record the round trip time (RTT).
step 3. Start a performance server on a second LAN using the port specified by
        the testvar perfPort.
step 4. Run a TCP download performance test over IPv4 using a target bandwidth
        of 1700 (Mbps).
step 5. Verify that the measured throughout performance is at least 95% of the
        target bandwidth. Also verify that the number of TCP retransmits is less
        than the value specified for perfDownloadTcpRetr, if it is set.
step 6. Shutdown the performance client and server. Verify connectivity between
        LAN and WAN.

Test	Name	Synopsis
`1720 Mbps IPv4 TCP download throughput test`	`perf_IPv4_TCP_download_1720Mbps`	1720 Mbps IPv4 TCP download throughput test



step 1. Start a performance client on the LAN.
step 2. Verify connectivity between the LAN performance client and its gateway
        (the DUT). If the testvar perfPingEnable is set to **yes**, m