On Mon, Aug 20, 2018 at 6:06 AM, Tobias Urdin wrote:
> When I removed those ips and set accept_ra to 0 on the backup router:
>
> ip netns exec qrouter-0775785e-a93a-4501-917b-be92ff03f36a sysctl -w
> net.ipv6.conf.qr-7fad6b1b-c9.accept_ra=0
> ip netns exec
When I removed those ips and set accept_ra to 0 on the backup router:
ip netns exec qrouter-0775785e-a93a-4501-917b-be92ff03f36a sysctl -w
net.ipv6.conf.qr-7fad6b1b-c9.accept_ra=0
ip netns exec qrouter-0775785e-a93a-4501-917b-be92ff03f36a sysctl -w
net.ipv6.conf.qr-5be04815-68.accept_ra=0
ip
Continuing forward, these patches should've fixed that
https://review.openstack.org/#/q/topic:bug/1667756+(status:open+OR+status:merged)
I'm on Queens.
The two inside interfaces on the backup router:
[root@controller2 ~]# ip netns exec
qrouter-0775785e-a93a-4501-917b-be92ff03f36a cat
Ok, so the issue here seems to be that I have a L3 HA router with SLAAC,
both the active and standby router will
configure the SLAAC obtained address causing a conflict since both side
share the same MAC address.
Is there any workaround for this? Should SLAAC even be enabled for
interfaces on
Forgot [neutron] tag.
On 08/20/2018 11:36 AM, Tobias Urdin wrote:
Hello,
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.
CC openstack-dev for help or feedback if it's a possible bug.
I've
