Neighbor solicit is not initiated by server after receiving neigbhor advertisement from client
 

My user application uses "linux-4.14.275 version".
Once IPV6 is enabled, my client is getting link-local, global and temporary address. I shall check in cmd prompt (ipconfig). However, in
"ip -6 neigh show", it is showing only link-local address but not the other two addresses (global and temporary).

If I initiate ping to the global address, neighbor got learnt in server side.

But I am expecting global address presence without ping itself. Because Neighbor solicit, advertisement should happen between server and client which should result in learning of all addresses in server side (ip -6 neigh show).
link-local address got learnt, but not global and temporary address.

Root cause analysis:
Client is initiating Neighbor advertisement from those three IP addresses with destination IP as ff02::1. These packets are received on bridge interface. However, neighbor solicit is not initiated from bridge interface. As a result, neighbor learning is not happening for global address.
After above packet reception, server is initiating NS to link-local address separately with proper source IP and dest IP (not multicast IP) which results in Link local address learning. The same is not happening for other two addresses.

If I use linux-3.18.21, issue is not seen. I shall get all three IP addresses learnt as neighbors (ip -6 neigh show).

please share your views for the root cause and what could be the problem in linux-4.14.275 version.

The neighbor is on the local network only. So global IP address of the client doesn't matter whether it show on server.

thanks for the response.

Does it mean, it will learn only link-local address and not global address in neighbor table?
If so, NS will be sent only for link-local address and not for global address?
why linux-3.18.21 version code is sending NS to global address as well?

Thanks.

The global address doesn't need to activate advertisement. The passive learning is fine.