Skip to content

Knowledge catalog

Generated reference

Read-only pages rendered from the Quake AI knowledge graph.

Competitor MappingReference node

N/A (No managed NAT service — self-managed Linux NAT server required)

Competitor mapping for Hetzner Cloud.

This page is a structured knowledge reference. For step-by-step migration guidance, see the migration guide.

Details

Provider
Hetzner Cloud
Service term
N/A (No managed NAT service — self-managed Linux NAT server required)
Provider documentation
External reference

Behavioral divergences

N/A (No managed NAT service — self-managed Linux NAT server required)

Quake AI concept: NAT

  • Hetzner has no managed NAT gateway service. Outbound internet access for private servers requires provisioning a server with a public IP, enabling Linux IP forwarding (net.ipv4.ip_forward=1), and configuring iptables MASQUERADE. Neutron provides managed SNAT via the L3 agent when a router has an external gateway attached.
  • The NAT server must be provisioned as a regular billable server (minimum ~€3.29/month); Neutron SNAT is a control-plane service with no additional instance cost.
  • Hetzner SDN routes traffic to the NAT server via a static network route (destination: 0.0.0.0/0, gateway: <nat-server-private-ip>); this must be manually configured and updated if the NAT server IP changes. Neutron manages routing automatically when a router has an external gateway.
  • No native HA NAT option; high availability requires a custom keepalived/VRRP setup. Neutron L3 HA routers support active-standby failover.

Related

Diverges from (incoming)

Citations

  1. Hetzner Cloud
  2. Hetzner Cloud

These citations record configured source URLs in the knowledge graph. They are not a live platform walk verification date.