On Thu, Jul 12, 2018 at 12:40:16AM +0300, Vasiliy Tolstov wrote: > Hi again. I have problem with ipv6 slaac address on my servers with > fedora 28 (4.16.14-300.fc28.x86_64). > server 1: > link/infiniband > 80:00:02:08:fe:80:00:00:00:00:00:00:00:21:28:00:01:a0:99:bd brd > 00:ff:ff:ff:ff:12:40:1b:ff:ff:00:00:00:00:00:00:ff:ff:ff:ff > link/infiniband > 80:00:02:09:fe:80:00:00:00:00:00:00:00:21:28:00:01:a0:99:be brd > 00:ff:ff:ff:ff:12:40:1b:ff:ff:00:00:00:00:00:00:ff:ff:ff:ff > > server 2: > link/infiniband > 80:00:02:08:fe:80:00:00:00:00:00:00:00:21:28:00:01:a0:cf:e1 brd > 00:ff:ff:ff:ff:12:40:1b:ff:ff:00:00:00:00:00:00:ff:ff:ff:ff > link/infiniband > 80:00:02:09:fe:80:00:00:00:00:00:00:00:21:28:00:01:a0:cf:e2 brd > 00:ff:ff:ff:ff:12:40:1b:ff:ff:00:00:00:00:00:00:ff:ff:ff:ff > > > On server 3 with subnet manager i'm install bird and send ra: 2001:db8:1::/64 > > server 2 succeseful configure ipv6 address, but server 1 not. > messages from server 1: > [1372976.977527] ICMPv6: RA: ndisc_router_discovery failed to add default route > [1372977.632880] IPv6: bond0: IPv6 duplicate address > 2001:db8:1:0:8200:2ff:fe09:fe80 used by 00:00:00:00:00:00 detected! > > because on all ib devices hw address begins with: > 80:00:02:09:fe:80 (8200:2ff:fe09:fe80 in slaac) What is the link local address? Things handling HW addresses have to have special support for how to map the 20 byte IB HW adress into an EUI-64 - the kernel has this support and creates correct link-local addresses (see ipv6_generate_eui64) I'm guessing there is something wrong with BIRD, but I don't recall all the details of how stateless autoconfiguration works.. Maybe a wireshark dump of the SLAAC exchange would be informative. 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
