[RFE] DHCP agent should provide ipv6 RAs for isolated networks with ipv6 subnets
Bug #1498987 reported by
Ihar Hrachyshka
This bug affects 3 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
neutron |
Won't Fix
|
Wishlist
|
Dustin Lundquist |
Bug Description
Currently, if there is no router attached to a subnet, then instances cannot walk thru IPv6 address assignment because there is nothing on the network that multicasts RAs that would provide basic info about how ipv6 addressing is handled there. We can have DHCP agent to run radvd in that case. Then instances would be able to receive IPv6 addresses on isolated networks too.
We could try to rely on https:/
tags: | added: rfe |
tags: | added: ipv6 |
Changed in neutron: | |
importance: | Undecided → Wishlist |
Changed in neutron: | |
milestone: | mitaka-2 → mitaka-3 |
Changed in neutron: | |
milestone: | mitaka-3 → mitaka-rc1 |
Changed in neutron: | |
milestone: | mitaka-rc1 → newton-1 |
tags: | added: rfe-approved |
summary: |
- DHCP agent should provide ipv6 RAs for isolated networks with ipv6 + [RFE] DHCP agent should provide ipv6 RAs for isolated networks with ipv6 subnets |
Changed in neutron: | |
milestone: | newton-1 → newton-2 |
Changed in neutron: | |
milestone: | newton-2 → newton-3 |
Changed in neutron: | |
milestone: | newton-3 → newton-rc1 |
Changed in neutron: | |
milestone: | newton-rc1 → none |
status: | Triaged → Incomplete |
To post a comment you must log in.
I'm now thinking that Router Lifetime option here [1] might be the way to go. Set it to 0 and the DHCP server shouldn't be used as a default route.
[1] https:/ /tools. ietf.org/ html/rfc4861# section- 4.2