Skip to content

QA Cafe ― IP Test Solutions

Knowledge Base > CDRouter 6.5 Release Notes

CDRouter 6.5 Release Notes

Release Notes

Release History

Release Type Release Number Release Date
Original CDRouter 6.5 Build 65 April 25, 2011
Maintenance CDRouter 6.5 Build 83 June 28, 2011
Maintenance CDRouter 6.5 Build 84 July 6, 2011
Maintenance CDRouter 6.5 Build 90 July 8, 2011
Maintenance CDRouter 6.5 Build 94 August 11, 2011
Maintenance CDRouter 6.5 Build 103 August 24, 2011
Maintenance CDRouter 6.5 Build 107 September 30, 2011


Original release: CDRouter 6.5 Build 65, April 25, 2011

New Features and Enhancements


CDRouter

  • Support for Ubuntu 11.04 (Natty Narwhal)

    The latest release of the Ubuntu Linux operating system from Canonical, version 11.04 codenamed Natty Narwhal, has been tested for compatibility with CDRouter 6.5 and is now recommended by QA Cafe. CDRouter 6.5 supports both the 32-bit and 64-bit Desktop Editions of Ubuntu 11.04.

    UPDATE: Support for Ubuntu 11.04 has been withdrawn due to potential stability issues with ath9k based wireless interfaces. We now recommend Ubuntu 10.10 instead.

