yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #74343
[Bug 1787919] [NEW] Upgrade router to L3 HA broke IPv6
Public bug reported:
When I disabled a router, changed it to L3 HA and enabled it again all
the logic that was implemented in [1] did not seem to work.
Please see the thread on ML [2] for details.
The backup router had the net.ipv6.conf.qr-<interface>.accept_ra values for the qr interfaces (one for ipv4 and one for ipv6) set to 1.
On the active router the net.ipv6.conf.all.forwarding option was set to
0.
After removing SLAAC addresses on the backup router, setting accept_ra
to 0 and enabling ipv6 forwarding on the active router it started
working again.
Please let me know if you need anything to troubleshoot this here or on
IRC (tobias-urdin).
Best regards
Tobias
[1] https://review.openstack.org/#/q/topic:bug/1667756+(status:open+OR+status:merged
[2] http://lists.openstack.org/pipermail/openstack-dev/2018-August/133499.html
** Affects: neutron
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1787919
Title:
Upgrade router to L3 HA broke IPv6
Status in neutron:
New
Bug description:
When I disabled a router, changed it to L3 HA and enabled it again all
the logic that was implemented in [1] did not seem to work.
Please see the thread on ML [2] for details.
The backup router had the net.ipv6.conf.qr-<interface>.accept_ra values for the qr interfaces (one for ipv4 and one for ipv6) set to 1.
On the active router the net.ipv6.conf.all.forwarding option was set
to 0.
After removing SLAAC addresses on the backup router, setting accept_ra
to 0 and enabling ipv6 forwarding on the active router it started
working again.
Please let me know if you need anything to troubleshoot this here or
on IRC (tobias-urdin).
Best regards
Tobias
[1] https://review.openstack.org/#/q/topic:bug/1667756+(status:open+OR+status:merged
[2] http://lists.openstack.org/pipermail/openstack-dev/2018-August/133499.html
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1787919/+subscriptions
Follow ups