hstan77 commented on issue #4463: URL: https://github.com/apache/cloudstack/issues/4463#issuecomment-878969855
Hi All, i suggested before in on gitshub to do like this, may be can consider it: Physical Router have IPv6 with /48 prefix Cloudstack allocates each VR with one /64 prefix , and VR will have function of DHCP6 to assign to the VM . Cloudstack VR have a default route to the /48 IP in Physical Router. Cloudstack only allocates the /64 of /48 that available in Physical router to VR. and VR assign IPv6 via DHCP6 to the VM. The router side need to make sure the /48 is only use for Cloudstack , but not self allocate it to others to avoid overlap. For IPv6, minimum to use in Router is /48 cause that is like minimum prefix to annocue to outside world, This /48 is similar to /24 in IPv4 . While Ipv6 /64 is similar to /32 in IPv4 k which is like a single IP . So in this way, it shall no need any BGP / OSPF session between Cloustack and Physical Router. The traffic will reach /64 at VR and VR route to VM single IPv6 We can try on this. On Tue, Jul 13, 2021 at 5:14 PM Wei Zhou ***@***.***> wrote: > @wido <https://github.com/wido> @GabrielBrascher > <https://github.com/GabrielBrascher> @mkriegs <https://github.com/mkriegs> > @hstan77 <https://github.com/hstan77> @luhaijiao > <https://github.com/luhaijiao> > we are investigating the ipv6 support in cloudstack, (see my colleague > Alex's email in users/dev mailing list: > https://markmail.org/message/dd7uihxwpav6jhkc). It would be nice to get > your input. > > — > You are receiving this because you were mentioned. > Reply to this email directly, view it on GitHub > <https://github.com/apache/cloudstack/issues/4463#issuecomment-878919734>, > or unsubscribe > <https://github.com/notifications/unsubscribe-auth/ARFNGASVGGUS5QC4E4AX7O3TXP7YBANCNFSM4TSMJQXA> > . > -- Regards, Hean Seng -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
