bhouse-nexthop commented on issue #11584: URL: https://github.com/apache/cloudstack/issues/11584#issuecomment-3602679399
> > Being able to advertise an IPv4 /32 could provide some interesting functionality in the future. Think about anycast use-cases where you may want to say this IP address is not only portable across zones but can actually be advertised simultaneously out of multiple zones which may be different physical datacenters (of course this assumes the datacenters are physically interconnected using private circuits, e.g. wavelengths and whatnot, so they can route non-local traffic to the proper dc). > > [@bhouse-nexthop](https://github.com/bhouse-nexthop) I read the description again, IMHO, advertising public IPv4 addresses is a very special use case, and probably impossible to implement in VR. The routes of public IPv4 addresses should be configured in the upstream router, not cloudstack VR, remember that VR is not the gateway of public IPv4 addresses. You'd still need an ip range for the peering purposes that is adjacent to the upstream routers. But it wouldn't technically be a gateway in the sense that you are saying. Just instead of static routes pointing to the ip it tells the upstream bgp saying here i am. -- 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]
