Knowledge Base >
CDRouter 2.8 Release Notes
CDRouter 2.8 Release Notes
Release Notes
Welcome to CDRouter version 2.8!
What's new since version 2.7.1:
SIP ALG/Proxy Testing
---------------------
* CDRouter 2.8 introduces a new test module (sip-alg.tcl) for SIP
verification of routers that support a SIP ALG or proxy through
NAT. CDRouter contains 22 new test cases specific to SIP. CDRouter
includes a built in SIP client and proxy. Test scenerios will
verify the NAT translation of SIP headers fiels and SDP data.
CDRouter will also initiate RTP streams to verify VoIP traffic.
The following testvars are available to control SIP testing:
#
# -- SIP ALG support
#
# If the router supports a SIP ALG or Proxy through NAT, configure the
# testvar supportsSipAlg to yes. Set to no otherwise.
#
testvar supportsSipAlg yes
#
# The amount of time to wait for an RTP port mapping to be deleted after
# a SIP call has ended can be configured using testvar
# sipCallTeardownDelay. If the ALG uses the default UDP traffic
# timeout, this value should be configured to same timeout as the
# UDP timeout (see testvar natUdpTimeout).
#
testvar sipCallTeardownDelay 5
#
# The maximum number of outbound and inbound SIP calls to attempt.
#
testvar sipMaxOutboundCalls 10
testvar sipMaxInboundCalls 10
#
# The rate of SIP call establishment can be slowed down by configuring the
# testvar sipCallPacing to a number of milliseconds to delay before
# establishing a new SIP call.
#
# testvar sipCallPacing 0
#
#
# The duration of the SIP scaling tests can be modified by configuring the
# testvar sipScaleRunTime to the number of seconds to run the test. The
# default value is 30 seconds.
#
# testvar sipScaleRunTime 30
#
# To limit the number of SIP user names that CDRouter will create, set
# the testvar sipMaxUserNames to the limit value. By default, CDRouter
# will create a unique name of phone number for each test case. Some
# routers will SIP proxy support limit the number of unique users
# that can be registered.
#
# testvar sipMaxUserNames 10
#
RIPv2 Broadcast
---------------
* CDRouter now supports RIPv2 broadcast mode for all RIP testing. To
configure RIPv2 broadcast mode, configure the testvar ripV2mode
to broadcast. When the RIPv2 mode is set to broadcast, CDRouter will
send RIP updates to network broadcast address. When the RIPv2
mode is set to multicast, CDRouter will send RIP updates to the
multicast address 224.0.0.9. The default value is multicast.
Example:
testvar ripV2mode broadcast
Other 2.8 Features
------------------
Several other minor enhancements have also been added to 2.8:
* User comments can now be logged to the test log and HTML report
using the -comment option with buddy.
Example:
% buddy -config pppoe.conf -comment "Testing image 2.3.bin"
* In test case cdrouter_nat_150, a new testvar called natTcpPortDelay
can be used to add a delay between the reuse of the same
TCP port number. It defaults to 1 second.
* In test case cdrouter_nat_130, the behavior of src port 0 is
now configurable. Some routers will always drop src port 0 packets
by design. If the router under test does not support forwarding
src port 0 connections through NAT, the testvar natSrcPort0 may
be configured to "no". When set to "no", the test case will
expected these connections to fail. The default setting for
natSrcPort0 is yes.
testvar natSrcPort0 no
* UDP port scans and DMZ verification now send real UDP application
data for ports 53 (DNS), 69 (TFTP), 161 (SNMP), 517 (talk), and
518 (ntalk).
* New keywords for the testcase start and stop time text strings
are now available for template files.
%TESTCASE_STARTTIME_STR%
%TESTCASE_STOPTIME_STR%
These will be expanded to the start and stop times when a test
case runs. Please see "Report Templates" section in Chapter 9 of
the User Guide.
* DHCPREQUEST messages sent during the RENEW action no longer
include the "server identifier" and "requested IP address"
options per RFC 2131.
What's new since version 2.7:
CDRouter version 2.7.1 is primarily the same as release as
CDRouter 2.7 with a few functional changes and bug fixes
explained below. Two new test cases have also been
introduced to verify the attributes and behavior of the
GetStatusInfo UPnP Action.
* The UPnP event receiver now supports NOTIFY events that
use Transfer-Encoding: chunked. Previously, CDRouter would
not wait for the entired XML body when the chunked
encoding was used.
* The UPnP event server now handles implementations that
send each variable in a seperate NOTIFY message. Previously,
the ConnectionStatus and NewExternalIPAddress needed
to be sent in the same NOTIFY message.
* The UPnP client now includes the 'Connection: Close'
header in all SOAP requests.
* The PPPoE server now includes the session-relay-id TAG
in any PPPoE Discovery responses from the client as
per RFC 2516.
* All CHAP based protocols (CHAP, MSCHAP, MSCHAPv2) will
now retransmit additional CHAP challenges when waiting
for the PPP link to recover.
* The GRE packet summary (used when -pt is enabled) now
displays the GRE Ack number when no upper layer data
is included.
New UPnP GetStatusInfo Action test cases
----------------------------------------
TEST 189: Verify UPnP GetStatusInfo Action returns correct ConnectionStatus information
MODULE: upnp.tcl
NAME: cdrouter_upnp_31
TEST 190: Verify UPnP GetStatusInfo Action returns increasing Uptime value
MODULE: upnp.tcl
NAME: cdrouter_upnp_32
Related articles that may also be helpful:
