Store both LLA and GUA on router interface port
Based on the two modes (ipv6-ra-mode and ipv6-address-mode) design, RA can be sent from both openstack controlled dnsmasq or existing devices.
RA From dnsmasq: gateway ip that dnsmasq binds into should be link local address (LLA). This means we need to pass the LLA of the created router internal port (i.e. qr-xxxx) to dnsmasq spawned by openstack dhcp agent. In the mean while, we need to assign an GUA to the created router port so that the traffic from external network can be routed back using the GUA of the router port as the next hop into the internal subnet. Therefore, we will need some change to the current logic to leverage both LLA and GUA on router port.
RA from existing device on the same link which is not controlled by openstack: dnsmasq will not send RA in this case. RA is sending from subnet's gateway address which should also be LLA. Allowing subnet's gateway IP to be LLA is enough in this case. Current code works when
force_gateway_
RA from router gateway port (i.e. qg-xxxx): the LLA of the gateway port (qg-xxxx) should be set as the gateway of tenant subnet to get the RA from that. This could be potentially calculated or by other methods in the future considering privacy extension. However, this will make the tenant network gateway port qr-xxxx useless. Therefore, we also need code change to current router interface attach logic.
Blueprint information
- Status:
- Complete
- Approver:
- Sean M. Collins
- Priority:
- Undefined
- Drafter:
- Xu Han Peng
- Direction:
- Needs approval
- Assignee:
- Xu Han Peng
- Definition:
- Obsolete
- Series goal:
- None
- Implementation:
- Unknown
- Milestone target:
- None
- Started by
- Completed by
- Armando Migliaccio
Related branches
Related bugs
Sprints
Whiteboard
Dec-07-2015(armax): If someone is interested in pursuing it, this must be re-submitted according to guidelines defined in [1].
[1] http://
---------------