On Tue, Jul 31, 2018 at 05:46:52PM +0300, Vasiliy Tolstov wrote: > > > but server2 have two ipv6 addresses: > > > 6: bond0: <BROADCAST,MULTICAST,MASTER,UP,LOWER_UP> mtu 2044 state UP qlen 1000 > > > inet6 fd00:1::8200:2ff:fe09:fe80/64 scope global dynamic > > > mngtmpaddr noprefixroute > > > valid_lft 86393sec preferred_lft 14393sec > > > > No idea what this is. Did you reboot everything and stop other > > advertising servers? I think you need to tcpdump to investigate this.. > > > > > inet6 fd00:1::221:2800:1a0:cfe2/64 scope global dynamic mngtmpaddr > > > valid_lft 86393sec preferred_lft 14393sec > > > inet6 fe80::221:2800:1a0:cfe2/64 scope link > > > valid_lft forever preferred_lft forever > > > > This looks like it worked to me, the above is the radv address and > > the link local address, both with the correct suffix. > > > > Jason > > Thanks for answer, i'm double check all things. Invalid ipv6 address > generated by kernel on server2, tcpdump: I think you need to figure out where the first address above came from.. If you boot the system without any radv it doesn't show? Then if you start radv on one of the nodes it appears? Jason -- To unsubscribe from this list: send the line "unsubscribe linux-rdma" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
