GRE tunnel DDoS protectionProtect a server anywhere, over GRE.

Your origin can stay with any host that gives you a stable public IP. Templass scrubs the attack in Frankfurt and hands clean traffic back to you through a GRE tunnel.

What GRE protection means

GRE is a simple point-to-point tunnel. Templass wraps the clean traffic for your protected address and sends it to a public IP you control. Your router, firewall or Linux box unwraps it and passes the packets to the real service.

The protected address is announced on AS208743, so attack traffic lands at the Templass edge in Equinix FR5 instead of on your uplink. Only what survives scrubbing goes into the tunnel.

When GRE is the right choice

  • Your origin is already on the internet, with a host or provider you want to keep.
  • You can terminate GRE and add a route for the protected address.
  • You want to start without a data center order or a physical circuit.

If you colocate in Equinix FR5, a Cross-Connect gives you a dedicated physical link with no GRE encapsulation. The trade is order time. If you are unsure, start with GRE.

How setup goes

  1. Request a quote and choose GRE tunnel as the connection type.
  2. Send your outer address. It must be reachable from the internet, allow GRE, and stay stable. A WAN IP that changes with DHCP will drop the tunnel.
  3. Receive the provisioned values: the Templass endpoint, inner addresses, the protected prefix, and a key if one is used.
  4. Bring the tunnel up on Linux with ip tunnel, or as a GRE interface on a hardware router or firewall.
  5. Route the protected address through the tunnel, test it from outside, then move DNS.

The step-by-step runbook, with placeholders and a Linux example, is in the GRE tunnel setup guide.

Mistakes that break GRE protection

  • Asymmetric routing. Traffic comes in through the tunnel but replies go out your normal uplink. Stateful firewalls and some protocols break. Send replies back through the tunnel.
  • Serving on the tunnel endpoint. The outer GRE address is only for the tunnel. Do not run the game or website on it.
  • A second public path. If the origin still answers on another interface or an old DNS record, attackers will use that instead.
  • Guessed endpoints. Use only what Templass provisions.

Cost and what it is based on

Billing follows clean Mbps delivered to your origin at the 95th percentile. Attack traffic and GRE overhead are not separate line items. Read DDoS protection pricing for the tiers, or see how GRE fits game server DDoS protection.

Questions

What do I need on my side for GRE?

A stable public IPv4 address that can terminate GRE, permission to add a tunnel and a route on the device, and a firewall that allows IP protocol 47 between your address and the Templass endpoint.

Where do I get the Templass GRE endpoint and keys?

Templass provisions them after your quote is accepted. The docs only use placeholders. Do not guess an endpoint or copy one from somewhere else.

Does GRE add latency?

Clean traffic travels from Frankfurt to your origin over the internet, so the path to Frankfurt plus the path from there to your server is what players or users feel. An origin close to Frankfurt keeps that extra stretch short.

Does GRE overhead count toward my bill?

No. You are billed on clean Mbps delivered to the origin at the 95th percentile. Your ISP uplink and GRE outer overhead are not a separate Templass charge.

Can I move from GRE to a Cross-Connect later?

Yes. If you get presence in Equinix FR5, a Cross-Connect can replace the tunnel. That is a new quote for the different handoff.

Related

Pick GRE in the quote form, add your peak clean Mbps, and we come back with a number.

Request a quote