Skip to Main Content
feedback.corp.metal
Status Shipped
Workspace Network Features
Created by Ben White
Created on Feb 28, 2022

Virtual Routing & Forwarding (VRF) for Overlapping IP Space on Dedicated and Shared Ports

This idea was imported from Canny. Originally created by: Raj Venkat. The current owner is: Unassigned.

Support Virtual Routing & Forwarding (VRF) to support private, overlapping Layer 3 connectivity leveraging a customer's own public or private IPv4 blocks. Enable support on dedicated ports as well as shared ports.
  • Admin
    Ben White
    Reply
    |
    Jan 31, 2024

    This comment was imported from Canny. Originally created by: Chris Turra with 0 likes.

    We are excited to share that we have released the first iteration of Virtual Routing and Forwarding (VRF), which can be configured through the API or UI directly. More information around what VRF is and how to use it can be found on the following deploy documentation page: => https://deploy.equinix.com/developers/docs/metal/layer2-networking/vrf/

  • Admin
    Ben White
    Reply
    |
    Aug 24, 2022

    This comment was imported from Canny. Originally created by: Shyam Krish with 0 likes.

    Target: Q4'22

  • Admin
    Ben White
    Reply
    |
    May 23, 2022

    This comment was imported from Canny. Originally created by: Zachary Smith with 0 likes.

    With the VRF feature nearing completing, the API specification and Equinix Terraform provider are available: https://registry.terraform.io/providers/equinix/equinix/latest/docs/resources/equinix_metal_vrf https://metal.equinix.com/developers/api/vrfs/

  • Admin
    Ben White
    Reply
    |
    Oct 22, 2021

    This comment was imported from Canny. Originally created by: Andy Tan with 0 likes.

    good idea I also need

  • Admin
    Ben White
    Reply
    |
    May 28, 2021

    This comment was imported from Canny. Originally created by: Chris Harris with 4 likes.

    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.

  • Admin
    Ben White
    Reply
    |
    Apr 29, 2021

    This comment was imported from Canny. Originally created by: Raj Venkat with 4 likes.

    targeted for delivery in Q2'21

  • Admin
    Ben White
    Reply
    |
    Mar 4, 2021

    This comment was imported from Canny. Originally created by: Raj Venkat with 0 likes.

    Planned for Q2'21

  • Admin
    Ben White
    Reply
    |
    Jan 29, 2021

    This comment was imported from Canny. Originally created by: Adam Rothschild with 0 likes.

    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...

  • Admin
    Ben White
    Reply
    |
    Jan 29, 2021

    This comment was imported from Canny. Originally created by: Damian Sieczkowski with 4 likes.

    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.

  • Admin
    Ben White
    Reply
    |
    Jan 28, 2021

    This comment was imported from Canny. Originally created by: Raj Venkat with 0 likes.

    Per tenant gateway is planned in Private networking

  • Admin
    Ben White
    Reply
    |
    Jan 28, 2021

    This comment was imported from Canny. Originally created by: Raj Venkat with 0 likes.

    Hi @damian, could you please share the customers interested in this feature via email?

  • +83