CDRouter IPv6

  • Support for DS-Lite on the WAN

    CDRouter now supports draft-ietf-softwire-dual-stack-lite-07, dual-stack lite (DS-Lite) as an IPv4 WAN mode. DS-Lite is a new protocol that defines an IPv4-in-IPv6 tunnel architecture on the WAN that provides IPv4 connectivity over a native IPv6 WAN connection. There are two primary endpoints in a DS-Lite network: the "B4" element is located within the DUT and is responsible for encapsulating and transmitting IPv4 packets over an IPv6 connection on the WAN to the "AFTR" element. The AFTR is an IPv6 host maintained by the ISP that acts as the DS-Lite tunnel endpoint. In a DS-Lite network the IPv4 NAT functionality typically performed by the DUT is moved into the ISP's network. As a result, in a DS-Lite configuration the DUT does not have distinct WAN and LAN IPv4 addresses. The DUT's private LAN IPv4 address and network are tunneled directly to the ISP.

    To enable DS-Lite set the testvar wanMode to dslite. CDRouter will automatically create a DS-Lite AFTR element at the address specified by the new testvar ipv6DsliteAfter. In addition, CDRouter's DNS can be configured to include a domain name for the AFTR element on the WAN using the testvar dhcpv6WanAftrName. When a domain name is defined for the AFTR element, CDRouter's DNS servers will automatically resolve the configured domain name to the IPv6 address specified by the ipv6DsliteAftr testvar. Here's an example DS-Lite configuration:

    testvar wanMode             dslite
    testvar ipv6DsliteAftr      3001:aaaa::1
    testvar dhcpv6WanAftrName   aftr.qacafe.com
    

    Although DS-Lite is an IPv4 WAN mode, the CDRouter IPv6 add-on is required for DS-Lite testing. For more information, please see our Application Note on testing DS-Lite with CDRouter.

  • New test module for DS-Lite

    A new dslite.tcl test module has been introduced in this release. This module is designed to verify basic DS-Lite functionality and includes nine new test cases. Please scroll down to see a description of each test case included in this module.

  • New test module for verifying IPv6 DNS proxy functionality

    A new dns-v6.tcl test module has been introduced in this release. This module includes 15 new test cases for verifying the IPv6-related DNS proxy functionality of the DUT. Please scroll down to see a description of each test case included in this module.

  • New test module for LAN multiport testing over IPv6

    A new lan-mp-v6.tcl test module has been introduced in this release. This module is designed to verify basic LAN multiport functionality over IPv6 and includes four new test cases. Please scroll down to see a description of each test case included in this module.

  • Two new test cases in the IPv6 firewall test module

    Two new test cases, ipv6_firewall_512 and ipv6_firewall_513, have been added. These test cases verify recommendations 8 and 9, respectively, listed in Section 3.1 "Stateless Filters" of RFC 6092 Simple Security in IPv6 Gateway CPE. Recommendations 8 and 9 state the following:

       REC-8: By DEFAULT, inbound DNS queries received on exterior
       interfaces MUST NOT be processed by any integrated DNS resolving
       server.
    
       REC-9: Inbound DHCPv6 discovery packets [RFC3315] received on
       exterior interfaces MUST NOT be processed by any integrated DHCPv6
       server or relay agent.
    

    ipv6_firewall_512 verifies that DNS queries are not processed by the DUT on the WAN. Likewise, ipv6_firewall_513 verifies that DHCPv6 solicitations are not processed by the DUT on the WAN. With the inclusion of these two tests CDRouter's firewall-v6.tcl test module now supports all nine recommendations listed in Section 3.1 of RFC 6092.

  • Support for RFC 6106 DNSSL option on the WAN

    CDRouter now supports the new DNS search list (DNSSL) option defined in RFC 6106. The DNSSL option can be enabled in router advertisements sent by CDRouter on the WAN using the new testvar ipv6WanDNSSL. The value of the testvar wanDomainName is used to populate the DNSSL option on the WAN.

    testvar ipv6wanDNSSL yes
    testvar wanDomainName qacafe.com
    

  • New test case in ndp.tcl module for verifying RFC 6106 DNSSL option on LAN

    The test case ipv6_ndp_33 now verifies the contents of the Router Advertisement DNS Search List option (31) defined in RFC 6106. If the DUT supports this option the domain name(s) and lifetime provided will be verified based on the expected values as defined by the wanDomainName testvar. The ipv6DnsslSupport testvar can be used to specify whether or not the DUT supports this option:

    testvar ipv6DnsslSupport yes
    

    If the testvar ipv6DnsslSupport is set to "no", ipv6_ndp_33 will be automatically skipped by CDRouter.

  • New test case in dhcpv6-pd.tcl module for verifying subnet ID bits

    The test case dhcpv6_pd_14 now verifies the subnet ID bits contained in Router Advertisements sent on the LAN. The expected subnet ID bits can be configured using the testvar ipv6LanSubnetId. This testvar is a variable length string of hex characters, and should match the subnet ID configured on the DUT. Some example configurations are shown below:

    testvar ipv6LanSubnetId ffff
    testvar ipv6LanSubnetId 1
    

  • Support for RFC 5969 6rd DHCPv4 Option

    CDRouter now supports the 6rd DHCPv4 Option defined in IETF RFC 5969. When the testvar ipv6rdDHCPv4Option is enabled, CDRouter will include Option 212 in all DHCPv4 transactions on the WAN. The 6rd prefix, prefix length, IPv4 mask length, and border relay address that are included will be based on the values contained in the CDRouter config file.

    # -- Enable 6rd DHCPv4 Option
    testvar ipv6rdDHCPv4Option    yes
    
    # -- Configure other 6rd related parameters
    testvar ipv6RelayServer       192.88.99.1
    testvar ipv6rdPrefix          2010:1234::
    testvar ipv6rdPrefixLen       32
    testvar ipv6rdIPv4MaskLen     0
    

    This option is only applicable to configurations utilizing DHCP for IPv4 connectivity on the WAN.

  • New URL filtering module for IPv6

    The new url-filter-v6.tcl test module is designed to verify URL filtering over IPv6. We have seen a number of devices that provide IPv4 web filtering, but lack IPv6 web filtering capabilities entirely, and even allow access via IPv6 to web URLs that are filtered via IPv4. This new test module is an IPv6 port of CDRouter's existing url-filter.tcl test module and utilizes the same configuration testvars to define a list of blocked and permitted URLs to test:

    testvar urlFilterSupported      yes
    testvar filtered-urls 		"http://abc.com/yahoo.htm http://www.foo.com/home.htm"
    testvar non-filtered-urls 	"http://www.qacafe.com"
    

    Note that the url-filter-v6.tcl test module requires that the DUT supports DNS proxy functionality. As a result, if the testvar supportsDnsProxy is set to no this module will be automatically skipped by CDRouter.

