PhoenixNAP provides isolated Layer-2 connectivity with VLANs that can be configured on demand through its API or web console. Add a gateway, and you get inter-VLAN routing. Basic gateways are great, but they have clear limitations:
- no Network Access Control Lists
- no DHCP
- no NAT
- limited to /25 (max 128 IP)
- no IPv6
- no Load Balancer
You could use a couple of Linux servers to act as gateways. You can use iptables for network access control and NAT, ISC DHCP/Kea, and other open-source software. Configured and maintained correctly, this can be a solid solution; the downside is added complexity for maintenance, updates, redundancy, and potential risk for misconfiguration.
Netris VPC does all of this for you automatically with an intuitive web console and API/IaC for management. And when you deploy at PhoenixNAP, there is no need to worry about integration, architecture, or implementation: Netris recognizes your servers as native objects, and when you create V-Nets (virtual networks), Netris automatically provisions and configures Layer-2 networks leveraging the PhoenixNAP API.
- Native integration with PhoenixNAP networking
- PhoenixNAP Servers appear as network endpoint objects
- Unlimited IPv4/IPv6, DHCP, NAT, ACLs, Load Balancing
- Intuitive & declarative