Virtual Routing & Forwarding (VRF) for Overlapping IP Space
Raj Venkat PM Networking Venkat
Support Virtual Routing & Forwarding (VRF) to support private, overlapping Layer 3 connectivity leveraging a customer's own public or private IPv4 blocks.
Merged in a post:
Use Your IPs as Equinix Metal Elastic IPs
Instead of running and configuring BIRD to announce your block on Equinix Metal... users supply their ASN and IP blocks so they can be managed as an Elastic IP Address Pool. Users control where they want to attach their IPs through the portal and API, just like Equinix Metal Elastic IPs!
With the VRF feature nearing completing, the API specification and Equinix Terraform provider are available:
marked this post as
I also need
What would be lovely as part of this would be a basic stateful firewall to put in front of ones dedicated server. One could then have the option of a private IP space using NAT or not.
this specific use case is something for our bgp/default route feature; f5 should support that. with that said, let's get this on the map for q2, we've got some good designs for this...
Hi Raj Venkat, do you know when this would be available for use? Currently, a deployment that requires internet connectivity in an active/passive highly available setup using a virtual IP, eg a pair of HA Fortinet or F5 appliances, requires a user to create their own top level networking infrastructure that can provide this functionality. It would be extremely useful to have a default internet gateway available on an L2 VLAN so this HA functionality can be supported without the additional network setup.