qacafe - ip test solutions

Release Information: Storage v7.0

Released on: 2011-09-30

Release Notes

Release History

Release Type Release Number Release Date
Original CDRouter 7.0 Build 102 December 1, 2011
Maintenance CDRouter 7.0 Build 111 January 4, 2012
Maintenance CDRouter 7.0 Build 117 February 2, 2012
Maintenance CDRouter 7.0 Build 119 February 17, 2012
Maintenance CDRouter 7.0 Build 128 March 8, 2012
Maintenance CDRouter 7.0 Build 134 April 2, 2012
Maintenance CDRouter 7.0 Build 138 May 1, 2012


Original release: CDRouter 7.0 Build 102, December 1, 2011

New Features and Enhancements

CDRouter

  • New informational test modules based on nmap

    • Nmap is now integrated into CDRouter! CDRouter 7.0 includes four new Nmap test modules, nmap, nmap-wan, nmap-v6, and nmap-wan-v6, which are designed to provide additional informational about the DUT and how it behaves and appears on the network using the popular Nmap network scanner. The new Nmap test modules perform various nmap port scans on the DUT's LAN and WAN interfaces over both IPv4 and IPv6. Please see the New Test Modules section below for details on the tests included.

    Note that CDRouter's Nmap test module is based on the 5.61 version of Nmap and require a 2.6.35 or newer Linux kernel. Also note that the IPv6 Nmap tests can only be run if the CDRouter IPv6 add-on is installed.

    Important: NTA1000 systems currently do not support Linux kernel versions beyond 2.6.35. Upgrading the kernel to a version beyond version 2.6.35 could cause the NTA1000 to become unbootable, and potentially require a full system reinstall causing the loss of all test configurations and results. Please see our Knowledge Base for instructions on updating the Linux kernel on NTA1000 systems before performing any kernel updates or system upgrades.

    Minimal configuration is required to run the Nmap tests. By default Nmap support is disabled within CDRouter. To enable Nmap the testvar supportsNmap must be set to yes. The testvar nmapScanTimeout is provided which defines the amount of time to wait for an Nmap scan to complete. If the timeout is reached, the scan will be stopped and the test will be marked as a FAIL. This testvar defaults to a value of 900 seconds. The testvar nmapTimingTemplate selects the timing profile that will be used for each scan. Nmap has 6 built in timing templates that adjust retries and timeouts. The values range from 0 to 5. CDRouter uses a default value of 5 which runs the scan as fast as possible. Lowering this value will produce slower scans. Please see Nmap's manual for more information on the timing template option. 

    testvar supportsNmap          yes
testvar nmapScanTimeout       900
testvar nmapTimingTemplate    5

  • Support for 802.1x over wired Ethernet on the LAN

    • In previous releases CDRouter supported 802.1x for wireless LAN interfaces only. CDRouter now supports 802.1x on both wireless and wired Ethernet LAN interfaces. To enable 802.1x on the LAN, set the testvar lanUseEapol to yes and specify the appropriate EAP type using the eapType testvar: 

    # If you are running EAPOL on the lanInterface, configure lanUseEAPOL to yes.
# Otherwise, lanUseEAPOL should be set to no.
#
testvar lanUseEAPOL           no

# Configure the EAP type to use. Supported eapTypes are:
#
#  eap-md5   
#  eap-tls
#  eap-ttls
#  eap-peap
#  eap-sim
#  eap-aka
#
testvar eapType               eap-tls

    CDRouter's RADIUS server is enabled by default on the remoteHost at 3.3.3.3. CDRouter's RADIUS settings can be modified in the RADIUS SETUP section of the config file. Note that when 802.1x is used on an Ethernet LAN interface the eap-radius test module can be run.

  • Support for bridge WAN mode

    • CDRouter can now be used to test devices operating in bridge mode such as wireless access points and DSL CPE devices. To enable bridge mode, set the testvar forwardingMode to bridge: 

    testvar forwardingMode        bridge

    In most scenarios, the DUT's DHCP server will be disabled when configured for bridge mode. As a result, CDRouter will automatically enable its internal DHCP server on the LAN when bridge mode is used. This allows CDRouter's LAN client to obtain an IPv4 address and DNS information. CDRouter's internal DHCP server will assign addresses from the configured DHCP pool and provide the DNS server address specified by the testvar internalDHCPdns: 

    testvar dhcpClientStart       192.168.1.2
