CDRouter IPv6 User Guide 6.3/Test Methodology
From QA Cafe Support Wiki
Contents |
Test Methodology
Initial Setup
As mentioned earlier, CDRouter IPv6 is compatible with all existing CDRouter or CDRouter Multiport test setups. However, there are a few important caveats that must be taken into consideration prior to performing IPv6 testing with CDRouter IPv6.
- 1. IPv6 configuration within Linux
We recommend that IPv6 be disabled within the CDRouter Linux host operating system to avoid potential addressing conflicts when using CDRouter IPv6. Please see this Knowledge Base article for more information on disabling IPv6 within your Linux operating system.
- 2. Avoid using private IPv4 addresses for the primary IPv4 WAN connection when using 6to4 for IPv6 WAN connectivity
The 6to4 mechanism defined in RFC 3056 relies on translating globally routable 32-bit IPv4 addresses into a unique 48-bit IPv6 prefix. 6to4 is not designed to work with private IPv4 addresses, which should be avoided when configuring and running tests with CDRouter IPv6. Please see Example 1 provided in the Example Configurations section of this document for more information.
Start-Up
During the start-up procedure, CDRouter IPv6 expects the DUT to obtain an IPv4 address using any of the standard WAN connection modes supported by CDRouter (DHCP, PPPoE, PPPoA, PPP/T1, L2TP, PPTP, and static IP). Once an IPv4 address is obtained, the DUT should attempt to establish IPv6 connectivity on the WAN using the selected IPv6 WAN protocol (static, DHCP, PPPoE, 6to4, 6rd, or autoconf).
CDRouter will then create one or more IPv6 enabled LAN clients with IPv6 link local addresses. CDRouter’s LAN clients can be configured to obtain global IPv6 addresses via DHCPv6 or stateless address autoconfiguration. When DHCPv6 is chosen, CDRouter expects the DUT to be running a DHCPv6 server. Likewise, when stateless address autoconfiguration is used, CDRouter expects the DUT to advertise a valid global prefix on the LAN.
If CDRouter’s LAN client is successful in obtaining a valid global IPv6 address, basic Path MTU Discovery will be performed on the LAN and the testing procedure will begin.
Running
IPv6 support can be enabled within CDRouter by uncommenting the testvar supportsIPv6 and setting it to a value of “yes”.
CDRouter IPv6 includes a number of test modules designed to verify a wide variety of IPv6 related functionality, as outlined in the following table:
| Test Module | Description |
| basic-v6.tcl | Basic IPv6 extension header processing tests |
| frag-v6.tcl | IPv6 fragmentation tests |
| ndp.tcl | Neighbor Discovery Protocol and Router Advertisement tests for IPv6 devices |
| ndp-wan.tcl | Neighbor Discovery Protocol and Router Advertisement tests for the WAN side of IPv6 devices |
| dhcpv6-c.tcl | DHCPv6 client tests for the WAN side of the router |
| dhcpv6-pd.tcl | DHCPv6 prefix delegation tests for WAN to LAN IPv6 configuration |
| dhcpv6-s.tcl | DHCPv6 server tests for the LAN side of the router |
| pppoe-c-v6.tcl | PPPoE client tests with IPv6 on the WAN side of the router |
| 6to4.tcl | 6to4 tunnel tests for connecting IPv6 hosts over IPv6 networks |
| 6rd.tcl | 6rd tunnel tests for connecting IPv6 hosts over IPv6 networks |
| icmp-v6.tcl | ICMPv6 tests for baseline ICMPv6 not including Neighbor Discovery |
| firewall-v6.tcl | IPV6 firewall tests including port scans |
| apps-v6.tcl | Application tests for IPv6 |
| forward-v6.tcl | IPv6 forwarding tests with different packet sizes and directions |
| scaling-v6.tcl | Scaling tests for maximum number of IPv6 clients and connections (TCP, HTTP, etc) |
To run only the IPv6 related test modules from the buddy command-line:
# buddy –module basic-v6.tcl,ndp.tcl,ndp-wan.tcl,dhcpv6-c.tcl,dhcpv6-pd.tcl,dhcpv6-s.tcl,
pppoe-c-v6.tcl,6to4.tcl,6rd.tcl,icmp-v6.tcl,firewall-v6.tcl,apps-v6.tcl,
forward-v6.tcl,scaling-v6.tcl –trace –pt
For additional test execution options, see the CDRouter User Guide.