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