CDRouter IPv6 User Guide 6.3/Example Configurations
From QA Cafe Support Wiki
Example Configurations
There are large variety of IPv6 configurations that can be tested with CDRouter IPv6. CDRouter IPv6 currently supports 11 distinct IPv6 WAN modes, two IPv6 LAN modes, and seven IPv4 WAN modes, resulting in over 100 unique configurations that can be tested. The table below summarizes the dual-stack configurations that can be tested with CDRouter IPv6:
| IPv4 WAN Mode wanMode |
IPv6 WAN Mode Configuration Number |
IPv6 LAN Mode ipv6LanMode |
| Any* | 1-2 | autoconf or DHCP |
| Any Ethernet** | 3-5 | autoconf or DHCP |
| Any* | 6-11 | autoconf or DHCP |
* CDRouter currently supports the following IPv4 WAN modes: static, DHCP, PPPoE, L2TP, PPTP, PPPoA, PPP/T1.
** PPPoE requires an Ethernet physical layer. As a result, this IPv6 WAN mode supports only IPv4 WAN modes of static, DHCP, PPPoE, L2TP, PPTP.
A number of basic example configurations for CDRouter IPv6 are provided below. The examples provided are independent of the IPv4 WAN connection mode used by the DUT, and cover the following IPv6 modes of operation:
- Example 1: 6to4 on the WAN and autoconf on the LAN
- Example 2: 6to4 on the WAN and DHCPv6 on the LAN
- Example 3: Static IPv6 on the WAN and autoconf on the LAN
- Example 4: Static IPv6 on the WAN and DHCPv6 on the LAN
- Example 5: DHCPv6 without prefix delegation on the WAN and autoconf on the LAN
- Example 6: DHCPv6 with prefix delegation on the WAN and DHCPv6 on the LAN
- Example 7: Autoconf on the WAN and DHCPv6 on the LAN
- Example 8: 6rd on the WAN and autoconf on the LAN
- Example 9: IPv6 over PPPoE on the WAN
- Example 10: Static IPv6 with prefix delegation on the WAN and autoconf on the LAN
- Example 11: Autoconf with prefix delegation on the WAN and autoconf on the LAN
Example 1: 6to4 on the WAN and autoconf on the LAN
In this example, CDRouter is configured to create a basic dual-stack IPv4/IPv6 test setup for the DUT using 6to4 for IPv6 connectivity on the WAN and autoconfiguration for IPv6 address assignment on the LAN. This is the most basic IPv6 test setup and requires minimal configuration of CDRouter and the DUT.
From an IPv4 perspective, CDRouter will create a DHCP server on the WAN which will terminate the DUT’s WAN DHCP connection. CDRouter is configured to provide the global IPv4 address 12.12.12.2 and DNS servers 1.1.1.1 and 1.1.1.2 to the DUT. The DUT is also configured with a LAN IPv4 address of 192.168.1.1 and a DHCP pool range of 192.168.1.2 through 192.168.2.7. CDRouter is configured to match these LAN-side settings on the DUT. Please see the CDRouter User's Guide for more information on the IPv4 specific configuration options listed below.
From an IPv6 perspective, IPv6 is enabled and it is expected that the DUT will provide IPv6 connectivity to all connected clients via an automatic 6to4 tunnel on the WAN. As a result, CDRouter is configured to create a 6to4 relay server at the default anycast address of 192.88.99.1 on the WAN.
The DUT’s global IPv6 address is expected to be <6to4 prefix>:<ipv6LanSubnetId>:<host ID portion of ipv6LanIp>. In this particular example, assuming the 16-bit Site Level Aggregator (SLA) used by the DUT is simply 1, the expected global IPv6 address of the DUT is:
- <6to4 prefix>:<ipv6LanSubnetId>:<host ID portion of ipv6LanIp> = 2002:c0c:c02:1::1
CDRouter is also configured to use IPv6 stateless address autoconfiguration on the LAN for all clients that it creates. CDRouter will create 100 LAN clients during the scaling tests.
This example also assumes that the DUT supports the NDP RDNSS option (25) and is configured to provide its global IP address as the DNS server to all clients on the LAN.
IPv4 Configuration: testvar wanInterface eth2 testvar wanMode DHCP testvar wanIspIp 12.12.12.1 testvar wanIspAssignIp 12.12.12.2 testvar wanNatIp 12.12.12.2 testvar wanIspNextIp 12.12.12.254 testvar wanIspMask 255.255.255.0 testvar wanMac 00:0b:0b:00:00:01 testvar wanDnsServer 1.1.1.1 testvar wanBackupDnsServer 1.1.1.2 testvar lanInterface eth1 testvar lanIp 192.168.1.1 testvar lanMask 255.255.255.0 testvar lanMac 00:0a:0a:00:00:01 testvar dhcpClientStart 192.168.1.2 testvar dhcpClientEnd 192.168.1.7 IPv6 Configuration: testvar supportsIPv6 yes # -- WAN configuration testvar ipv6WanMode 6to4 testvar ipv6RelayServer 192.88.99.1 # -- LAN configuration testvar ipv6LanMode autoconf testvar ipv6LanIp ::1 testvar ipv6LanSubnetId 1 testvar ipv6SupportsRdnss yes testvar ipv6DNStoLAN no testvar ipv6RAInterval 300 # -- other configuration options testvar ipv6RemoteHost 3001:51a:cafe::1 testvar ipv6MaxLanClients 100 testvar ipv6FreeNetworkStart 3001:cafe:1:: testvar ipv6FreeNetworkEnd 3001:ffff:ffff:: testvar ipv6FreeNetworkPrefixLen 64 IPv6 Firewall Configuration: testvar ipv6FirewallTcpClosedPorts “80 8080” testvar ipv6FirewallUdpClosedPorts all testvar ipv6FirewallTcpOpenPorts “443” testvar ipv6FirewallUdpOpenPorts 113 testvar ipv6WanPingRespond no
Note that the range of ports scanned in the firewall-v6.tcl test module can be configured using the portScanStart and portScanStop testvars. Please see the CDRouter User's Guide for more information.
Example 2: 6to4 on the WAN and DHCPv6 on the LAN
In this example, the IPv4 configuration and IPv6 firewall configuration are identical to those provided in Example 1 above.
The primary difference between this configuration and the configuration provided in Example 1 is the IPv6 LAN mode. As in Example 1, the DUT will provide IPv6 connectivity to all connected clients via an automatic 6to4 tunnel on the WAN. As a result, CDRouter is configured to create a 6to4 relay server at 192.88.99.1 on the WAN. The DUT’s global IPv6 address is expected to be <6to4 prefix>:<ipv6LanSubnetId>:<host ID portion of ipv6LanIp>. In this particular example, assuming the 16-bit Site Level Aggregator (SLA) used by the DUT is simply 1, the expected global IPv6 address of the DUT is again:
- <6to4 prefix>:<ipv6LanSubnetId>:<host ID portion of ipv6LanIp> = 2002:c0c:c02:1::1
Likewise, the DHCPv6 pool range of the DUT is expected to be:
- <6to4 prefix>:<ipv6LanSubnetId>:<ipv6DhcpClientStart> = 2002:c0c:c02:1::2
- <6to4 prefix>:<ipv6DhcpClientEnd> = 2002:c0c:c02:1::1F
With the following LAN clients excluded from the DHCPv6 pool:
- <6to4 prefix>:<ipv6LanSubnetId>:<ipv6DhcpClientExlude> = 2002:c0c:c02:1::3,
2002:c0c:c02:1::7
In this example, 28 LAN clients (the size of the DHCPv6 pool) will be created during the scaling tests. This example also assumes that the DUT does not support the NDP RDNSS option (25) and that the DUT is configured to provide the specific IPv6 DNS server addresses 3001:51:cafe::2 and 3001:51:cafe::3 to clients on the LAN via DHCPv6 options.
IPv6 Configuration: testvar supportsIPv6 yes # -- WAN configuration testvar ipv6WanMode 6to4 testvar ipv6RelayServer 192.88.99.1 # -- LAN configuration testvar ipv6LanMode DHCP testvar ipv6LanIp ::1 testvar ipv6LanSubnetId 1 testvar ipv6DhcpClientStart ::2 testvar ipv6DhcpClientEnd ::1F testvar ipv6DhcpClientExclude “::3 ::7” testvar ipv6SupportsRdnss no testvar ipv6DNStoLAN yes testvar ipv6RAInterval 300 # -- other configuration options testvar ipv6RemoteHost 3001:51a:cafe::1 testvar ipv6WanDnsServer 3001:51a:cafe::2 testvar ipv6WanBackupDnsServer 3001:51:cafe::3 testvar ipv6MaxLanClients 100 testvar ipv6FreeNetworkStart 3001:cafe:1:: testvar ipv6FreeNetworkEnd 3001:ffff:ffff:: testvar ipv6FreeNetworkPrefixLen 64
Example 3: Static IPv6 on the WAN and autoconf on the LAN
In this example, the IPv4 configuration and IPv6 firewall configuration are identical to those provided in Example 1 above.
The primary difference between this configuration and the configuration provided in Example 1 is the IPv6 WAN mode. In this example, it is expected that the DUT will provide IPv6 connectivity to all connected clients via a static IPv6 connection on the WAN. The DUT’s static IPv6 address is 3001::2, and CDRouter’s IPv6 address (representing the ISP next-hop gateway) is 3001::1. CDRouter will create IPv6 DNS servers at the addresses 3001:51a:cafe::2 and 3001:51a:cafe::3.
On the LAN side, the DUT is configured for autoconf. Since the IPv6 WAN mode is static, the DUT’s global LAN IPv6 address must be manually configured. In this example the DUT’s global LAN IPv6 address is configured to 2004::1 with a prefix length of 64. This example assumes that IPv6 DNS information will be provided to clients on the LAN via DHCPv6 information requests.
In this example, 100 LAN clients will be created during the scaling tests.
IPv6 Configuration: testvar supportsIPv6 yes # -- WAN configuration testvar ipv6WanMode static testvar ipv6WanIspIp 3001::1 testvar ipv6WanIspAssignIp 3001::2 # -- LAN configuration testvar ipv6LanMode autoconf testvar ipv6LanIp 2004::1 testvar ipv6LanPrefixLen 64 testvar ipv6DNStoLAN yes testvar ipv6RAInterval 300 # -- other configuration options testvar ipv6RemoteHost 3001:51a:cafe::1 testvar ipv6WanDnsServer 3001:51a:cafe::2 testvar ipv6WanBackupDnsServer 3001:51a:cafe::3 testvar ipv6MaxLanClients 100 testvar ipv6FreeNetworkStart 3001:cafe:1:: testvar ipv6FreeNetworkEnd 3001:ffff:ffff:: testvar ipv6FreeNetworkPrefixLen 64
Example 4: Static IPv6 on the WAN and DHCPv6 on the LAN
In this example, the IPv4 configuration and IPv6 firewall configuration are identical to those provided in Example 1 above. Additionally, both the IPv6 WAN mode and IPv6 LAN mode differ from that of Example 1.
On the WAN side, it is expected that the DUT will provide IPv6 connectivity to all connected clients via a static IPv6 connection. In this example, the DUT’s static IPv6 address is 3001::2, and CDRouter’s IPv6 address (representing the ISP next-hop gateway) is 3001::1. CDRouter will create IPv6 DNS servers at the addresses 3001:51a:cafe::2 and 3001:51a:cafe::3.
On the LAN side, the DUT’s global IPv6 address is configured to be 2004::1 with a prefix length of 64. The LAN side prefix is automatically determined by CDRouter based on these values.
Any LAN clients created by CDRouter are configured to obtain global IPv6 addresses via DHCPv6. The configured DHCPv6 pool is ::2 through ::1F, where the prefix is automatically determined as stated above. There is one address excluded from the DHCPv6 pool range (::12). This pool range must match the pool range configured on the DUT. With the prefix included, the DHCPv6 pool range is:
- <LAN prefix>:<ipv6DhcpClientStart> = 2004::2
- <LAN prefix>:<ipv6DhcpClientEnd> = 2004::1F
With the following LAN clients excluded from the DHCPv6 pool:
- <LAN prefix>:<ipv6DhcpClientExlude> = 2004::12
This example assumes that IPv6 DNS server address will be provided to clients on the LAN via DHCPv6 options.
In this example, 29 LAN clients (the size of the DHCPv6 pool) will be created during the scaling tests.
IPv6 Configuration: testvar supportsIPv6 yes # -- WAN configuration testvar ipv6WanMode static testvar ipv6WanIspIp 3001::1 testvar ipv6WanIspAssignIp 3001::2 testvar ipv6WanIspNextIp 3001::3 testvar ipv6WanIspPrefixLen 64 # -- LAN configuration testvar ipv6LanMode DHCP testvar ipv6LanIp 2004::1 testvar ipv6LanPrefixLen 64 testvar ipv6DhcpClientStart ::2 testvar ipv6DhcpClientEnd ::1F testvar ipv6DhcpClientExclude ::12 testvar ipv6DNStoLAN yes testvar ipv6RAInterval 300 # -- other configuration options testvar ipv6RemoteHost 3001:51a:cafe::1 testvar ipv6WanDnsServer 3001:51a:cafe::2 testvar ipv6WanBackupDnsServer 3001:51a:cafe::3 testvar ipv6FreeNetworkStart 3001:cafe:1:: testvar ipv6FreeNetworkEnd 3001:ffff:ffff:: testvar ipv6FreeNetworkPrefixLen 64
Example 5: DHCPv6 without prefix delegation on the WAN and autoconf on the LAN
In this example, the IPv4 configuration and IPv6 firewall configuration are identical to those provided in Example 1 above. Additionally, it is expected that the DUT will implement DHCPv6 on the WAN for acquisition of a non-temporary IPv6 address. DHCPv6 prefix delegation is not used in this configuration. CDRouter’s DHCPv6 server (representing the ISP next-hop gateway as well) is 3001::2. CDRouter will assign the non-temporary IPv6 address 3001::2 and the IPv6 DNS server addresses 3001:51a:cafe::2 and 3001:51a:cafe::3 to the DUT via DHCPv6. The prefix length utilized by CDRouter on the WAN is configured to 64 bits. CDRouter will use the address 3001::3 as a temporary address for renumbering tests on the WAN.
On the LAN side, the DUT is configured for autoconf. The DUT’s global LAN IPv6 address must be manually configured. In this example the DUT’s global LAN IPv6 address is configured to 2004::1 with a prefix length of 64. This configuration also assumes that the DUT passes the IPv6 DNS server addresses learned on the WAN to clients on the LAN via the NDP RDNSS option (25).
In this example, 100 LAN clients will be created during the scaling tests.
IPv6 Configuration: testvar supportsIPv6 yes # -- WAN configuration testvar ipv6WanMode DHCP testvar ipv6WanIspIp 3001::1 testvar ipv6WanIspAssignIp 3001::2 testvar ipv6WanIspNextIp 3001::3 testvar ipv6WanIspPrefixLen 64 testvar dhcpv6WanEnablePD no # -- LAN configuration testvar ipv6LanMode autoconf testvar ipv6LanIp 2004::1 testvar ipv6LanPrefixLen 64 testvar ipv6SupportsRdnss yes testvar ipv6DNStoLAN yes testvar ipv6RAInterval 300 # -- other configuration options testvar ipv6RemoteHost 3001:51a:cafe::1 testvar ipv6WanDnsServer 3001:51a:cafe::2 testvar ipv6WanBackupDnsServer 3001:51a:cafe::3 testvar ipv6MaxLanClients 100 testvar ipv6FreeNetworkStart 3001:cafe:1:: testvar ipv6FreeNetworkEnd 3001:ffff:ffff:: testvar ipv6FreeNetworkPrefixLen 64
Example 6: DHCPv6 with prefix delegation on the WAN and DHCPv6 on the LAN
In this example, the IPv4 configuration and IPv6 firewall configuration are identical to those provided in Example 1 above. Additionally, it is expected that the DUT will implement DHCPv6 on the WAN for acquisition of a non-temporary IPv6 address and an IPv6 address prefix for the LAN. CDRouter’s DHCPv6 server (representing the ISP next-hop gateway as well) is 3001::2. CDRouter will assign the non-temporary IPv6 address 3001::2 and the IPv6 DNS server addresses 3001:51a:cafe::2 and 3001:51a:cafe::3 to the DUT via DHCPv6. The prefix length utilized by CDRouter on the WAN is configured to 64 bits. CDRouter will use the address 3001::3 as a temporary address for renumbering tests on the WAN.
The prefix assigned by CDRouter to the DUT is 3001:dddd:: with a prefix length of 48 bits. The prefix 3001:ddde:: will be used by CDRouter for renumbering tests on the WAN. CDRouter is also configured with a prefix delegation latency of 30 seconds. This latency specifies the expected amount of time, in seconds, that it takes for the DUT to propagate prefix changes on the WAN to clients on the LAN.
On the LAN side, the DUT is configured to provide addresses to clients via DHCPv6, as in Example 2. This example also assumes that the DUT is configured to provide the IPv6 DNS server addresses learned on the WAN, 3001:51:cafe::2 and 3001:51:cafe::3, to clients on the LAN via DHCPv6 options.
In this example, 100 LAN clients will be created during the scaling tests.
IPv6 Configuration: testvar supportsIPv6 yes # -- WAN configuration testvar ipv6WanMode DHCP testvar ipv6WanIspIp 3001::1 testvar ipv6WanIspAssignIp 3001::2 testvar ipv6WanIspNextIp 3001::3 testvar ipv6WanIspPrefixLen 64 testvar dhcpv6WanEnablePD yes testvar dhcpv6WanAssignPrefix 2011:dddd:: testvar dhcpv6WanAssignNextPrefix 3001:ddde:: testvar dhcpv6WanAssignPrefixLen 48 testvar dhcpv6PDLatency 30 # -- LAN configuration testvar ipv6LanMode DHCP testvar ipv6LanIp ::1 testvar ipv6DhcpClientStart ::2 testvar ipv6DhcpClientEnd ::1F testvar ipv6DhcpClientExclude “::3 ::7” testvar ipv6DNStoLAN yes testvar ipv6RAInterval 300 # -- other configuration options testvar ipv6RemoteHost 3001:51a:cafe::1 testvar ipv6WanDnsServer 3001:51a:cafe::2 testvar ipv6WanBackupDnsServer 3001:51a:cafe::3 testvar ipv6MaxLanClients 100 testvar ipv6FreeNetworkStart 3001:cafe:1:: testvar ipv6FreeNetworkEnd 3001:ffff:ffff:: testvar ipv6FreeNetworkPrefixLen 64
Example 7: Autoconf on the WAN and DHCPv6 on the LAN
In this example, the IPv4 configuration and IPv6 firewall configuration are identical to those provided in Example 1 above. Additionally, it is expected that the DUT will implement stateless address autoconfiguration for IPv6 address acquisition on the WAN. The prefix and prefix length advertised by CDRouter are automatically determined based on WAN ISP address and prefix length. In this example the prefix advertised on the WAN will be 3001::/64.
On the LAN side, the DUT is configured to provide addresses to clients via DHCPv6, as in Example 2. This example also assumes that the DUT is configured to provide the IPv6 DNS server addresses learned on the WAN, 3001:51:cafe::2 and 3001:51:cafe::3, to clients on the LAN via DHCPv6 options.
In this example, 100 LAN clients will be created during the scaling tests.
IPv6 Configuration: testvar supportsIPv6 yes # -- WAN configuration testvar ipv6WanMode autoconf testvar ipv6WanIspIp 3001::1 testvar ipv6WanIspPrefixLen 64 testvar dhcpv6WanEnablePD no # -- LAN configuration testvar ipv6LanMode DHCP testvar ipv6LanIp ::1 testvar ipv6DhcpClientStart ::2 testvar ipv6DhcpClientEnd ::1F testvar ipv6DhcpClientExclude “::3 ::7” testvar ipv6DNStoLAN yes testvar ipv6RAInterval 300 # -- other configuration options testvar ipv6RemoteHost 3001:51a:cafe::1 testvar ipv6WanDnsServer 3001:51a:cafe::2 testvar ipv6WanBackupDnsServer 3001:51a:cafe::3 testvar ipv6MaxLanClients 100 testvar ipv6FreeNetworkStart 3001:cafe:1:: testvar ipv6FreeNetworkEnd 3001:ffff:ffff:: testvar ipv6FreeNetworkPrefixLen 64
Example 8: 6rd on the WAN and autoconf on the LAN
Please see this Application Note for more information on configuring CDRouter for 6rd support on the WAN.
Example 9: IPv6 over PPPoE on the WAN
Please see this Application Note for more information on configuring CDRouter for IPv6 over PPPoE support on the WAN.
Example 10: Static IPv6 with prefix delegation on the WAN and autoconf on the LAN
In this example, the IPv4 configuration and IPv6 firewall configuration are identical to those provided in Example 1 above.
This example is very similar to Example 3 above with one major difference - DHCPv6 prefix delegation is used on the WAN to obtain a global IPv6 prefix for the LAN. In this example, it is expected that the DUT will provide IPv6 connectivity to all connected clients via a static IPv6 connection on the WAN. The DUT’s static IPv6 address is 3001::2, and CDRouter’s IPv6 address (representing the ISP next-hop gateway) is 3001::1. CDRouter will create IPv6 DNS servers at the addresses 3001:51a:cafe::2 and 3001:51a:cafe::3. CDRouter's DHCPv6 server is configured to provide the prefix 3001:dddd::/48 to the DUT via DHCPv6 on the WAN.
On the LAN side, the DUT is configured for autoconf. Since the IPv6 WAN mode is static with prefix delegation, the DUT’s global LAN IPv6 address must be manually configured*. The DUT’s global LAN IPv6 address is configured to 3001:dddd::%eui64% (which assumes the DUT is using EUI64 for the host ID portion of its global LAN IPv6 address), matching the configuration of CDRouter's DHCPv6 server on the WAN. This example assumes that IPv6 DNS information will be provided to clients on the LAN via DHCPv6 information requests.
In this example, 100 LAN clients will be created during the scaling tests.
* Note that this configuration is an exception, since in most configurations involving DHCPv6 prefix delegation the prefix portion of the ipv6LanIp is dynamically calculated by CDRouter. However, when using static IPv6 with prefix delegation the prefix portion of the ipv6LanIp testvar must be explicitly configured to match the expected prefix assigned by CDRouter's DHCPv6 server on the WAN, as specified by the testvar dhcpv6WanAssignPrefix. Likewise, the LAN IPv6 prefix length, ipv6LanPrefixLen must also match the prefix length utilized by CDRouter's DHCPv6 server as specified by the testvar dhcpv6WanAssignPrefixLen.
IPv6 Configuration: testvar supportsIPv6 yes # -- WAN configuration testvar ipv6WanMode static testvar ipv6WanIspIp 3001::1 testvar ipv6WanIspAssignIp 3001::2 testvar ipv6WanIspNextIp 3001::3 testvar ipv6WanIspPrefixLen 64 # -- WAN DHCPv6 prefix delegation configuration testvar dhcpv6WanEnablePD yes testvar dhcpv6WanAssignPrefix 3001:dddd:: testvar dhcpv6WanAssignNextPrefix 3001:ddde:: testvar dhcpv6WanAssignPrefixLen 48 testvar dhcpv6PDLatency 30 # -- LAN configuration testvar ipv6LanMode autoconf testvar ipv6LanIp 3001:dddd::%eui64% testvar ipv6LanPrefixLen 64 testvar ipv6DNStoLAN yes testvar ipv6RAInterval 300 # -- other configuration options testvar ipv6RemoteHost 3001:51a:cafe::1 testvar ipv6WanDnsServer 3001:51a:cafe::2 testvar ipv6WanBackupDnsServer 3001:51a:cafe::3 testvar ipv6MaxLanClients 100 testvar ipv6FreeNetworkStart 3001:cafe:1:: testvar ipv6FreeNetworkEnd 3001:ffff:ffff:: testvar ipv6FreeNetworkPrefixLen 64
Example 11: Autoconf with prefix delegation on the WAN and autoconf on the LAN
In this example, the IPv4 configuration and IPv6 firewall configuration are identical to those provided in Example 1 above.
This example uses autoconf on the WAN to determine a global WAN IPv6 address. DHCPv6 prefix delegation is also used on the WAN to obtain a global IPv6 prefix for the LAN. The DUT should automatically configure its WAN interface with a valid global IPv6 address based on the prefix information provided by CDRouter on the WAN. CDRouter is configured to advertise the prefix 3001::/64 on the WAN and will create IPv6 DNS servers at the addresses 3001:51a:cafe::2 and 3001:51a:cafe::3. CDRouter's DHCPv6 server is configured to provide the prefix 3001:dddd::/48 to the DUT via DHCPv6 on the WAN.
On the LAN side, the DUT is configured for autoconf. The DUT should automatically assign a global IPv6 address to its LAN interface via the prefix information obtained from CDRouter's DHCPv6 server on the WAN. CDRouter is configured to advertise the prefix 3001:dddd::/48. The DUT should use this prefix information to determine a valid 64-bit prefix to advertise to clients on the LAN. CDRouter's LAN clients will listen for Router Advertisements on the LAN and automatically assign EUI-64 based addresses using the 64-bit prefix advertised by the DUT. It is expected in this configuration that the DUT will assign its LAN interface an EUI-64 based global IPv6 address using the 64-bit prefix it has derived.
In this example, 100 LAN clients will be created during the scaling tests.
IPv6 Configuration: testvar supportsIPv6 yes # -- WAN configuration testvar ipv6WanMode autoconf testvar ipv6WanIspIp 3001::1 testvar ipv6WanIspPrefixLen 64 # -- WAN DHCPv6 prefix delegation configuration testvar dhcpv6WanEnablePD yes testvar dhcpv6WanAssignPrefix 3001:dddd:: testvar dhcpv6WanAssignNextPrefix 3001:ddde:: testvar dhcpv6WanAssignPrefixLen 48 testvar dhcpv6PDLatency 30 # -- LAN configuration testvar ipv6LanMode autoconf testvar ipv6LanIp 3001:dddd::%eui64% testvar ipv6LanPrefixLen 64 testvar ipv6DNStoLAN yes testvar ipv6RAInterval 300 # -- other configuration options testvar ipv6RemoteHost 3001:51a:cafe::1 testvar ipv6WanDnsServer 3001:51a:cafe::2 testvar ipv6WanBackupDnsServer 3001:51a:cafe::3 testvar ipv6MaxLanClients 100 testvar ipv6FreeNetworkStart 3001:cafe:1:: testvar ipv6FreeNetworkEnd 3001:ffff:ffff:: testvar ipv6FreeNetworkPrefixLen 64