testvar dhcpClientEnd         192.168.1.7
testvar internalDHCPdns       1.1.1.1

    Likewise, if IPv6 is enabled, CDRouter will also send router advertisements on the WAN that should be bridged to the LAN so that its LAN IPv6 client can obtain an address. The router advertisements will contain the prefix information specified by the following testvars: 

    testvar ipv6WanIspIp             3001::1
testvar ipv6WanIspPrefixLen      64

    Note that CDRouter can be used to test TR-069, if supported by the DUT in bridge mode. When configured for bridge mode, CDRouter will also automatically skip any test cases or test modules that are not applicable or incompatible.

    Typically, a DUT in bridge mode will obtain an IP address for its management interface using one of the following methods:

    • IPv4: DHCP or static configuration
    • IPv6: DHCP, autoconf, or static configuration

    Likewise, CDRouter supports all of the above WAN modes for bridge mode configurations. In addition, CDRouter also supports a new IPv6 WAN mode of none. This new IPv6 WAN mode is useful for testing IPv6 forwarding on devices that do not support IPv6 directly on their management interface. 

    testvar ipv6WanMode none

    Please see this Application Note for more information on bridge mode testing with CDRouter.

  • Single installer for both 32 bit and 64 bit architectures

    • CDRouter's installer is now compatible with both 32 bit and 64 bit architectures. The new installer is now distributed as a .bin file with the product, release, and build information included in the filename. For example, the CDRouter 7.0 Build 9 installer is named cdrouter-base_7.0-9.bin and is compatible with both 32 and 64 bit architectures. Likewise, the CDRouter Multiport 7.0 build 9 installer is named cdrouter-mp_7.0-9.bin. Note that despite these changes the installation process is unchanged - the installer must be downloaded from the Customer Lounge, made executable using the chmod command, and run from the command line as root or using the sudo command.

  • Support for the carl9170 wireless driver

    • CDRouter now supports the carl9170 native Linux driver for Atheros based USB wireless adapters. This driver is present in Linux kernel versions 3.0+ and replaces the original ar9170usb driver found in pre 3.0 Linux kernels. See the Linux Wireless website for more information.

    CDRouter now supports the ath9k, ar9170usb, and carl9170 native Linux drivers for Atheros based wireless cards. By default, CDRouter will restart any of these wireless drivers automatically during the startup procedure. CDRouter can be configured to not restart the wireless driver by setting the testvar wirelessDriverRestart to a value of no. 

    testvar wirelessDriverRestart no

CDRouter TR-069

  • Support for ACS discovery in DHCP or DHCPv6

    • CDRouter supports ACS discovery as outlined in TR-069 Amendment 3 Section 3.1. This feature is enabled by default when TR-069 is enabled. When the DHCP server receives a client request containing the Vendor Class option 60 with the value "dslforum.org", the DHCP server will include DHCP Vendor Specific option 43 in the response indicating the location of the ACS server. By default, CDRouter will use the format transport://ip_of_acs:port/. This feature is also supported using DHCPv6 using DHCPv6 Vendor Class option 16 and DHCPv6 Vendor Specific option 17. You may also set the ACS URL to a specific value. This may be required when using DNS names or HTTPS transport for your ACS connections. 

    testvar acsDiscoveryUrl https://myserver.foo.com

    ACS Discovery may be turned off by setting the testvar acsDiscoveryUrl to none. For example: 

    testvar acsDiscoveryUrl none

  • Support for TR-157 Amendment 3 profiles

    • CDRouter TR69 now includes support for verifying the data model profiles defined in Broadband Forum TR-157 Amendment 3. The new test cases for TR-157 Amendment 3 have been added to the existing tr157_profiles test module which is included as part of the TR69-EDM add-on for CDRouter TR-069.

  • Updated support for the LAN side devices behind non-TR-069 gateways

    • CDRouter TR-069 now allows the acsCpeConnReqURLMapped testvar to be configured for the primary TR-069 device. In previous releases this testvar was only supported for secondary TR-069 devices. This update is useful for testing TR-069 LAN-side devices that are connected to non-TR-069 enabled gateways. In these scenarios the TR-069 LAN-side device is the primary TR-069 device in CDRouter's config file.

    The acsCpeConnReqURLMapped testvar defines the mapped location of the DUT's TR-069 connection request URL. The DUT's connection request URL must be reachable using a manually created port mapping on the gateway that forwards requests between the mapped connection request URL on the WAN to the DUT's actual connection request on the LAN. For example, if the DUT's connection request URL is http://192.168.1.5:5678/cwmp, and the gateway's public IP is 5.5.5.5, the mapped URL will look like this, assuming port 5678 on the gateway is mapped to port 5678 on LAN host 192.168.1.5: 

    testvar acsCpeConnReqURLMapped  http://5.5.5.5:5678/cwmp

    Note that when the acsCpeConnReqURLMapped testvar is used for the primary TR-069 device, the DUT's OUI and SN must also be configured: 

    