CDRouter TR-069

  • od128.tcl module updated to support OD-128 Rev 04

    The od128.tcl has been updated to support Broadband Forum OD-128 Rev 04. Rev 04 of OD-128 includes provisions for devices implementing the Device:2 data model defined in TR-181 Issue 2. The test parameters defined for Device:2 compliant IGD implementations in OD-128 Rev 04 are different than the parameters defined for InternetGatewayDevice:1.x compliant IGD implementations. As a result, CDRouter will automatically choose the correct parameters to use based on the setting of the testvar tr69DeviceType. If tr69DeviceType is set to "VoIP" or "STB", CDRouter will test with the VoIP or STB specific parameters defined in OD-128 Rev 03 and earlier, respectively. If tr69DeviceType is set to "IGD", CDRouter will attempt to autodetect which parameters to use based on the IGD's advertised root object. If the IGD's root object is InternetGatewayDevice. CDRouter will use the older IGD parameters defined in OD-128 Rev 04. If the IGD's root object is Device. CDRouter will use the newer Device parameters in OD-128 Rev 04.

    Note that a number of the parameters defined for InternetGatewayDevice:1.x implementations in OD-128 Rev 04 are invalid. As a result, CDRouter will use the parameters from earlier versions of OD-128 when testing InternetGatewayDevice:1.x implementations.

  • od128.tcl and tr69.tcl test modules now support Device:2 devices based on TR-181 Issue 2

    The od128.tcl and tr69.tcl test modules have been updated based on Broadband Forum OD-128 Rev 4 and now support devices using the Device:2 parameter model based on TR-181 Issue 2. When testing a Device:2 compliant IGD, CDRouter will use parameter names from the Device:2 data model instead of the older IGD:1.x data model defined in TR-098 Amendment 2.

  • New Deployment Unit Install/Uninstall tests based on TR-157 Issue 3 and OD-128 Rev 4

    The od128.tcl module now contains an implementation of OD-128 Test 35.1 and 35.6 to verify the ChangeDUState RPC for install or uninstall. In order to run these tests, a Deployment Unit image must be installed on your local disk. CDRouter can be configured with the path to the Deployment Unit image along with the UUID associated with Deployment Unit.

    testvar tr69DUInstallImage /home/lab/du.img
    testvar tr69DUInstallUUID 12-23-34-23
    testvar tr69DUChangeTimeout 600
    

  • The tr181i2_profiles test module now supports TR-181 Issue 2 Amendment 2
  • The new tr181i2_profiles.tcl test module supports the new Device:2.2 profiles defined and TR-181 Issue 2 Amendment 2. TR-181 Amendment 2 Issue 2 is the first data model to incorporate specific IPv6 parameters.


New Test Modules and Test Cases


CDRouter IPv6

  • ipv6_ndp_33
  • TEST: Verify IPv6 Router Advertisements contain DNSSL option
    MODULE: ndp.tcl
    NAME: ipv6_ndp_33
    

  • ipv6_firewall_512
  • TEST: Verify inbound IPv6 DNS queries on the WAN are not processed by DNS proxy
    MODULE: firewall-v6.tcl
    NAME: ipv6_firewall_512
    

  • ipv6_firewall_513
  • TEST: Verify inbound DHCPv6 discovery packets on the WAN are not processed by DHCPv6 server
    MODULE: firewall-v6.tcl
    NAME: ipv6_firewall_513
    

  • dhcpv6_pd_14
  • TEST: Verify client router advertisements on LAN include expected subnet ID
    MODULE: dhcpv6-pd.tcl
    NAME: dhcpv6_pd_14
    

  • New test modules
  • MODULE: dslite.tcl includes nine new test cases!
    MODULE: dns-v6.tcl includes 15 new test cases!
    MODULE: url-filter-v6.tcl includes six new test cases!
    MODULE: lan-mp-v6.tcl includes four new test cases!
    

    For a complete description of all individual test cases included in the above test modules, please see the official list of CDRouter IPv6 test case summaries.

