[radvd-devel-l] Question on NDP

Pekka Savola radvd-devel-l@litech.org
Wed, 13 Nov 2002 13:24:12 +0200 (EET)

On Wed, 13 Nov 2002, Pedro Mart=EDnez wrote:
> I don't know if this is the right place to ask about some aspects=20
> related to the Neighbor Discovery Protocol. Actually, this is the=20
> closest thing I have been able to find. If you think this list is not=20
> suitable enough, please indicate me where I should address my doubts.
> I have a problem to solve. This problem is that I need to know the MAC=20
> addresses of all of my neighbors by sending a single message. I though=20
> of NDP as a possible solution. I thought that by sending the Neighbor=20
> solicitation to the multicast group=20
> {0xff,0x02,0,0,0,0,0,0,0,0,0,0,0,0,0,1} would be enough, but it isn't=20
> so. My idea was sending this message to the multicast address and the=20
> sender would receive an answer by every neighbor receiving its request.
> Can you help me with this?. Do you know any other solution to my proble=

sampo2 ~/> ping6 -I eth0 ff02::1
PING ff02::1(ff02::1) from fe80::204:76ff:fef2:ee93 eth0: 56 data bytes
64 bytes from ::1: icmp_seq=3D1 ttl=3D64 time=3D0.081 ms
64 bytes from fe80::202:55ff:fefa:239e: icmp_seq=3D1 ttl=3D64 time=3D0.50=
2 ms (DUP!)
64 bytes from fe80::202:b3ff:fe8b:584f: icmp_seq=3D1 ttl=3D64 time=3D0.54=
7 ms (DUP!)
64 bytes from fe80::200:f8ff:fe08:3e0d: icmp_seq=3D1 ttl=3D64 time=3D0.61=
7 ms (DUP!)
64 bytes from fe80::201:2ff:fe75:686c: icmp_seq=3D1 ttl=3D64 time=3D0.639=
 ms (DUP!)
64 bytes from fe80::210:5aff:fe70:3d8f: icmp_seq=3D1 ttl=3D64 time=3D0.64=
9 ms (DUP!)
64 bytes from fe80::250:4ff:fe63:983b: icmp_seq=3D1 ttl=3D64 time=3D0.666=
 ms (DUP!)
64 bytes from fe80::250:4ff:fe4a:8c19: icmp_seq=3D1 ttl=3D64 time=3D0.793=
 ms (DUP!)
64 bytes from fe80::201:2ff:fe54:bede: icmp_seq=3D1 ttl=3D64 time=3D1.36 =
ms (DUP!)
64 bytes from fe80::250:4ff:fe8e:8e49: icmp_seq=3D1 ttl=3D64 time=3D2.08 =
ms (DUP!)

--- ff02::1 ping statistics ---
1 packets transmitted, 1 received, +9 duplicates, 0% loss, time 0ms
rtt min/avg/max/mdev =3D 0.081/0.794/2.083/0.524 ms

sampo2 ~/> /sbin/ip -6 n l
fe80::250:4ff:fe8e:8e49 dev eth0 lladdr 00:50:04:8e:8e:49 nud stale
2001:708:10:10::1 dev eth0 lladdr 00:00:f8:08:3e:0d router nud reachable
fe80::250:4ff:fe4a:8c19 dev eth0 lladdr 00:50:04:4a:8c:19 nud stale
fe80::202:b3ff:fe8b:584f dev eth0 lladdr 00:02:b3:8b:58:4f nud stale
fe80::202:55ff:fefa:239e dev eth0 lladdr 00:02:55:fa:23:9e nud stale
fe80::201:2ff:fe54:bede dev eth0 lladdr 00:01:02:54:be:de nud stale
fe80::201:2ff:fe10:87a4 dev eth0 lladdr 00:01:02:10:87:a4 nud stale
fe80::210:5aff:fe70:3d8f dev eth0 lladdr 00:10:5a:70:3d:8f nud stale
fe80::250:4ff:fe63:983b dev eth0 lladdr 00:50:04:63:98:3b nud stale
fe80::230:65ff:fe79:8836 dev eth0 lladdr 00:30:65:79:88:36 nud stale
fe80::201:2ff:fe75:686c dev eth0 lladdr 00:01:02:75:68:6c nud stale
fe80::200:f8ff:fe08:3e0d dev eth0 lladdr 00:00:f8:08:3e:0d nud stale

perhaps this is a useful tip.

Pekka Savola                 "Tell me of difficulties surmounted,
Netcore Oy                   not those you stumble over and fall"
Systems. Networks. Security.  -- Robert Jordan: A Crown of Swords