<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD><TITLE></TITLE>
<META http-equiv=Content-Type content="text/html; =
charset=us-ascii">
<META content="MSHTML 6.00.2800.1515" name=GENERATOR></HEAD>
<BODY><!-- Converted from text/plain format -->
<P><BR><FONT face="Bookman Old Style" color=#0000ff>Hi,<BR><BR>I did =
the
following steps<BR><BR> 1. Make sure the interface of NUT is
down.<BR> 2. Run the tcpdump at TN.<BR> 3. Activate the =
interface of
NUT.<BR><BR><BR>NUT configuration<BR># ifconfig
eth2<BR>eth2 Link encap:Ethernet =
HWaddr
00:12:79:9E:49:B8<BR> &nbs=
p;
inet6 addr: fe80::212:79ff:fe9e:49b8/64
Scope:Link<BR> UP
BROADCAST RUNNING MULTICAST MTU:1500
Metric:1<BR> RX =
packets:0
errors:0 dropped:0 overruns:0
frame:0<BR> TX =
packets:55
errors:0 dropped:0 overruns:0
carrier:0<BR> =
collisions:0
txqueuelen:1000<BR> =
RX
bytes:0 (0.0 b) TX bytes:4402 (4.2
KiB)<BR> Base
address:0x8040 Memory:c8120000-c8140000<BR><BR><BR>Here is the output of =
Tcpdump
@ TN<BR># tcpdump -i bge0<BR>tcpdump: verbose output suppressed, use -v =
or -vv
for full protocol decode<BR>listening on bge0, link-type EN10MB =
(Ethernet),
capture size 96 bytes<BR>e1000: eth2: e1000_watchdog: NIC Link is Up 100 =
Mbps
Full Duplex<BR>15:53:40.131599 :: > ff02::16: HBH icmp6: type-#143 =
[hlim
1]<BR>15:53:40.131613 :: > ff02::1:ff9e:49b8: icmp6: neighbor sol: =
who has
fe80::212:7<BR>9ff:fe9e:49b8<BR>15:53:40.131618 fe80::212:79ff:fe9e:49b8 =
>
ff02::2: icmp6: router solicitation<BR>15:53:40.131623 =
fe80::212:79ff:fe9e:49b8
> ff02::2: icmp6: router solicitation<BR>15:53:40.131627
fe80::212:79ff:fe9e:49b8 > ff02::2: icmp6: router =
solicitation<BR><BR>Earlier
I misunderstood , Now I think NUT is not generating NS.<BR>Is it a bug =
in the
driver?!!<BR><BR>I think my driver name is <STRONG>e1000. =
</STRONG></FONT></P>
<P><FONT face="Bookman Old Style"
color=#0000ff> <BR><BR><BR>Thanx,<BR>Praveen<BR><BR><BR><BR>-----O=
riginal
Message-----<BR>From: Lobo, Praveen Rajesh (STSD)<BR>Sent: Thursday, =
September
22, 2005 7:50 PM<BR>To: users@tahi.org<BR>Subject: [users:00122] Re: =
IPv6
Conformance Test For Stateless Address Configuration - Failing
why!!<BR><BR><BR>Thanks a lot!!<BR>I tried what ever you told to =
me, I am
getting a single NS and 3 router solicitations. So looks like driver is
perfect.<BR><BR>Thanx,<BR>Praveen<BR><BR><BR>-----Original =
Message-----<BR>From:
Mitsuru Chinen [</FONT><A href="mailto:mitch@jp.ibm.com"><FONT
face="Bookman Old Style">mailto:mitch@jp.ibm.com</FONT></A><FONT
face="Bookman Old Style" color=#0000ff>]<BR>Sent: Thursday, =
September 22, 2005
7:30 PM<BR>To: users@tahi.org<BR>Subject: [users:00121] Re: IPv6 =
Conformance
Test For Stateless Address Configuration - Failing =
why!!<BR><BR>Hi,<BR><BR>Lobo,
Praveen Rajesh (STSD) wrote:<BR>> But the all est cases related =
to
Stateless Address Configuration are<BR><BR>> failing because =
of
NUT , which is not transmitting any DAD NS<BR>packets.<BR>> I =
observed
in tcpdump, NUT is not at all generating any packets<BR>> =
during
execution of these test cases.<BR>> <BR>> Should I need to do =
any
configuration in linux to enable DAD packet<BR>> =
generation?<BR><BR>No, you
don't need to do any configuration.<BR>Why don't you try the simple =
check
without TAHI?<BR>Namely,<BR><BR> 1. Make sure the interface of NUT =
is
down.<BR> 2. Run the tcpdump at TN.<BR> 3. Activate the =
interface of
NUT.<BR><BR>If you cannot see any NSs, you may doubt the network =
driver.<BR>I
heard there were a few drivers which have a bug, they disturbed IPv6 =
protocol
stack when sending NSs.<BR><BR>Best Regards,,<BR>----<BR>Mitsuru Chinen
<mitch@jp.ibm.com><BR><BR><BR><BR><BR></P></FONT></BODY></HTML>