testvar tr69DeviceOui           e09153
testvar tr69DeviceSn            2673964

CDRouter IPv6

  • Support for MLDv1/v2 proxy

    • CDRouter now supports the versions 1 and 2 of IPv6 Multicast Listener Discovery protocol as defined in IETF RFC 2710 and RFC 3810, respectively. In addition, the test module mcast-v6 has been added to the CDRouter IPv6 add-on. The mcast-v6 test module includes 24 new test cases for verifying MLDv1/v2 proxy and pass-through functionality. General information about multicast testing with CDRouter can be found in this Application Note.

    CDRouter's MLD support can be enabled by configuring the testvar supportsIPv6Multicast to "yes". The following configuration options are also available: 

    # ------------------------------------------------------------------------------
#
# SECTION: IPv6 MULTICAST SETUP
#
# ------------------------------------------------------------------------------

# If the DUT supports IPv6 multicast forwarding or proxy functionality, set this
# testvar to 'yes' to enable multicast support within CDRouter.
#
testvar supportsIPv6Multicast yes

# Some CPE devices can only receive multicast on the LAN and can not forward 
# multicast outbound through the WAN interface. If the device does not 
# support outbound multicast, the testvar supportsIPv6MulticastOut can be 
# configured to no. The default is yes.
#
# testvar supportsIPv6MulticastOut no
#

# The MLD version for all LAN clients and the WAN side MLD behavior can be 
# configured using the testvar mldVersion. The default MLD version is 1. 
# Version 2 may also be configured. Some test require MLDv2.
#
# For MLDv1:
# testvar mldVersion 1
#
# For MLDv2:
# testvar mldVersion 2
#

# The maximum number of MLD groups that are supported on the LAN interface
#
testvar mldMaxGroups          64

# The IPv6 multicast cache timeout is used to specify a delay after a host 
# leaves a group before forwarding should stop. Some devices implement a cache 
# function that allows packets to be forwarded for a few seconds after the last 
# host leaves a multicast group.
#
testvar ipv6MulticastCacheTimeout 10


#
# -- MLD Timers
#

# RFC 2710 and RFC 3810 define the following parameters for MLD 
# implementations:
#
# testvar mldQueryInterval          125
# testvar mldRobustnessVariable     2
# testvar mldQueryResponseInterval  10 
#


#
# -- MLD Fast Leave
#

# When MLD Fast Leave is enabled, no group specific MLD query is sent when a 
# host leaves a group and its the only host on a port. Normally, MLD Fast leave
# is used when MLD Snooping is also enabled.
#
# testvar mldFastLeave no
#


#
# -- IPv6 IPTV Configuration Options
#

# The IPv6 multicast test module contains IPTV specific channel change tests. 
# There are a few configuration options available:
#
# The number of channels to change:
#
# testvar ipv6IptvChannelRange 200
#
# The amount of delay in milliseconds between each channel change:
#
# testvar ipv6IptvChannelChangeDelay 200
#
# Stop the channel change test after a specific number of failures:
#
# testvar ipv6IptvMaxFailures 10
#

    In addition, a range of multicast addresses must be configured. These addresses will be used by CDRouter when running various tests in the mcast-v6 test module. 

    testvar ipv6MulticastPoolStart ff0e::1
