[Dibbler] FW: DHCPv6 issue

[nagarajan.balamukundan at wipro.com]

Hi All,

     I'm facing a problem in using my DHCPv6 cilent. The client is
running on VxWorks platform and I've setup a Dibbler server on a Win
2003 machine. It's solicit messages are recognized and it goes on to
form the Advertisement. But the packet doesn't come out in the network.
But the response may just start coming randomly. There is no certainty
that on a given attempt I get back the advertisement. But if I do go on
to receive advertisement, the complete message exchange including
REQUEST, REPLY, goes on. Please can anyone suggest what is the solution.


   I'm attaching the server logs and a copy of the configuration file of
the server. 



| Dibbler - a portable DHCPv6, version 0.4.1 (SERVER, WinXP/2003 port)

| Authors : Tomasz Mrugalski<thomson(at)klub.com.pl>,Marek
Senderski<msend(at)o2

.pl>

| Licence : GNU GPL v2 or later. Developed at Gdansk University of
Technology.

| Homepage: http://klub.com.pl/dhcpv6/



22:12:30 Notice    Windows 2003 detected (majorVersion=5,
minorVersion=2), so this is proper port.

22:12:30 Critical  | Dibbler - a portable DHCPv6, version 0.4.1 (SERVER,
WinXP/2003 port)

22:12:31 Notice    Detected iface Teredo Tunneling Pseudo-Interface/5,
MAC=ff:ff:ff:ff:ff:ff:ff:ff.

22:12:31 Notice    Detected iface ToshibaLab/4, MAC=00:13:d4:96:78:fa.

22:12:31 Notice    Detected iface 6to4 Pseudo-Interface/3,
MAC=00:13:d4:96.

22:12:31 Notice    Detected iface Automatic Tunneling
Pseudo-Interface/2, MAC=0a:65:41:9d.

22:12:31 Notice    Detected iface Loopback Pseudo-Interface/1, MAC=.

22:12:31 Notice    Parsing C:\dibbler\server.conf config file...

22:12:31 Debug     Parsing C:\dibbler\server.conf done.

22:12:31 Debug     1 interface(s) specified in server.conf

22:12:31 Info      Interface ToshibaLab/4 configuration has been loaded.

22:12:31 Notice    Running in stateful mode.

22:12:31 Info      My duid is 00:01:00:06:45:4f:51:7b:00:13:d4:96:78:fa.

22:12:31 Notice    Creating multicast (ff02::1:2) socket on ToshibaLab/4
(ToshibaLab/4) interface.

22:12:31 Notice    Accepting connections. Next event in 2147483647
second(s).

22:13:22 Debug     Received 40 bytes on interface ToshibaLab/4
(socket=328, addr=fe80::280:91ff:fe43:12b.).

22:13:22 Warning   Option type 25 invalid. Option ignored.

22:13:22 Notice    Received SOLICIT on ToshibaLab/4,TransID=0x6a5e, 2
opts: 1 8, 0 relay(s).

22:13:22 Debug     0 answers buffered. Old reply for transID=6a5e not
found. Generating new answer.

22:13:22 Debug     Preference set to 0.

22:13:22 Notice    Sending ADVERTISE on ToshibaLab/4,transID=0x6a5e,
opts: 1 2 7, 0 relay(s).

22:13:23 Notice    Accepting connections. Next event in 2147483647
second(s).

22:13:24 Debug     Received 40 bytes on interface ToshibaLab/4
(socket=328, addr=fe80::280:91ff:fe43:12b.).

22:13:24 Warning   Option type 25 invalid. Option ignored.

22:13:24 Notice    Received SOLICIT on ToshibaLab/4,TransID=0x6a5e, 2
opts: 1 8, 0 relay(s).

22:13:24 Debug     0 answers buffered. Old reply for transID=6a5e not
found. Generating new answer.

22:13:24 Debug     Preference set to 0.

22:13:24 Notice    Sending ADVERTISE on ToshibaLab/4,transID=0x6a5e,
opts: 1 2 7, 0 relay(s).

22:13:24 Notice    Accepting connections. Next event in 2147483647
second(s).

22:13:26 Debug     Received 40 bytes on interface ToshibaLab/4
(socket=328, addr=fe80::280:91ff:fe43:12b.).

22:13:26 Warning   Option type 25 invalid. Option ignored.

22:13:26 Notice    Received SOLICIT on ToshibaLab/4,TransID=0x6a5e, 2
opts: 1 8, 0 relay(s).

22:13:26 Debug     0 answers buffered. Old reply for transID=6a5e not
found. Generating new answer.

22:13:26 Debug     Preference set to 0.

22:13:26 Notice    Sending ADVERTISE on ToshibaLab/4,transID=0x6a5e,
opts: 1 2 7, 0 relay(s).

22:13:26 Notice    Accepting connections. Next event in 2147483647
second(s).

22:13:30 Debug     Received 40 bytes on interface ToshibaLab/4
(socket=328, addr=fe80::280:91ff:fe43:12b.).

22:13:30 Warning   Option type 25 invalid. Option ignored.

22:13:30 Notice    Received SOLICIT on ToshibaLab/4,TransID=0x6a5e, 2
opts: 1 8, 0 relay(s).

22:13:30 Debug     0 answers buffered. Old reply for transID=6a5e not
found. Generating new answer.

22:13:30 Debug     Preference set to 0.

22:13:30 Notice    Sending ADVERTISE on ToshibaLab/4,transID=0x6a5e,
opts: 1 2 7, 0 relay(s).

22:13:30 Notice    Accepting connections. Next event in 2147483647
second(s).









As can be seen above, the Server logs suggest that the Advertisement is
being sent, but the corresponding packets cannot be captured on
Ethereal, and so the client goes on retransmitting the solicit.





The following is the server conf file at my end.



log-level 7

log-mode short



iface "Local Area Connection" {



# clients should renew every half an hour

 rapid-commit yes

 T1 1800

 T2 2000

 prefered-lifetime 3600

 valid-lifetime 7200

 class {

   pool 2000::1-2000::ff

 }



 option dns-server 2000::100,2000::101

 option domain example.com, test1.example.com



}





Please look into this issue and revert back to me with a solution as
soon as possible.



Thanking you all,



Regards,

B.Nagarajan






The information contained in this electronic message and any attachments to this message are intended for the exclusive use of the addressee(s) and may contain proprietary, confidential or privileged information. If you are not the intended recipient, you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately and destroy all copies of this message and any attachments.

WARNING: Computer viruses can be transmitted via email. The recipient should check this email and any attachments for the presence of viruses. The company accepts no liability for any damage caused by any virus transmitted by this email.

www.wipro.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://klub.com.pl/pipermail/dibbler/attachments/20061112/39472af2/attachment.htm