<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
Continuing forward, these patches should've fixed that
<a class="moz-txt-link-freetext" href="https://review.openstack.org/#/q/topic:bug/1667756+(status:open+OR+status:merged)">https://review.openstack.org/#/q/topic:bug/1667756+(status:open+OR+status:merged)</a><br>
I'm on Queens.<br>
<br>
The two inside interfaces on the backup router:<br>
[root@controller2 ~]# ip netns exec
qrouter-0775785e-a93a-4501-917b-be92ff03f36a cat
/proc/sys/net/ipv6/conf/qr-7fad6b1b-c9/accept_ra<br>
1<br>
[root@controller2 ~]# ip netns exec
qrouter-0775785e-a93a-4501-917b-be92ff03f36a cat
/proc/sys/net/ipv6/conf/qr-5be04815-68/accept_ra<br>
1<br>
<br>
Perhaps the accept_ra patches does not apply for enable/disable or
routers changing from a normal router to a L3 HA router?<br>
Best regards<br>
<br>
<div class="moz-cite-prefix">On 08/20/2018 11:50 AM, Tobias Urdin
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:4e1f27a4-cd70-4ad4-5249-20b18e1dab76@binero.se">
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
Ok, so the issue here seems to be that I have a L3 HA router with
SLAAC, both the active and standby router will<br>
configure the SLAAC obtained address causing a conflict since both
side share the same MAC address.<br>
<br>
Is there any workaround for this? Should SLAAC even be enabled for
interfaces on the standby router?<br>
<br>
Best regards<br>
Tobias<br>
<br>
<div class="moz-cite-prefix">On 08/20/2018 11:37 AM, Tobias Urdin
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:e512b55c-e828-3939-d72e-bd3cfb5da1dc@binero.se">
Forgot [neutron] tag.<br>
<br>
<div class="moz-cite-prefix">On 08/20/2018 11:36 AM, Tobias
Urdin wrote:<br>
</div>
<blockquote type="cite"
cite="mid:07d859f1-034e-d3b4-7fc0-0c7b087056a4@binero.se">
Hello,<br>
<br>
Note: before reading, this router was a regular router but was
then disable, changed ha=true so it's now a L3 HA router, then
it was enabled again.<br>
CC openstack-dev for help or feedback if it's a possible bug.<br>
<br>
I've been testing around with IPv6 and overall the experience
has been positive but I've met some weird issue that I cannot
put my head around.<br>
So this is a neutron L3 router with an outside interface with
a ipv4 and ipv6 from the provider network and one inside
interface for ipv4 and one inside interface for ipv6.<br>
<br>
The instances for some reason get's there default gateway as
the ipv6 link-local (in fe80::/10) from the router with SLAAC
and radvd.<br>
<br>
(1111.2222 is provider network, 1111.4444 is inside network,
they are masked so don't pay attention to the number per se)<br>
<br>
<b>interfaces inside router:</b><br>
15: ha-9bde1bb1-bd: <BROADCAST,MULTICAST,UP,LOWER_UP>
mtu 1450 qdisc noqueue state UNKNOWN group default qlen 1000<br>
link/ether fa:16:3e:05:80:32 brd ff:ff:ff:ff:ff:ff<br>
inet 169.254.192.7/18 brd 169.254.255.255 scope global
ha-9bde1bb1-bd<br>
valid_lft forever preferred_lft forever<br>
inet 169.254.0.1/24 scope global ha-9bde1bb1-bd<br>
valid_lft forever preferred_lft forever<br>
inet6 fe80::f816:3eff:fe05:8032/64 scope link <br>
valid_lft forever preferred_lft forever<br>
19: qg-86e465f6-33: <BROADCAST,MULTICAST,UP,LOWER_UP>
mtu 1500 qdisc noqueue state UNKNOWN group default qlen 1000<br>
link/ether fa:16:3e:3b:8b:a5 brd ff:ff:ff:ff:ff:ff<br>
inet 1.2.3.4/22 scope global qg-86e465f6-33<br>
valid_lft forever preferred_lft forever<br>
inet6 1111:2222::f/64 scope global nodad <br>
valid_lft forever preferred_lft forever<br>
inet6 fe80::f816:3eff:fe3b:8ba5/64 scope link nodad <br>
valid_lft forever preferred_lft forever<br>
1168: qr-5be04815-68: <BROADCAST,MULTICAST,UP,LOWER_UP>
mtu 1450 qdisc noqueue state UNKNOWN group default qlen 1000<br>
link/ether fa:16:3e:c3:85:bd brd ff:ff:ff:ff:ff:ff<br>
inet 192.168.99.1/24 scope global qr-5be04815-68<br>
valid_lft forever preferred_lft forever<br>
inet6 fe80::f816:3eff:fec3:85bd/64 scope link <br>
valid_lft forever preferred_lft forever<br>
1169: qr-7fad6b1b-c9: <BROADCAST,MULTICAST,UP,LOWER_UP>
mtu 1450 qdisc noqueue state UNKNOWN group default qlen 1000<br>
link/ether fa:16:3e:66:de:a8 brd ff:ff:ff:ff:ff:ff<br>
inet6 1111:4444:0:1::1/64 scope global nodad <br>
valid_lft forever preferred_lft forever<br>
inet6 fe80::f816:3eff:fe66:dea8/64 scope link <br>
valid_lft forever preferred_lft forever<br>
<br>
I get this error messages in dmesg on the network node:<br>
[581085.858869] IPv6: qr-5be04815-68: IPv6 duplicate address
1111:4444:0:1:f816:3eff:fec3:85bd detected!<br>
[581085.997497] IPv6: qr-7fad6b1b-c9: IPv6 duplicate address
1111:4444:0:1:f816:3eff:fe66:dea8 detected!<br>
[581142.869939] IPv6: qr-5be04815-68: IPv6 duplicate address
1111:4444:0:1:f816:3eff:fec3:85bd detected!<br>
[581143.182371] IPv6: qr-7fad6b1b-c9: IPv6 duplicate address
1111:4444:0:1:f816:3eff:fe66:dea8 detected!<br>
<br>
<b>radvd:</b><br>
interface qr-7fad6b1b-c9<br>
{<br>
AdvSendAdvert on;<br>
MinRtrAdvInterval 30;<br>
MaxRtrAdvInterval 100;<br>
<br>
AdvLinkMTU 1450;<br>
<br>
RDNSS 2001:4860:4860::8888 {};<br>
<br>
prefix 1111:4444:0:1::/64<br>
{<br>
AdvOnLink on;<br>
AdvAutonomous on;<br>
};<br>
};<br>
<br>
<b>inside instance:</b><br>
ipv4 = 192.168.199.7<br>
ipv6 = 1111:4444:0:1:f816:3eff:fe29:723d/64 (from radvd SLAAC)<br>
<br>
I can ping ipv4 gateway 192.168.199.1 and internet over ipv4.<br>
I can ping ipv6 gateway 1111:4444:0:1::1 but I can't ping the
internet<br>
<br>
checking the ipv6 routing table on my instance I either get no
default gateway at all or I get a default gateway to a
fe80::/10 link-local address.<br>
IIRC this worked before I changed the router to a L3 HA
router.<br>
<br>
Appreciate any feedback!<br>
<br>
Best regards<br>
Tobias<br>
</blockquote>
<br>
</blockquote>
<br>
</blockquote>
<br>
</body>
</html>