#!/usr/bin/perl # # Copyright (C) 1999, 2000, 2001, 2002, 2003, 2004, 2005, 2006 Yokogawa Electric Corporation. # All rights reserved. # # Redistribution and use of this software in source and binary # forms, with or without modification, are permitted provided that # the following conditions and disclaimer are agreed and accepted # by the user: # # 1. Redistributions of source code must retain the above copyright # notice, this list of conditions and the following disclaimer. # # 2. Redistributions in binary form must reproduce the above copyright # notice, this list of conditions and the following disclaimer in # the documentation and/or other materials provided with # the distribution. # # 3. Neither the names of the copyrighters, the name of the project # which is related to this software (hereinafter referred to as # "project") nor the names of the contributors may be used to # endorse or promote products derived from this software without # specific prior written permission. # # 4. No merchantable use may be permitted without prior written # notification to the copyrighters. # # 5. The copyrighters, the project and the contributors may prohibit # the use of this software at any time. # # THIS SOFTWARE IS PROVIDED BY THE COPYRIGHTERS, THE PROJECT AND # CONTRIBUTORS "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING # BUT NOT LIMITED THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS # FOR A PARTICULAR PURPOSE, ARE DISCLAIMED. IN NO EVENT SHALL THE # COPYRIGHTERS, THE PROJECT OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, # INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES # (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR # SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) # HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, # STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING # IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE # POSSIBILITY OF SUCH DAMAGE. # # $TAHI: ct-dhcpv6/dhcpv6.tahi/S_RFC3315_7_Relay-replyMsgFormat.seq,v 1.37 2006/03/09 08:45:57 mnaoki Exp $ ######################################################################## BEGIN { $V6evalTool::TestVersion = '$Name: DHCPv6_1_0 $'; } use strict; use V6evalTool; use DHCPv6_common; use Server_pktdesc; #--------------------------------------------------------------# # Initialization #--------------------------------------------------------------# vLogHTML('==== NUT Initialization ====
'); my $IF0 = "Link0"; #initial NUT config parameters, my %NUT_Server_Config = ( 'if_nut0'=> "$V6evalTool::NutDef{Link0_device}", 'init_opcode' => "vRemote(\"dhcp6s.rmt\", \"start\",\"link0=$V6evalTool::NutDef{Link0_device}\",\"startaddr=3ffe:501:ffff:101::10\",\"endaddr=3ffe:501:ffff:101::11\",\"valduid=$DUID_CLIENT\")" ); dhcpSvrInit(\%NUT_Server_Config); # set Options $CID_OPTION = "opt_CID_LLT_client1"; $IA_NA_OPTION = "opt_IA_NA"; # send DHCPv6 Relay Forward Message(Solicit) my($ret1, %rfsol1) = send_relay_forward($IF0, "relayforward_solicit_client1_to_alldhcp"); if (0 != $ret1){ dhcpExitFail(); } # wait for DHCPv6 Relay Reply Message(Advertise) my ($ret2, %rradv2) = wait_for_relay_reply_advertise($IF0, 5,"relay_reply_nut_relay"); if (0 != $ret2){ dhcpExitFail(); } #------------------------------------------------------------------- vLogHTML("The Format of Relay-reply Message is correct
"); #------------------------------------------------------------------- dhcpExitPass(); #NOTREACHED ######################################################################## __END__ =head1 NAME S_RFC3315_7_Relay-replyMsgFormat.seq - Check Server's Relay-reply Message Format =head1 TARGET Server =head1 SYNOPSIS =begin html
 S_RFC3315_7_Relay-replyMsgFormat.seq [-tooloption ...]
 -pkt S_RFC3315_7_Relay-replyMsgFormat.def  
 -tooloption: v6eval tool option
See Also  DHCPv6.def 
 
=end html =head1 INITIALIZATION =begin html
Link1 ---------------------+---------------- 3ffe:501:ffff:101::/64
                           |
                         TN(Relay1)
                           |
Link0 ---------------------+----------+----- 3ffe:501:ffff:100::/64
                                      |
                                 NUT(Server1)
  
Device Name Device Type I/F Assigned Prefix Link Local Addr MAC Addr
Server1 NUT Link0 3ffe:501:ffff:100::/64 NUT's Linklocal address NUT's MAC address
Relay1(Link0) TN Link0 3ffe:501:ffff:100::/64 fe80::200:ff:fe00:a4a4 00:00:00:00:a4:a4
Relay1(Link1) TN Link1 3ffe:501:ffff:101::/64 fe80::200:ff:fe00:a5a5 00:00:00:00:a5:a5
=end html =head1 TEST PROCEDURE =begin html
	       NUT     TN
	        |       |
	        |       |        initialize NUT (as a DHCPv6 Server)
	        |       |        
	        | <---- |        Relay Forward(Solicit)
	        | ----> |        Relay Reply(Advertise)  (*1)
=end html =head1 JUDGEMENT The server's Reply-reply message(*1 )'s Format must be base on description of RFC(see above Verification Points). =head1 TERMINATION N/A =head1 REFERENCE =begin html
  see also RFC3315
  7. Relay Agent/Server Message Formats
  20.3. Construction of Relay-reply Messages
=end html =head1 SEE ALSO perldoc V6evalTool =cut