ipv6 : why ndp resolves to global scope address?

Posted by Julien on Server Fault See other posts from Server Fault or by Julien
Published on 2014-08-21T08:59:57Z Indexed on 2014/08/21 10:21 UTC
Read the original article Hit count: 397

Filed under:
|
|

I'm facing a strange ipv6 behavior and I don't know how to solve it because I'm not familiar with ipv6. Maybe this behavior is normal. I hope that you will help me. ( I'm running under debian 6.0.9 with a custom kernel 3.2.58 )

machine A is "2a00:7d30:edf6:100::1" wants to ping machine B, which is "2a00:7d30:edf6:100::10". Both are on the same segment.

machine A asks for the address of machine B and I don't understand why machine B gives its global scope address instead of the local scope one ?

10:59:02.082785 IP6 2a00:7d30:edf6:100::1 > ff02::1:ff00:10: ICMP6, neighbor solicitation, who has 2a00:7d30:edf6:100::10, length 32

10:59:02.082821 IP6 2a00:7d30:edf6:100::10 > 2a00:7d30:edf6:100::1: ICMP6, neighbor advertisement, tgt is 2a00:7d30:edf6:100::10, length 32

after that machine A pings the global scope address of machine B and it works fine :

10:59:02.082927 IP6 2a00:7d30:edf6:100::1 > 2a00:7d30:edf6:100::10: ICMP6, echo request, seq 1, length 64

10:59:02.082960 IP6 2a00:7d30:edf6:100::10 > 2a00:7d30:edf6:100::1: ICMP6, echo reply, seq 1, length 64

Thank you for you help best regards Julien

© Server Fault or respective owner

Related posts about IPv6

Related posts about scope