testvar ipv6MulticastPoolStop ff0e:ffff::

  • Support DS-Lite configurations that provide LAN connectivity via IPv4 only

    • The ipv6LanMode testvar now supports a new mode of none. This mode is useful for testing DS-Lite configurations where the DUT provides all LAN clients with connectivity via IPv4 exclusively. In these configurations the DUT is dual stack on the WAN only; IPv6 connectivity on the WAN is provided for the sole purpose of establishing a DS-Lite tunnel endpoint (aka the B4 element). 

    testvar ipv6LanMode none

    When the testvar ipv6LanMode is set to "none" CDRouter will not attempt to obtain global IPv6 addresses for all LAN clients during the startup sequence.

  • Support for NTP over IPv6

    • CDRouter can provide up to two IPv6 NTP timeservers on the WAN interface. To configure an NTP timeserver, use the ipv6NtpServer1 and ipv6NtpServer2 testvars to configure an IPv6 address for each server. The IPv6 addresses should not be the same as any other network elements such as the ipv6RemoteHost or ipv6WanIspIp. The NTP servers can also be mapped to specific DNS names using the ipv6NtpServerName1 and ipv6NtpServerName2 testvars. 

    testvar ipv6NtpServer1        4321::23
testvar ipv6NtpServerName1    time.nist.gov

testvar ipv6NtpServer2        4321::24
testvar ipv6NtpServerName2    time.foo.com

    By default, CDRouter's NTP servers will use the local time from the CDRouter host. You can specify an offset in seconds to adjust the time forward or backward. 

    
# To move ahead one day:
testvar ntpOffset 86400

# To move back one year:
testvar ntpOffset -31536000

BuddyWeb

  • Drag and drop file imports

    • BuddyWeb file import utility now supports drag and drop! To import a CDRouter results archive, test package, or config file, simply drag it from a browser or folder into the drop box on the Importer page: http://localhost:8015/importer.


New Test Modules and Test Cases

For a complete description of all individual test cases included in CDRouter 7.0, please see the official list of test case summaries for each available product:

The following test modules and test cases are new for CDRouter 7.0:

CDRouter

  • New nmap test modules
    •  
MODULE: nmap.tcl 
NAME: Nmap based IPv4 portscan tests from the LAN side of the device
TEST CASES: 16


    MODULE: nmap-wan.tcl 
NAME: Nmap based IPv4 portscan tests from the WAN side of the device
TEST CASES: 16


    MODULE: nmap-v6.tcl 
NAME: Nmap based IPv6 portscan tests from the LAN side of the device
TEST CASES: 16


    MODULE: nmap-wan-v6.tcl 
NAME: Nmap based IPv6 portscan tests from the WAN side of the device
TEST CASES: 16

CDRouter IPv6

  • New test module for MLD
    • MODULE: mcast-v6.tcl 
DESCRIPTION: MLDv1/v2 and multicast data tests for IPv6 MLD proxy
TEST CASES: 24

CDRouter TR-069

  • New test cases in tr157_profiles module for TR-157 Amendment 3
    • MODULE: tr157_profiles.tcl 
DESCRIPTION: TR-157 CWMP Profile testing for Component Objects
TEST CASES: 129

Bug Fixes and Notes

CDRouter

  • Support for Tcl 8.4 has been deprecated in CDRouter 7.0. Please see this Knowledge Base article for information on upgrading to Tcl 8.5.

  • Fixed an issue with the Config Wizard. In previous releases the PPPoE Configuration window would disappear when the Basic IPv6 Configuration window was opened and enabled. The PPPoE Configuration window is now persistent when the IPv4 WAN mode is set to PPPoE, regardless of the IPv6 settings that are specified.

  • CDRouter's integrated DynDNS server now supports the checkip tool on ports 80 and 8245. In previous releases checkip was supported only on port 80.

  • CDRouter's multicast forwarding implementation has been updated. When forwarding multicast packets, CDRouter will now send a second multicast packet automatically if the first packet is not received. This update allows CDRouter's mcast test module to work with implementations that always drop the first packet when setting up a multicast connection. Note that the new IPv6 MLD test module, mcast-v6, has also been updated with similar functionality.

  • Tests cdrouter_rtsp_1 through cdrouter_rtsp_50 in the apps test module have been updated to include a new QA Cafe defined HTTP session header in all server responses. This modification allows these tests to work with implementations that translate the standard HTTP Session ID header of RTSP packets.

  • CDRouter's L2TP server behavior during the cdrouter_l2tp_5 test case has been modified. CDRouter's L2TP server now better handles L2TP client implementations that actively clean up the tunnel by sending PPP Terminate Request messages to the server.

  • CDRouter's WAN PPPoE server will now ignore NCP Configure-Requests if the IPv4 wanMode is not PPPoE. In previous releases, if PPPoE was enabled on the WAN for IPv6 but not IPv4, CDRouter's PPPoE server would still respond to IPv4 NCP Configure-Requests.

  • CDRouter now ensures that IPsec tunnel connections use a unique SPI identifier in both directions. In prior releases, a single SPI value was used in both directions for the same connection. While this is valid, it is very unlikely to occur in practice and caused problems for some implementations.

  • In conformance with RFC 1661, CDRouter's PPP server has been updated to actively send an LCP Terminate-Request if it rejects a client's authentication credentials.

  • The nat-timeout test module now provides a brief delay before checking whether the DUT has deleted an expired NAT connection. In prior releases, CDRouter would send a test packet on the instant that a NAT connection timeout had elapsed, which caused inconsistent results for some implementations.

  • The logging in test cases dns_45 and dns_46 has been improved. A warning is now printed when the DUT fails over to an alternate DNS server unexpectedly, indicating the reason for the failure of a particular section of the test case.

  • Use of the cdrouter_update_vlan_filter API call is no longer supported. Any custom test cases that use this API call should be updated to use Stack_set_filter and Stack_get_filter calls instead. Please see this Knowledge Base article for more information.

