NATTED mode should support dynamic routing (BGP) to advertise public ipv4/32 addresses and ipv6 subnets #11584
Description
The required feature described as a wish
Currently in NATTED mode with ipv4 and ipv6 everything is statically routed, your VR is assigned a public ipv4 address from a pool, a private ipv4 subnet, and an ipv6 subnet (of course with ipv6 there's no separation of private and public). You can then request additional public ipv4/32 addresses be added for static nat or port forwarding purposes.
One of the main problems with NATTED mode are the ipv6 subnets won't have routes, so you have to listen for events and trigger them to be added somehow, since it is all relying on static routing.
With ROUTED mode, you lose basically all desirable ipv4 functionality. All ips are public, you get a whole public ipv4 subnet which is wasteful especially these days where ipv4 public addresses are scarce, and you lose the ability to do load balancing (obviously in routed mode there is no need for port forwarding or static nat since they are all public ips).
What I'm looking for is essentially a NATTED mode with dynamic routing (BGP) support. The difference is the public ipv4/32 address(es) and ipv6 /64 subnets assigned to the VR should be advertised via BGP rather than be statically routed. Each new claimed public ipv4 /32 address from the pool would be added to the virtual router and then advertised out BGP. It would function identically to the current NATTED mode, just would also use BGP for the public side.