CDRouter TR-069

  • od128_test_35.1
  • TEST: Change DU State - Install without Execution Environment Reference
    MODULE: od128.tcl
    NAME: od128_test_35.1
    

  • od128_test_35.6
  • TEST: Change DU State - Uninstall
    MODULE: od128.tcl
    NAME: od128_test_35.6
    

  • New test modules
  • MODULE: tr181i2_profiles.tcl includes over 100 new test cases!
    

Bug Fixes and Notes


CDRouter

  • This release resolves an issue in the cdrouter_nat_300 test case when PPP based WAN modes are used in conjunction with WAN and LAN VLANs. In previous releases this test case would produce a fatal error in this scenario.
  • Support for madwifi and DriverLoader based wireless interfaces has been deprecated. We recommend utilizing an Atheros ath9k, ath5k, ar9170usb based wireless adapter instead. Please see this Knowledge Base article for a list of recommended wireless adapters.
  • The cdrouter_pppoe_client_320 test case has been updated to resolve an issue associated with the PPPoE relays that included a Relay-Session-Id tag. In previous releases CDRouter's PPPoE server would not include the correct Relay-Session-Id tag in PADO responses if the preceding PADI included this tag already.
  • Fixed an issue with bad ICMPv6 checksums in CDRouter's router advertisements sent on the WAN. In previous releases, router advertisements sent by CDRouter on the WAN that included the RDNSS option, enabled by setting the testvar ipv6WanRDNSS to yes, would include an incorrect ICMPv6 checksum. The checksums are now calculated correctly in this release.
  • Fixed an issue in the cdrouter_dyndns_10 test case. In previous releases there was a bug in the logic of this test case that resulted in the improper clearing of state within the members.dyndns.org server at the end of the test. This issue could result in failures in subsequent DynDNS tests. This issue has been resolved in CDRouter 6.5
  • CDRouter's dyndns.tcl now provides DynDNS capability on either the older checkip.dyndns.org and members.dyndns.org domains or the newer checkup.dyndns.com and members.dyndns.com domains. In previous releases CDRouter supported only the checkup.dyndns.org and members.dyndns.org domains.
  • Resolved a startup issue when two IPSec tunnels (IKE or manual) are configured on the WAN. In previous releases the second tunnel would produce an error during initialization which would cause the startup procedure to abort. This issue has been resolved in CDRouter 6.5.