CDRouter Multiport

  • Fixed an issue with multiport configurations involving basic wireless on secondary LAN interfaces. In previous releases CDRouter's wireless restart logic did not handle this specific configuration properly. As a result, CDRouter's wireless interface would not fully initialize leading to a fatal error during startup. This issue only impacted configurations in which a secondary wireless LAN interface was defined.

CDRouter IPv6

  • Resolved an issue in the dhcpv6-pd_14 test case. In previous releases this test case would generate a fatal error if no IPv6 router advertisements were received with the expected prefix.

  • The test ipv6_ndp_30 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_30 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.

  • Resolved an issue when responding to DHCPv6 Solicit messages that contain both IA_PD Prefix and Rapid Commit options. Prior to CDRouter 7.0, the DHCPv6 server would include the received IA_PD Prefix option in its Reply message, and set the preferred-lifetime and valid-lifetime fields to 0. This would be in addition to the IA_PD Prefix option being delegated to the DHCPv6 client. The DHCPv6 server now ignores any IA_PD Prefix options received in Solicit messages.

  • CDRouter's DHCPv6 server has been updated to handle Renew messages that unexpectedly contain an IA_PD Prefix option with an all-zero prefix (eg. "::/56").

  • Test case ipv6_dns_60 has been updated to resolve an issue in which the original DNS servers were not readvertised to the DUT at the end of the test. This only occurred when the ipv6WanMode testvar was set to "PPPoE".

  • Fixed an issue in which the ipv6_frag_2 and ipv6_frag_3 test cases did not properly calculate the MTU for fragmented packets when both PPPoE and VLAN tagging were applied to IPv6 RD or 6-to-4 encapsulated packets, causing a fatal error.

  • Updated the Router Advertisements sent by CDRouter on the WAN when the ipv6WanMode is set to static. In previous releases the M-bit in CDRouter's WAN Router Advertisements would be enabled (ie set to a value of 1). The M-bit is now disabled (set to 0) when static IPv6 addresses are used on the WAN.

  • The icmpv6v_5 test case has been updated to ping the DUT's WAN side global IPv6 address, if present. Previously this test would always attempt to ping the DUT's LAN side global IPv6 address, since it may not have a global address on the WAN in certain configurations (6to4, 6rd, etc.).

  • The startup procedure was updated so that it no longer skips the dhcpv6-pd test module for IPv6 Prefix Delegation when the ipv6WanMode is set to "static"

CDRouter Storage

  • CDRouter Storage has been updated to unset the ftp_proxy and http_proxy environment variables. These environment variables, if set, will be utilized by curl and may cause issues with many of the test cases provided in the CDRouter Storage add-on. This is a follow on to the curl update that was included in Build 107 of CDRouter 6.5.

  • Resolved an issue in which certain configurations could cause a fatal error to occur in test case ipv6_ftp_wan_51 with the message, "Can not find any FTP users with permission type Any".

