CDRouter 13.15

June 1, 2023


New Features

  • Per Client Performance: Added eight new test cases that enable users to configure unique Performance Testing profiles for each LAN client. Please see the Performance User Guide for more information. [sc2435]

    • perf_client_1
    • perf_client_2
    • perf_client_3
    • perf_client_4
    • ipv6_perf_client_1
    • ipv6_perf_client_2
    • ipv6_perf_client_3
    • ipv6_perf_client_4
  • TR-143: Added 16 test cases for testing multiple connections in TR-143 using the Device.IP.Diagnostics.NumberOfConnections parameter. [sc4347]

    • tr143_http_5
    • tr143_http_6
    • tr143_http_7
    • tr143_http_8
    • tr143_http_15
    • tr143_http_16
    • tr143_http_17
    • tr143_http_18
    • tr143_http_105
    • tr143_http_106
    • tr143_http_107
    • tr143_http_108
    • tr143_http_115
    • tr143_http_116
    • tr143_http_117
    • tr143_http_118
  • Unnumbered IPv6 WAN: The following test cases can now be executed when the ipv6WanMode testvar is set to unnumbered. [sc25079]

    • ipv6_dns_60
    • ipv6_firewall_513
    • ipv6_ndp_34
    • ula_10
    • ula_11
    • ula_13
    • ula_14
    • ipv6_npd_wan_3
    • ipv6_npd_wan_4
    • ipv6_npd_wan_5
    • ipv6_npd_wan_6

Change Log

  • CDRouter: Corrected an error introduced in release 13.14 with the metrics API endpoint of the CDRouter Web API that returned a nil pointer deference error when used. [sc25423]

  • CDRouter: Updated the test pause/unpause feature to have the same behavior when executed from the web UI or cdrouter-cli. [sc25293]

  • CDRouter: Resolved an issue where WAN MAC address stability allocation failed pre-maturely. When stable MAC address allocation fails, CDRouter will continue with randomized MAC addresses. [sc25417]

  • CDRouter: Updated the device connect feature to improve compatibility with more DUTs. [sc25643]

  • CDRouter: Fixed an error that removed quotes from the sslDeprecatedCiphers testvar during a bulk config upgrade. [sc25568]

  • CDRouter: Added the TCP MSS Option to TCP connections for tests verifying the DUT properly forwards both IPv4 and IPv6 packets. This issue was originally discovered in test rfc6092_rec_33 and added to other tests that verify TCP connections. [sc25323]

  • CDRouter: Updated the connectivity_1 test case to generate a warning, instead of a failure, when a link does not go down as part of the test. This improves compatibility in environments where CDRouter isn’t directly connected to the CPE. [sc25325]

  • DOCSIS: Fixed an issue with CDRouter not responding to DOCSIS DHCP Request messages that match the docsisDhcpRelayServer testvar. [sc24939]

  • DOCSIS: After defining the docsisDhcpServer the following testvars all default to the next ip address in the following order: [sc25247]

  • IKE: Fixed a fatal error with IKE timers that occur under specific conditions. [sc24106]

  • Security: The ET Open ruleset shipped with the CDRouter Security expansion has been updated to version 10316. [sc25441]

  • TR-069: Fixed an issue introduced in CDRouter 13.14 with the TR-069 download tests being skipped when the tr69DUInstallImage, tr69DUInstallUUID, and tr69DUChangeExecEnvRef testvars were not enabled in the config. All TR-069 download tests will now run without these testvars being configured. [sc25490]

  • TR-069: Updated the 5_030_redirect_302 and 5_031_redirect_307 test cases to set the periodic inform interval to 60 seconds if it’s configured to be greater than 60. The value is reset at the end of tests. [sc20651]

  • TR-069: Addressed an issue related to DHCP renumbering in bridge mode that caused the DUT to be assigned a new address during renumbering tests. [sc24851]

  • TR-069: Added IPv6 support to tests tr69_210 and tr69_220 using DHCPv6 or PPPoE with DHCPv6 to support renumbering the CPE. [sc4243]

  • TR-069: Updated tests tp181_test_5.3.1 and tp181_test_5.6.1 - tp181_test_5.6.15 to not verify an interface if the GPV on that interface fails. [sc25586] [sc25590]

  • USP: Updated test usp_conformance_11_10 to wait for an MQTT CONNECT message before checking that the EUT sends a DISCONNECT message. This allows more flexibility in the reboot step of the test case, in case a EUT sends a DISCONNECT much later than when a reboot takes place. [sc25404]