CDRouter IPv6

  • The test ipv6_ndp_32 has been updated to accept link-local addresses as valid DNS servers on the LAN. When the testvar ipv6DNStoLAN is set to no, ipv6_ndp_32 now allows the DUT to provide its LAN side link-local address in the RDNSS option in router advertisements sent on the LAN. In previous releases this test only accepted the DUT's LAN side global IPv6 address when the testvar ipv6DNStoLAN was set to no.
  • Fixed an issue in the dhcpv6_pd_12 test case included in the dhcpv6-pd.tcl test module. This test case originally compared the LAN side prefix to the expected WAN side prefix using the LAN side prefix length instead of the WAN side prefix length. This did not allow for the inclusion of subnet bits and would produce a failure if non-zero subnet bits were used by the DUT. This test has been updated to ensure that the WAN side prefix length is used in the prefix comparison.
  • CDRouter's DHCPv6 client timing has been updated and improved for higher accuracy. In previous releases the DHCPv6 client timeouts were not being calculated correctly - this issue has now been resolved.
  • CDRouter's 6rd prefix delegation expected prefix calculations have been updated. In previous releases the testvar ipv6rdPrefix must be configured with the exact number of bits as specified by the testvar ipv6rdPrefixLen. In this release CDRouter now truncates the ipv6rdPrefix based on the ipv6rdPrefixLen testvar. For example, if is 4001:5555:: and ipv6rdPrefixLen is 16, CDRouter will automatically truncate the expected prefix to 4001::. In previous releases the entire configured prefix would be used, based on the assumption that it would be configured to exactly match the specified prefix length.
  • A configuration check has been added to ensure that the IPv6 relay server, as configured using the testvar ipv6RelayServer, is not on the same network as the primary WAN connection, as defined by the testvars wanIspIp, wanIspAssignIp, and wanIspMask. If the ipv6RelayServer is configured on the primary WAN network, CDRouter will now produce a warning during startup and abort the test run.
  • Fixed an issue with CDRouter's WAN router advertisement RDNSS option. In previous releases when the testvar ipv6WanRDNSS was set to yes, the ICMPv6 checksum for the RDNSS option was not being calculated correctly.
  • CDRouter's LAN client behavior has been modified with respect to how IPv6 DNS server information is learned. During the start-up procedure CDRouter will attempt to obtain IPv6 DNS servers via the NDP RDNSS option if the ipv6LanMode is set to autoconf. If ipv6LanMode is set to DHCP, CDRouter will attempt to obtain IPv6 DNS servers via DHCPv6. In cases where ipv6LanMode is set to autoconf but the RDNSS option is not provided, CDRouter will send a DHCPv6 Information Request for the IPv6 DNS servers if the O-bit is set in router advertisements from by the DUT. During the start-up procedure CDRouter's LAN client will now also produce a warning message if no IPv6 DNS servers are learned.

    After the start-up procedure, CDRouter will monitor RDNSS information in all received router advertisements on the LAN and automatically install the IPv6 DNS addresses specified if the lifetime is greater than 0, and the addresses are different than the ones that were previously learned. If CDRouter is unable to obtain IPv6 DNS servers via RDNSS and the O-bit is set, CDRouter will continue to send DHCPv6 Information Requests for DNS to the DUT.

  • The ipv6_6rd_10 test case has been updated to use the wanIspNextIp address instead of the remoteHostIp address, as originally specified, as the remote WAN endpoint of this test. This change ensures that the remote WAN endpoint lies within the aggregateable 6rd domain of the DUT when 6rd address compression is enabled. Note that the testvar wanIspNextIp must be properly configured in order for this test to work correctly. Both wanIspNextIp and wanIspAssignIp must reside within the same network.
  • The tests ipv6_6to4_103 and ipv6_6rd_103 have been updated. These tests now verify that the preferred lifetime of the prefix being aged out is 0, as specified by Requirement L-13 in IETF RFC 6204:

      L-13:  If the delegated prefix changes, i.e. the current prefix is
              replaced with a new prefix without any overlapping time
              period, then the IPv6 CE router MUST immediately advertise the
              old prefix with a preferred lifetime of 0 and a valid lifetime
              of 2 hours (which must be decremented in real time) in a
              Router Advertisement message.
    

    Note that the valid lifetime is not currently verified in these tests. In earlier releases the valid lifetime was explicitly verified while the preferred lifetime was not.
  • Resolved an issue with CDRouter's DHCPv6 client on the LAN when an empty Domain Search List option is provided by the DHCPv6 server. In previous releases this condition would generate an error and cause CDRouter's DHCPv6 LAN client to restart. This issue has been resolved in CDRouter 6.5.

CDRouter TR-069

  • CDRouter's TR-098 profile definition has been updated to include a missing parameter in the Bridging:1 profile. In previous releases the parameter InternetGatewayDevice.Layer2Bridging.Filter.{i}.FilterInterface had been incorrectly omitted from this profile.

BuddyWeb

  • Fixed an issue with certain documentation links that included a . character in the URL. For example, in earlier releases, the following link would not work:

    http://localhost:8015/docs/testcases/od128_test_1.1

    BuddyWeb now properly handles these types of documentation links and displays the expected information.


Maintenance release: CDRouter 6.5 Build 83, June 28, 2011

Bug Fixes and Notes


CDRouter

  • The buddydiag script has been updated to display the contents of the /etc/network/interfaces file. Note that the buddydiag script is used only by QA Cafe Support when needed to collect diagnostic information which can be useful when debugging system level issues.
  • Updated the cdrouter_dmz_200 test case. The packets transmitted for IP protocol types 4, 41, and 58 included payloads which resulted in malformed packets. The packets for these three protocol types have been cleaned up and are no longer malformed.
  • Resolved an issue with the cdrouter_nat_510 test case where the first TCP connection that is established is deleted immediately. This issue should not impact results in most cases since the state of this TCP connection is irrelevant - it is only used to create a mapping in the DUT's NAT table. Note that this issue was introduced in CDRouter 6.5 and is not present in earlier releases.
  • Resolved a WAN ISP renumbering issue in the cdrouter_static_20 test case when the wanMode is set to DHCP. In previous releases the WAN ISP address would renumber and immediately proceed with the test without waiting for the DUT's DHCP client to learn the new ISP gateway address.

CDRouter IPv6

  • Resolved an issue with the ipv6_ndp_32 test case. In previous releases this test case would generate a fatal error if the testvar ipv6DNStoLAN was set to no and the DNS server provided by the DUT in the RDNSS option was not the DUT's LAN link local address or global IPv6 address.
  • Resolved an issue with the dhcpv6-pd_11 test case. In previous releases the check to ensure that the preferred lifetime for the advertised prefix on the LAN is less than or equal to the preferred lifetime provided by CDRouter on the WAN was being performed incorrectly.
  • The ipv6_firewall_513 test case has been updated to use the default address of 3001:51a:cafe::1 for the IPv6 remote host if the testvar ipv6RemoteHost is not defined. In previous releases this test case would generate a fatal error if the ipv6RemoteHost was not included in the config file.
  • By default CDRouter's LAN client will set the default IPv6 route based on the source link layer address option included in the DUT's router advertisements on the LAN. In previous releases a test run would be aborted if a default route for IPv6 could not be determined during the start up procedure. CDRouter's LAN client will now use Neighbor Discovery to determine the DUT's link layer address based on the source address of router advertisements received on the LAN if the source link layer address option is not present.
  • CDRouter now generates a warning and aborts startup if the ipv6LanMode testvar is set to DHCP and router advertisements from the DUT have the M-bit set to a value of 0. This is an invalid configuration that was not flagged by CDRouter in prior releases.
  • Resolved an issue with the dhcpv6ServerOptionCode and dhcpv6ServerOptionData testvars. In previous releases CDRouter's DHCPv6 server on the WAN would generate a fatal error if these testvars were configured or if the DHCPv6 client request additional undefined parameters.
  • Resolved an issue with CDRouter's IPv6 free network range calculations. In previous releases CDRouter would not iterate through the free network range properly for certain prefix and prefix length combinations.

Maintenance release: CDRouter 6.5 Build 84, July 6, 2011

Bug Fixes and Notes


CDRouter TR-069

  • The od128_test_20.1 test case has been updated to resolve a bug with its WAN interface detection algorithm. This bug was introduced in CDRouter 6.5 Build 65 and caused the test to fail immediately after it was started.


Maintenance release: CDRouter 6.5 Build 90, July 8, 2011

Bug Fixes and Notes


CDRouter

  • CDRouter checks the status of the DHCP leases for all LAN clients at the start of each test case. This is done to avoid interfering with a test case while it is running. If the T1 timer for a lease has expired when checked, CDRouter will attempt to renew the lease. Previously in these situations CDRouter would make multiple attempts to renew the lease until either:

    1. A response is received from the server and the lease is renewed, or
    2. The T2 timer expires, at which point CDRouter's LAN client will drop back to DHCP DISCOVERY mode.

    In this release CDRouter's DHCP client behavior has been modified such that clients will now fall back to DHCP DISCOVERY mode after only two failed renewal attempts.

  • CDRouter's LAN DHCP client behavior has been updated to better handle scenarios involving an address change during a test run. In previous releases CDRouter's LAN DHCP client would not function properly if a different IP address was obtained via a renewal transaction that occurred during a test run. This release resolves this issue.

CDRouter TR-069

  • The tr69_200 test case has been updated to resolve an issue similar to the one resolved for test od128_test_20.1 in CDRouter 6.5 Build 84.

CDRouter IPv6

  • The ipv6_dns_60 test case has been updated. This test performs DNS AAAA record lookups when verifying that the CPE's DNS proxy fails over to the new servers provided by the ISP. In previous releases this test would perform A lookups only.


