Knowledge Base >
Release Notes >
CDRouter 3.2 Release Notes
CDRouter 3.2 Release Notes
Welcome to CDRouter version 3.2!
What's new since version 3.1:
New License Management from Buddy Command-line
----------------------------------------------
* You can now update your CDRouter license file right from the buddy
command-line. The -update-license option will contact the QA Cafe
license server and download the latest copy of the license. This is
useful for updating the license after renewing support or
enabling any add-on modules such as BuddyWeb or CDRouter-IKE.
To update your license, run buddy -update-license
Example:
# buddy -update-license
Check for the Latest Version
----------------------------
* You can now check for the latest version of CDRouter from the
buddy command-line using the -check-version option. When this
option is run, buddy will query qacafe.com for the latest
version.
Example:
# buddy -check-version
New Repeat Option for Test Execution
------------------------------------
* Starting with CDRouter 3.2, you can now use a -scount option to
repeat each test multiple times before continuing on to the new
test.
Example:
# buddy -module nat.tcl -scount 3
The -scount option can also be used with the -rcount which controls
how many loops are made through the entire test list.
# buddy -module nat.tcl -scount 3 -rcount 10
The -scount option is also available through BuddyWeb. In the
package wizard when configuring the Run-Time options, check the
"Run each test times in a row" checkbox under the
"Other options" section. Once enabled, you can enter a count.
For more explaination of the -scount and how -scount and -rcount
are different, please search the knowledge base for "-scount".
http://www.qacafe.com/help
New Test Cases in CDRouter 3.2
------------------------------
* CDRouter 3.2 contains a new renum-pptp.tcl test module that verifies
renumbering and DNS to DHCP interactions when running PPTP. To run
the new test module, enable PPTP and then run:
# buddy -module renum-pptp.tcl
CDRouter 3.2 also contains a bug fix to correctly handle PPTP-DHCP
when the WAN link is reset. The issue previously effected the upnp.tcl
and dyndns.tcl modules when PPTP-DHCP was enabled.
* CDRouter 3.2 contains a new test case in the firewall.tcl module to
verify that the router ignores DNS queries on the WAN interface. The
new test case is cdrouter_firewall_10.
# buddy -execute cdrouter_firewall_10
Multiport Update for multiple LAN subnets
-----------------------------------------
* CDRouter-Multiport 3.2 contains an update that allows each LAN
interface to be configured on a different subnet. To configure
an additional LAN interface on a different subnet, you must
configure a new lanIp and lanMask for the additional interface.
Example. If the router is 192.168.1.1/24 on the first subnet but
has an additional subnet of 192.168.10.1/24.
testvar_group lan2 {
testvar lanInterface eth5
testvar lanType ethernet
testvar lanIp 192.168.10.1
testvar lanMask 255.255.255.0
}
Each interface may also be configured with a unique 802.1q
VLAN id using the testvar lanVlanId.
testvar_group lan2 {
testvar lanInterface eth5
testvar lanType ethernet
testvar lanIp 192.168.10.1
testvar lanMask 255.255.255.0
testvar lanVlanId 100
testvar lanVlanPriority 2
}
CDRouter-IKE adds NAT-Traversal
-------------------------------
* CDRouter-IKE now supports NAT-Traversal and contains a new test module
ike-natt.tcl to verify NAT-Traversal.
Currently, 4 different versions of NAT-T can be configured based on
different version of IETF drafts that resulted in RFC 3947.
To enable NAT-T, the testvar ikeNatTraversal should be configured
to one of the supported versions. The following values are supported:
draft-00
draft-02
draft-03
rfc-3947
no
Example:
testvar ikeNatTraversal draft-03
More details on configuring NAT-T and NAT-T testing can be found in
the CDRouter-IKE User Guide.
Please visit http://www.qacafe.com/cdrouter/cdrouter-ike-user-guide.pdf
BuddyWeb Enhanced for Multiple Test Loops
-----------------------------------------
* Starting in CDRouter 3.2, BuddyWeb now lets the user navigate through
each page of test reults when the "Loop Forever" or "Loop Count"
features are enabled on a package. While the package is running,
BuddyWeb will show the current executing tests by default, but the
user may start viewing test results from eariler loops by turning
off the "follow" mode.
BuddyWeb Scripting
------------------
* The BuddyWeb command-line now contains a new -wait option that makes
it easier to launch multiple BuddyWeb test runs from a script. When
-wait is used on the BuddyWeb command-line, the BuddyWeb command will
not return until the package has finished running.
Example Script:
#!/bin/sh
buddyweb -package config_a -wait
buddyweb -package config_b -wait
buddyweb -package config_c -wait
While the script is running, you may use the BuddyWeb interface to
monitor the results.