Hello,
Your thought is right, I think.
It seem that the NUT did not send Rapid Commit option.
Could you check the script(S_RFC3315_5.1_UDPPorts.seq) at line 73.
Is there "$RapidCommit_OPTION = "opt_RapidCommit";"?
If not, the NUT does not send Rapid Commit option.
How about using the attached script instead of original script.
Thanks,
...Hidehshi
On Wed, 14 Mar 2007 11:22:13 +0800
"Rommel Laranjo" <rslaranjo@gmail.com> wrote:
> Hello Hideshi,
>
> I copy-and-pasted some portions of test logs found at 2.html. It seems
> that from the packet information found below, TN did not send a
> rapidcommit option to the server. I am using DHCPv6_Self_Test_1-0 and
> v6eval-3.0.10 and I am doing a manual test. I think this might be the
> reason why the dhcpv6 server(NUT) was not able to send a reply to the
> TN.
>
> Title : UDP Port
> CommandLine : ./S_RFC3315_5.1_UDPPorts.seq -pkt
> ./S_RFC3315_5.1_UDPPorts.def -log 2.html -ti UDP Port
> TestVersion : DHCPv6_1_0
> ToolVersion : REL_3_0_10
> Start : 2007/03/13 11:38:46
> Tn : /usr/local/v6eval//etc//tn.def
> Nu : /usr/local/v6eval//etc//nut.def
> Pkt : ./S_RFC3315_5.1_UDPPorts.def
> System : manual
> TargetName : FreeBSD 6.1-RELEASE + WideDHCP
> HostName : dhcpv6server.infoweapons.com
> Type : host
> .
> .
> .
>
> Send DHCPv6 Solicit Message: CLIENT1 --> all DHCPv6 Servers at
> 11:38:51Frame_Ether (length:84)
> | Hdr_Ether (length:14)
> | | DestinationAddress = 33:33:00:01:00:02
> | | SourceAddress = 00:00:00:00:a2:a2
> | | Type = 34525
> | Packet_IPv6 (length:70)
> | | Hdr_IPv6 (length:40)
> | | | Version = 6
> | | | TrafficClass = 0
> | | | FlowLabel = 0
> | | | PayloadLength = 30
> | | | NextHeader = 17
> | | | HopLimit = 1
> | | | SourceAddress = fe80::200:ff:fe00:a2a2
> | | | DestinationAddress = ff02::1:2
> | | Upp_UDP (length:30)
> | | | Hdr_UDP (length:8)
> | | | | SourcePort = 546
> | | | | DestinationPort = 547
> | | | | Length = 30
> | | | | Checksum = 8776 calc(8776)
> | | | Udp_DHCPv6_Solicit (length:22)
> | | | | Type = 1
> | | | | Identifier = 100
> | | | | Opt_DHCPv6_CID (length:18)
> | | | | | Code = 1
> | | | | | Length = 14
> | | | | | DHCPv6_DUID_LLT_Ether (length:14)
> | | | | | | Type = 1
> | | | | | | HardwareType = 1
> | | | | | | Time = 300000
> | | | | | | LinkLayerAddress = 00:00:00:00:a2:a2
>
> =============
>
> I have tried to view these sites
>
> http://www.tahi.org/dhcpv6/result/server_client_1_0/
> http://www6.tahi.org/dhcpv6/result/server_client_1_0/2.html
>
> they were both using ToolVersion : REL_3_0_8 while the version that I
> am using is REL_3_0_10.
>
>
> Cheers,
>
> Rommel
>
> On 3/9/07, Hideshi.Enokihara@jp.yokogawa.com
> <Hideshi.Enokihara@jp.yokogawa.com> wrote:
> > I'm not really familiar with WIDE-dhcpv6.
> >
> > Could you confirm that the TN really sent rapid commit option in the
> > Solicit message or not, please?
> >
> > I can see the result on
> > http://www.tahi.org/dhcpv6/result/server_client_1_0/ .
> > In these results, TN certainly sends Rapid Commit option.
> >
> > If you don't care about sending the log, could you sent the result to
> > contact@tahi.org?
> >
> > Thanks,
> > ...Hideshi
> > ________________________________
> >
> > From: Rommel Laranjo [mailto:rslaranjo@gmail.com]
> > Sent: Friday, March 09, 2007 5:59 PM
> > To: dhcptest@tahi.org
> > Subject: [dhcptest:00151] Re: dhcptest
> >
> >
> > hideshi,
> >
> > i am really sorry to disturb you but i appreciate so much your
> > kindness and patience in helping me with this test.
> >
> > i have already allow rapid commit in my server, here is my
> > configuration:
> > # cat /usr/local/etc/dhcp6s.conf
> > option refreshtime 5000;
> >
> > interface em0 {
> > allow rapid-commit;
> > address-pool pool1 10000 20000;
> > };
> >
> > pool pool1 {
> > range 3ffe:501:ffff:100::10 to 3ffe:501:ffff:100::11 ;
> > };
> >
> >
> > and this is the debug output during the test... it seems that
> > wide-dhcpv6 did not received the rapid-commit option sent by the TN.
> > Mar/09/2007 16:52:17: received solicit from
> > fe80::200:ff:fe00:a2a2%em0
> > Mar/09/2007 16:52:17: get DHCP option client ID, len 14
> > Mar/09/2007 16:52:17: DUID:
> > 00:01:00:01:00:04:93:e0:00:00:00:00:a2:a2
> > Mar/09/2007 16:52:17: client ID
> > 00:01:00:01:00:04:93:e0:00:00:00:00:a2:a2
> > Mar/09/2007 16:52:17: set client ID (len 14)
> > Mar/09/2007 16:52:17: set server ID (len 14)
> > Mar/09/2007 16:52:17: transmit advertise to
> > fe80::200:ff:fe00:a2a2%em0
> >
> > thanks,
> >
> > Rommel
> >
> >
> >
> > On 3/9/07, Hideshi.Enokihara@jp.yokogawa.com
> > <Hideshi.Enokihara@jp.yokogawa.com> wrote:
> >
> > Hi,
> >
> > In this test, you have to set rapidcommit function in
> > your NUT.
> > > dhcp6s> Please enable the Server to support
> > rapidcommit.
> >
> > The NUT sends Advertise message, not sends Reply if NUT
> > does not support
> > rapidcommit.
> > So, TN says, "Could not get Reply Message".
> >
> > Thanks,
> > ________________________________
> >
> > From: Rommel Laranjo [mailto:rslaranjo@gmail.com
> > <mailto:rslaranjo@gmail.com> ]
> > Sent: Friday, March 09, 2007 12:02 PM
> > To: Enokihara, Hideshi
> > (Hideshi.Enokihara@jp.yokogawa.com);
> > dhcptest@tahi.org <mailto:dhcptest@tahi.org>
> > Subject: [dhcptest:00149] Re: dhcptest
> >
> >
> > hello hideshi,
> >
> > thanks for the reply, the script is now running.
> > now my problem
> > is this,
> > ========== TEST 2 ==========
> > ./S_RFC3315_5.1_UDPPorts.seq -pkt
> > ./S_RFC3315_5.1_UDPPorts.def
> > -log 2.html -ti "UDP Port"
> > ==== NUT Initialization ====
> > vRemote("dhcp6s.rmt",
> >
> > "start","rapidcommit","link0=em0","startaddr=3ffe:501:ffff:100::10","end
> >
> > addr=3ffe:501:ffff:100::11")
> >
> > dhcp6s> Set parameters of DHCPv6 Server manually
> > as following:
> >
> > dhcp6s> The interfaces used for DHCPv6 Server
> > test is em0.
> > dhcp6s> Please set following parameters of IA
> > and IA_address
> > options in DHCPv6 server
> > dhcp6s> prefer-life-time 10000;
> > dhcp6s> valid-life-time 20000
> > dhcp6s> renew-time(T1) 5000
> > dhcp6s> rebind-time(T2) 16000
> > dhcp6s> Please set the start address of
> > which can be
> > assigned:3ffe:501:ffff:100::10.
> > dhcp6s> Please set the end address of
> > which can be
> > assigned:3ffe:501:ffff:100::11.
> > dhcp6s> Please enable the Server to support
> > rapidcommit.
> > dhcp6s>
> >
> > dhcp6s> Please start the DHCPv6 Server!
> > dhcp6s> Then press the Enter.
> >
> > Start Capturing Packets (Link0)
> > Clear Captured Packets (Link0)
> > ==== Solicit/Reply Message Exchange ====
> > Send DHCPv6 Solicit Message: CLIENT1 -->
> > all DHCPv6
> > Servers
> > Solicit Message
> >
> > DHCPv6 OptionValues
> > IdentifierIdentifier = 100
> > Opt_DHCPv6_CIDDUID-LLT HardwareType = 1
> > DUID-LLT MAC = 00:00:00:00:a2:a2
> > DUID-LLT TIME = 300000
> >
> > Could not get Reply Message
> > NUT did not send Reply Message.
> > NG
> > DHCPv6 Server stop
> > ===========================================
> > It says that the NUT did not send Reply Message,
> > but when i try
> > to run my dhcp6s with -dDf it said "transmit advertise
> > to
> > fe80::200:ff:fe00:a2a2%em0" ...
> >
> > So with this, it seems that my TN did not
> > received the
> > advertise. :(
> >
> > May I ask what could possibly be the problem?
> >
> > Thanks alot,
> >
> > Rommel
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
>
--
*************************************
Hideshi Enokihara
IPv6 Business
Network & Software Development Dept.
Yokogawa Electric Corporation
158_2.seq