Maintenance release: CDRouter 6.5 Build 94, August 11, 2011

New Features and Enhancements


CDRouter IPv6

  • CDRouter now supports the AFTR-Name DHCPv6 option (option number 64) defined in RFC6334. CDRouter will provide the DS-Lite AFTR name specified by the testvar dhcpv6WanAftrName in response to any DHCPv6 option 64 requests from the DUT:

    testvar dhcpv6WanAftrName aftr.qacafe.com

Bug Fixes and Notes


CDRouter TR-069

  • Updated the InternetGatewayDevice.Layer2Bridging.Bridge.{i}.BridgeStandard parameter type field to string in the TR-098 profiles definition. In previous releases this parameter was incorrectly defined as a boolean by CDRouter.
  • Resolved an issue with CDRouter's CWMP protocol version functionality. In previous releases, when the test testvar cwmpProtocolVersion was set to a value of 1.1, the CWMP protocol version utilized by the ACS in its SOAP headers would be reset to a value of 1.0 in certain test cases. This issue has been resolved, and the CWMP protocol version specified by cwmpProtocolVersion is now persistent throughout a test run.
  • Tests 35.1 and 35.6 in the OD-128 test module have been updated. In previous releases these two tests waited for the 11 APP ACTION COMPLETE event code from the CPE, as defined in OD-128 rev 04. However, this event code does not officially exist in TR-069 Amendment 3 and appears to be a typo in OD-128 rev 04. This release updates these two test cases to wait for an event code of 11 DU STATE CHANGE COMPLETE as defined in Table 7 of TR-069 Amendment 3.
  • The tr69_30 test case has been updated to resolve a fatal error when testing TR-106 compliant devices with TR-111 Part 2 enabled and the NATDetected parameter set to true.
  • The tr69_300 test has been updated to now wait for a 1 BOOT event code from the CPE following the FactoryReset RPC issued by the ACS. In previous releases this test would incorrectly wait for an M Reboot event code from the CPE, which should only be sent following a Reboot RPC from the ACS.

CDRouter IPv6

  • Revisited an issue originally addressed in CDRouter 6.4 Build 136 that was not completely resolved. From the CDRouter 6.4 Build 136 release notes:

    CDRouter's handling of Router Advertisements that include prefix information options with unique local prefixes has been updated. In previous releases CDRouter would in some cases attempt to create a global LAN IPv6 address from a unique local prefix advertised by the DUT. This situation would only occur if the final prefix information option included in the DUT's Router Advertisements contained a unique local prefix. CDRouter now ignores unique local prefixes when constructing a global IPv6 address on the LAN via autoconfiguration.

    The above bug fix from CDRouter 6.4 was incomplete leading to certain situations where CDRouter's LAN client would still use advertised unique local prefixes to construct a global IPv6 address. This issue has been resolved in CDRouter 6.5 Build 94.

  • The url-filter-v6 test module is now automatically skipped if IPv6 is globally disabled within CDRouter. In previous releases CDRouter would allow users to run this test module when IPv6 was globally disabled, which would lead to a fatal error.
  • The ipv6_ndp_20 test case has been updated to verify that the source IPv6 address of the ICMPv6 Redirect message sent by the DUT is the DUT's link-local address, as defined in Section 8.1 of RFC4861. In previous releases the source address of the ICMPv6 Redirect message was not explicitly verified. As a result, implementations that did not use their link-local address as the source address of the ICMPv6 Redirect message would incorrectly pass the test.
  • The ipv6_ndp_1 and ipv6_ndp_wan_1 test cases have been updated with a 5 second timeout while waiting for a Router Advertisement from the DUT. In previous releases this timeout was set to 3 seconds, which created a race condition when either test case was repeated multiple times. The race condition resulted from subsequent iterations of the test beginning immediately after the last one completed, which causes the DUT to receive multiple Router Solicitations in a very short period of time. Due to the rate-limiting algorithm specified in Section 6.2.6 of RFC4861, a DUT in this situation MUST delay its response by at least 3 seconds when multiple Router Solicitations are received:

    In all cases, Router Advertisements sent in response to a Router Solicitation MUST be delayed by a random time between 0 and MAX_RA_DELAY_TIME [0.5] seconds. (If a single advertisement is sent in response to multiple solicitations, the delay is relative to the first solicitation.) In addition, consecutive Router Advertisements sent to the all-nodes multicast address MUST be rate limited to no more than one advertisement every MIN_DELAY_BETWEEN_RAS [3] seconds.

    By adjusting the timeout in these tests to 5 seconds the race condition described above is avoided.

  • The ipv6_6rd_103 and ipv6_6to4_103 test cases have been updated to resolve a race condition with certain implementations that could result in a false positive.

  • Updated the icmpv6_10 test case to resolve an issue resulting in a fatal error when a malformed ICMPv6 Time Exceeded packet is received.