CDRouter TR-069

  • Resolved an issue in the tr69_200 test case when testing Device 2.0 implementations. In this test case CDRouter attempts to initially set two parameters using with a SetParameterValues RPC. If the SetParameterValues is unsuccessful CDRouter generates a failure message. Originally this failure message had a bad variable reference leading to a 'can't read "path": no such instance' fatal error. This issue has now been resolved.

  • CDRouter will now generate a highlighted warning message if there is a SOAP ID mismatch between the ACS and client. In previous releases a SOAP ID mismatch would result in a test case failure, but the ID mismatch would not be explicitly called out as the reason.

  • All TR-069 related parameter processing associated with the cwmpSkipParameters and cwmpModifyParameters testvars is now done at the start of each test run. This resolves a potential issue in some setups with initialization of CDRouter's test interfaces during the startup procedure. In earlier releases delays associated with parameter processing could prevent CDRouter from properly initializing wireless LAN interfaces in particular.

  • The startup procedure has been updated to resolve an issue in which setting the tr69XMLCapturePath testvar caused a fatal error if the acsIp testvar was not also defined.

Maintenance release: CDRouter 7.0 Build 111, January 4, 2012

Bug Fixes and Notes

CDRouter IPv6

  • The ndp-wan test module does not currently support DHCPv6 relay configurations and is now skipped automatically if DHCPv6 relay is enabled.

  • Resolved an encoding issue with additional DHCPv6 options used by CDRouter's DHCPv6 server on the WAN. Specifically, in previous releases additional DHCPv6 server options, configured using the dhcpv6ServerOptionCodeN and dhcpv6ServerOptionDataN testvars, were not properly encoded by CDRouter in outgoing DHCPv6 Reply messages.

  • In previous releases CDRouter's DHCPv6 server would send DHCPv6 Relay-Reply messages with an empty link-address field in response to received DHCPv6 Relay-Forward messages on the WAN. CDRouter's DHCPv6 server now copies the link-address field from the Relay-Forward message when transmitting Relay-Reply messages. This change only impacts DHCPv6 Relay setups.

  • Addressed a potential fatal error condition in the ipv6_mcast_310 test case.

  • Resolved an MLDv2 issue associated with source specific requests. In previous releases CDRouter would send some MLDv2 Reports in the mcast-v6 test module to the address FF02::1, instead of FF02::16 as required by Section 5.2.14 of RFC 3810.

CDRouter Nmap

  • Warning messages such as "unable to find appropriate interface for system route" no longer cause test cases in the Nmap test module to fail. These messages are related to the system routing table and do not apply to these test cases since CDRouter maintains its own address and routing data structures.

Maintenance release: CDRouter 7.0 Build 117, February 2, 2012

Bug Fixes and Notes

CDRouter

  • Resolved a fatal error produced in WPA-based wireless configurations using EAP-SIM, EAP-AKA, or EAP-MD5 EAP types.

CDRouter IPv6

  • Resolved a logic issue with the icmpv6_5 test case in IPv6 over PPPoE configurations on the WAN with DHCPv6 used for IA_PD only. In previous releases this test case would perform a ping to the DUT's expected WAN-side global IPv6 address which is non-existent in this mode of operation. This test has been updated to now use the DUT's LAN-side global IPv6 address when running in this specific configuration.

  • All tests in frag-v6 test module have been modified to use a fixed IPv6 MTU of 1280 bytes. This change is transparent and should have no impact on CDRouter test results or configuration files.

CDRouter Nmap

  • Updated Nmap to handle ICMPv6 destination unreachable, admin prohibited messages that may result in an EACCESS code. This would previously cause Nmap to assert().


Maintenance release: CDRouter 7.0 Build 119, February 17, 2012

Bug Fixes and Notes

CDRouter IPv6

  • When performing Stateless Address Autoconfiguration, CDRouter will no longer bind to a prefix received in a Router Advertisement if the preferred-lifetime field is 0. Previously, CDRouter ignored this field and would create an address for any prefix advertised as long as the valid-lifetime field was not 0.
  • CDRouter's MLD multicast client has been updated to send the correct type of change record when unsubscribing from a multicast group. Specifically, the client will send a BLOCK_OLD_SOURCES record instead of CHANGE_TO_INCLUDE_MODE when unsubscribing from a group with a non-empty source list.
  • CDRouter's configuration parser now checks to ensure that the ipv6WanIspIp and ipv6WanIspAssignIp testvars share the same prefix. A mismatch will be reported during the start procedure and the test will be stopped to allow the configuration to be corrected.


