(usagi-users 02460) Re: Problem with neighbor solicitation

["Dmitrij Moskalev" <diam@xxxxxxxxx>]

----- Original Message -----
From: "William Sanchez" <wsanchez@xxxxxxxxxxxxxx>
To: <usagi-users@xxxxxxxxxxxxxx>
Sent: 8 июля 2003 г. 21:02
Subject: (usagi-users 02457) Re: Problem with neighbor solicitation


> When you say you added duplicate address, what do you mean, did you
> duplicate the Global address in both machines?
Yes, it is same addresses with same prefixes.
On one host I have:
[diam@rabbit src]$ ifconfig
eth0      Link encap:Ethernet  HWaddr 00:D0:B7:C6:C7:28
          inet addr:192.168.30.215  Bcast:192.168.30.255  Mask:255.255.255.0
          inet6 addr: ::/0 Scope:Global
          inet6 addr: fe80::2d0:b7ff:fec6:c728/64 Scope:Link
          inet6 addr: ::ffff:0:c3d0:3509/96 Scope:Global
          inet6 addr: ::ffff:0:c3d0:350b/96 Scope:Global
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:1613 errors:0 dropped:0 overruns:0 frame:0
          TX packets:750 errors:0 dropped:0 overruns:0 carrier:0
          collisions:1 txqueuelen:100
          RX bytes:106514 (104.0 KiB)  TX bytes:69338 (67.7 KiB)
          Interrupt:11 Base address:0xdf00 Memory:fd7ff000-fd7ff038
on another:

diam@crow:/usr/src$ sudo ifconfig
eth0      Link encap:Ethernet  HWaddr 00:20:AF:38:DA:2F
          inet addr:192.168.30.213  Bcast:192.168.30.255  Mask:255.255.255.0
          inet6 addr: fe80::220:afff:fe38:da2f/64 Scope:Link
          inet6 addr: ::ffff:0:c3d0:350b/96 Scope:Global
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:1946 errors:0 dropped:0 overruns:0 frame:0
          TX packets:478 errors:0 dropped:0 overruns:0 carrier:0
          collisions:1 txqueuelen:100
          RX bytes:141966 (138.6 KiB)  TX bytes:61792 (60.3 KiB)
          Interrupt:5 Base address:0x320

> What version of usagi are you using?
usagi-linux24-s20030512 and  usagi-linux24-s20030623

> For what I can see in the first case you are trying to ping a different
> Global address that is in the same net and it fails
Yes
> while in the other case you are doing a ping to the link local address
> and you are successful, because you are in the same net.
>
No, I don't ping. I just add duplicate address. All packets in this case
host creates without any my participation. And another host answers.
If I ping:

17:13:32.219391 ::ffff:0:c3d0:3509 > ff02::1:ffd0:350b: icmp6: neighbor sol:
>who has ::ffff:0:c3d0:350b
>17:13:33.219385 ::ffff:0:c3d0:3509 > ff02::1:ffd0:350b: icmp6: neighbor
sol:
>who has ::ffff:0:c3d0:350b
>17:13:34.219383 ::ffff:0:c3d0:3509 > ff02::1:ffd0:350b: icmp6: neighbor
sol:
>who has ::ffff:0:c3d0:350b /* There is no answer */

If I add address:
19:32:15.802498 :: > ff02::1:ffd0:350b: icmp6: neighbor sol: who has
>::ffff:0:c3d0:350b
>19:32:15.802827 ::ffff:0:c3d0:350b > ip6-allnodes: icmp6: neighbor adv: tgt
>is ::ffff:0:c3d0:350b           /* Host answered */
>19:32:16.512497 fe80::2d0:b7ff:fec6:c728 > ff02::1:ffd0:350b: HBH icmp6:
>multicast listener report max resp delay: 0 addr: ff02::1:ffd0:350b [hlim
1]

Destination addresses in both cases are the same, but host behavior is
different.

Best regards,
Dmitrij Moskalev,
ISP.