
Released on: 2009-12-16
The test case cdrouter_basic_20 now verifies the expected source MAC address used by the DUT on the WAN. To run this test, the new testvar wanDutMac must be enabled within your CDRouter configuration file. This testvar specifies the expected MAC address of the DUT's WAN interface. If the DUT is configured to clone a specific MAC address on the WAN, 00:0b:0b:0b:0b:0b for example, this testvar should match the cloned MAC address. This test case verifies that packets originating from the DUT utilize a specific MAC address.
testvar wanDutMac 00:0b:0b:0b:0b:0b
The test case cdrouter_basic_2 has also been updated with a new success metric. Based on this testvar. If an ARP is received, CDRouter will now also verify that the MAC address in the ARP response matches the expected value as defined by the wanDutMac testvar.
Note that cdrouter_basic_20 will be automatically skipped if the WAN mode is PPPoA or PPP/T1.
The cdrouter_dos_30 and cdrouter_dos_31 test cases use a default value of 80 for the Management Port value, but it can be changed with the testvar dosSynAttackPort:
testvar dosSynAttackPort 80
The latest release of the Ubuntu Linux operating system from Canonical, version 9.10 codenamed Karmic Koala, has been tested for compatibility with CDRouter 6.1 and is now recommended by QA Cafe. CDRouter 6.1 supports both the 32-bit and 64-bit Desktop Editions of Ubuntu 9.10.
The GRE protocol has been updated to handle GRE version 0. Although PPTP uses GRE version 1, the GRE protocol was not checking the version in some cases and GRE version 0 traffic was treated as GRE version 1 traffic.
New test cases have been added to the pppoe-c.tcl, pppoa-c.tcl, l2tp-c.tcl, pptp-c.tcl, and pppt1-c.tcl test modules for verifying that the PPP client is able to maintain the LCP Magic Number throughout a session. If the PPP client does not use the Magic Number options, this test case can be skipped by configuring the testvar pppMagicNumber to no.
testvar pppMagicNumber no
A new test case has been added to the pppoe-c.tcl test module for verifying that the PPPoE client is able to learn and maintain the PPPoE Relay-Session-Id tag throughout a session.
Starting with CDRouter 6.1, testvar names are no longer case sensitive. For example, the following testvar declarations are now processed the same way by CDRouter:
testvar wanMode DHCP testvar wanmode DHCP testvar WANMODE DHCP testvar WanMode DHCP
Test case cdrouter_nat_401 in the nat.tcl module has been updated to include an example Windows 7 based TCP signature.
The testvar portTriggerOpenDelay has been added. This testvar is used to insert a delay before any ports on the WAN are verified as being open following the trigger. This delay is required for some implementations that do not open WAN ports immediately (due to things like firewall settings that must be modified, etc.). This testvar is used only in the triggerp.tcl test module, and specifies a delay in milliseconds.
testvar portTriggerOpenDelay 1000
Note that the similarly named testvar portTriggerDelay is used to specify a delay between testing of individual port trigger rules.
CDRouter now supports static IPv6 WAN configurations. To specify a static IPv6 WAN configuration, set the testvar ipv6WanMode to static, and configure the new testvars ipv6WanIspIp and ipv6WanIspAssignIp:
testvar ipv6WanMode static testvar ipv6WanIspIp 3001::1 testvar ipv6WanIspAssignIp 3001::2
When static IPv6 is used on the WAN, the DUT's LAN IPv6 address and prefix length must also be specified. This is not the case when 6to4 is used on the WAN, since the 6to4 prefix and LAN IP of the DUT are deterministic. The DUT's LAN IP and prefix length, which must be an integer between 8 and 64, can be specified using the following new testvars:
testvar ipv6LanIp 3004::1 testvar ipv6LanPrefixLen 64
When running in static IPv6 mode, CDRouter will automatically skip any test modules and test cases that are not applicable or that verify specific behavior based on dynamic WAN connectivity, such as the 6to4.tcl module.
Note that you may have to alter the LAN configuration to ensure that the DUT's WAN interface and LAN interface are on different IPv6 networks.
CDRouter's IPv6 LAN clients now supports DHCPv6, in addition to autoconf. To enable DHCPv6 on the LAN, set the testvar ipv6LanMode to dhcp and configure the testvars ipv6DhcpClientStart and ipv6DhcpClientEnd to match the starting and ending addresses of the DUT's configured DHCPv6 address pool. In addition, a list of excluded DHCPv6 addresses can also be configured using the testvar ipv6DhcpClientExclude.
testvar ipv6DhcpClientStart 3004::2 testvar ipv6DhcpClientEnd 3004::50 testvar ipv6DhcpClientExclude 3004::11
When DHCPv6 is used on the LAN, CDRouter will automatically enable DHCPv6 on the initial LAN client that is created during the startup procedure. If this initial client is unable to obtain an initial IPv6 address via DHCPv6 during startup, CDRouter will abort the test run.
Note that when DHCPv6 is enabled CDRouter will use the range specified by the ipv6DhcpClientStart and ipv6DhcpClientEnd testvars to determine the validity of the DHCPv6 addresses provided by the DUT. CDRouter will also create a maximum number of DHCPv6 clients based the testvar ipv6MaxLanClients during the scaling-v6.tcl test module.
Note that the DUT's LAN IPv6 address and the DHCPv6 pool range should be in the same IPv6 network.
A list of DHCPv6 options can be configured for use with CDRouter's DHCPv6 client. CDRouter's DHCPv6 client can be configured to provide specific options to the server using the testvars dhcpv6ClientOptionCode and dhcpv6ClientOptionData. Likewise, CDRouter's DHCPv6 client can be configured to request specific options from the server using the testvar dhcpv6ClientOptionRequest
For example, the following testvars configure the client to request DHCPv6 options 21 and 22 from the server and provide the DHCPv6 FQDN option (option 39) to the server with a domain name of qacafe.com:
testvar dhcpv6ClientOptionCode1 39 testvar dhcpv6ClientOptionData1 000671616361666503636f6d00 testvar dhcpv6ClientOptionRequest "21 22"
Two new test cases have been added to the ndp.tcl test module to verify the status of the M and A bits in Router Advertisements sent by the DUT.
The use of site local IPv6 prefixes was depreciated in RFC 3979. CDRouter will now ignore these prefixes when attempting autoconf on any LAN IPv6 clients.
When viewing a Result it is possible to expand the top-section to see more details about the Package. Expanding this section for one result now carries over to other Results for a more consistent experience when browsing through recent runs.
If a results directory is moved or deleted, the user can now go in and update where BuddyWeb should expect to find the test logs.
All types of Resources (Packages, Configurations, and Results) are now uploaded using the same tool. Additionally, support for replacing, renaming, and tagging files as they are uploaded has been revamped and is much easier to use.
The buddyweb command-line tool now has the ability to upload and import files into BuddyWeb, export files, launch packages, and keep track of their status, all from a scriptable CLI command. For more information, please see the BuddyWeb CLI Guide available in the Customer Lounge.
Google has recently release their Chrome web browser for Linux. BuddyWeb is fully supported running in the latest Firefox, Chrome, and Safari browsers on all operating systems.
TEST: Outbound packets use specified/cloned source MAC address MODULE: basic.tcl NAME: cdrouter_basic_20
TEST: PPPoE PPP client maintains LCP Magic Number during session MODULE: pppoe-c.tcl NAME: cdrouter_pppoe_client_60
TEST: PPPoA PPP client maintains LCP Magic Number during session MODULE: pppoa-c.tcl NAME: cdrouter_pppoa_client_60
TEST: PPTP PPP client maintains LCP Magic Number during session MODULE: pptp-c.tcl NAME: cdrouter_pptp_60
TEST: L2TP PPP client maintains LCP Magic Number during session MODULE: l2tp-c.tcl NAME: cdrouter_l2tp_60
TEST: PPP client maintains LCP Magic Number during session MODULE: pppt1-c.tcl NAME: cdrouter_ppp_client_60
TEST: PPPoE client maintains Relay-Session-Id during PPPoE session establishment MODULE: pppoe-c.tcl NAME: cdrouter_pppoe_client_320
TEST: Verify that the DUT is not a Smurf reflector (ICMP attack) MODULE: dos.tcl NAME: cdrouter_dos_20
TEST: Verify that the DUT is not a Fraggle reflector (UDP attack) MODULE: dos.tcl NAME: cdrouter_dos_21
TEST: SYN floods an open port on the DUT from spoofed LAN clients MODULE: dos.tcl NAME: cdrouter_dos_30
TEST: SYN floods an open port on the WAN from spoofed Internet addresses MODULE: dos.tcl NAME: cdrouter_dos_31
TEST: ARP floods the DUT's LAN interface MODULE: dos.tcl NAME: cdrouter_dos_32
TEST: Christmas Tree floods the service ports on the WAN from spoofed Internet addresses MODULE: dos.tcl NAME: cdrouter_dos_33
TEST: Floods the WAN interface with anomalous TCP packets MODULE: dos.tcl NAME: cdrouter_dos_34
TEST: Verify IPv6 Router Advertisements contain M bit based on LAN mode MODULE: ndp.tcl NAME: ipv6_ndp_30 TEST: Verify IPv6 Router Advertisements contain A bit and prefix based on LAN IPv6 settings MODULE: ndp.tcl NAME: ipv6_ndp_31
buddyweb -package myPackage -- -comment 'multi word comment' -comment 'another comment'
testvar dhcpClientMac 00:00:03:04:05:06
INFO(acs): | SSL Alert:bad record mac