Maintenance release: CDRouter 7.0 Build 128, March 8, 2012

Bug Fixes and Notes

CDRouter

  • Resolved an issue with wireless adapters that utilize the "DriverLoader" driver set that caused them to filter out inbound IPv6 packets. Please note that the use of DriverLoader with CDRouter has been deprecated as of Release 6.5. For more details, please see the CDRouter 6.5 Release Notes.

BuddyWeb

  • Resolved an issue with BuddyWeb's Drag and Drop feature for importing configs, packages, and results in certain versions of Firefox. Note that the Drag and Drop feature is supported in Firefox versions 4+ only.

CDRouter IPv6

  • CDRouter now verifies whether matching IPv6 prefixes are set when running in environments with multiple router hops on the WAN. If the ipv6WanIspGateway testvar is defined, ipv6WanIspIp must be set to an address in the same prefix. Otherwise, it is assumed that CDRouter and the DUT are directly connected, and ipv6WanIspIp and ipv6WanIspAssignIp must share the same prefix. A mismatch will be reported during the start procedure and the test will be stopped to allow the configuration to be corrected.

Maintenance release: CDRouter 7.0 Build 134, April 2, 2012

Bug Fixes and Notes

BuddyWeb

  • Resolved an issue in which leaving the "Live" page in BuddyWeb open indefinitely could eventually cause a system error of "too many open files" to occur. This was caused by a failure to close a results file each time the "Live" page was automatically refreshed.

CDRouter IPv6

  • The ipv6_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.

  • In previous releases CDRouter would construct the default router's expected LAN link local address based on the source link layer address option received in router advertisements (RA) from the DUT. This method did not handle situations where the RA source link layer address option differed from the IPv6 source address of the packet containing the RA. In these situations certain IPv6 test cases involving the DUT's LAN link local address would fail because packets would be sent by CDRouter to the wrong address. CDRouter now constructs the expected link local address of the DUT on the LAN using the IPv6 source address of the received RA.

  • CDRouter's LAN DHCPv6 client now ignores unique local prefixes advertised by the DHCPv6 server when constructing a global IPv6 address on the LAN. In previous releases CDRouter would in some circumstances build a global IPv6 address based on a unique local prefix if provided by the DHCPv6 server in Advertise messages.

  • When the ipv6WanIspGateway testvar is defined CDRouter now makes an additional configuration check to ensure that not only does it share the same prefix as ipv6WanIspIp, but that the ipv6WanIspAssignIp testvar is in a different prefix. This configuration applies test environments where there are one or more devices between the DUT and CDRouter's WAN interface. Please see this Knowledge Base article for a detailed example.

  • Resolved an issue where CDRouter's IPv6 LAN client would set its IPv6 address based on a received Router Advertisement containing a prefix with a preferred-lifetime of 0. CDRouter will now check both the preferred-lifetime and valid-lifetime fields when attempting to create an IPv6 address, and ignore the prefix if either field is equal to 0.

Maintenance release: CDRouter 7.0 Build 138, May 1, 2012

Bug Fixes and Notes

CDRouter IPv6

  • Resolved an issue where CDRouter failed to age out a cached IPv6 prefix when it received a new Router Advertisement containing the prefix with a preferred-lifetime equal to 0.

CDRouter TR-069

  • The ACS will now ignore HTTP cookies if they are not in a recognized format. In certain test cases, the ACS sets an HTTP cookie on the DUT in order to maintain session continuity across multiple connections. In prior releases, if the ACS received an HTTP cookie from the DUT that did not match the original format, the ACS would stop processing the associated HTTP message. Now, the ACS will simply ignore the cookie and continue to process the received message.

  • The pktsrc API proc ACS_rpc_GetParameterNames has been updated with an additional optional argument called skipValidation. Setting this argument to a value of yes will disable CDRouter's parameter validation when performing GetParameterNames RPCs. Setting it to a value of no, which is the default, will enable parameter validation consistent with CDRouter's previous behavior. 

    proc ACS_rpc_GetParameterNames { stack parameterPath nextLevel nlist { device "" } { skipValidation no } }