Maintenance release: CDRouter 6.5 Build 103, August 24, 2011

New Features and Enhancements


CDRouter

  • The cdrouter_dmz_200 test case has been updated to resolve an issue with the IP protocol type 4 packets transmitted by CDRouter. This issue is only present on systems with IPv6 support and could possibly result in a false negative for IP proto type 4 in this test case.
  • The cdrouter_renum and pppoe-pt test modules have been updated to resolve an issue involving WAN VLANs. In previous releases certain test cases in these two modules would create alternate stacks on the WAN without the correct VLAN configuration. As a result, incoming and outgoing packets on these stacks were not handled properly leading to false negative results.
  • The cdrouter_icmp_11 test case has been updated to resolve a log message typo which could lead to a fatal error in certain circumstances. This issue is only present in situations where the DUT unexpectedly fragments the upstream UDP packet transmitted at the start of the test.

CDRouter TR-069

  • CDRouter has been updated to resolve a generic TR-069 related issue associated with the testvar acsWaitForInitialInform. By default acsWaitForInitialInform is set to yes, which forces CDRouter to wait for an initial inform from the DUT during the startup procedure. When acsWaitForInitialInform is set to no CDRouter will not wait for an initial inform during the startup procedure, which could cause certain test cases in the od128 test module to produce fatal errors if executed in isolation.

Maintenance release: CDRouter 6.5 Build 107, September 30, 2011

New Features and Enhancements


CDRouter

  • CDRouter's WAN DHCP server now includes the Server Identifier option in DHCP NAK messages sent to the DUT.
  • Resolved "Argument list too long" error when initializing wireless network interfaces at the start of testing. CDRouter performs a wireless network scan to detect and attach to the network identified by the lanSSID testvar. In previous versions of CDRouter, the output of this scan could cause the startup procedure to fail in environments with a large number of wireless devices (roughly 200 or more). The output buffer limit has been increased to accommodate twice this number.
  • The cdrouter_ipsecpt_3 and cdrouter_dos_1 test cases were updated to ensure that the WAN MTU value is correctly calculated for packets with both PPPoE encapsulation and VLAN tagging. CDRouter automatically calculates the MTU size for WAN and LAN interfaces to account for frame encapsulations and VLAN tagging in order to avoid unintended fragmentation during test execution.
  • Resolved an issue in which CDRouter's configuration parser was no longer validating testvars such as dhcpClientOptionData1 that expect a string of hexidecmal digits representing abritrary binary data. This was causing the startup procedure to fail at runtime instead of notifying the user with an appropriate error message when the config file was parsed.

CDRouter Storage

  • Many storage tests rely on a version of the curl program to perform file transfers to and from the DUT. By default this program will apply any user customizations found in special .curlrc files, which alter the way curl behaves and may result in invalid test results. CDRouter has been updated to pass the -q option to curl which causes it to ignore any of these files if they exist.

    Note that the behavior of the curl program can also be adversely affected by certain environment variables, such as http_proxy and ftp_proxy, which are shared by other common applications and can be set as part of the system-level preferences. CDRouter's default installation does not set any of these environment variables and it is strongly recommended that they not be used in order to ensure the proper operation of CDRouter. Please refer to the curl(1) man page on your CDRouter system for a list of environment variables that curl recognizes.