Choosing IPsec proposals: what to use and what to retire
A practical guide to IPsec encryption, integrity, PRF and Diffie-Hellman groups for new tunnels, with recommended proposals and what to retire.
Connect your office firewall to your own TunnelYard gateway over IPsec. Your office's internet traffic leaves from the gateway's dedicated static IP, so SaaS apps, banks and partners can allow-list one address that doesn't change.
Dedicated, not shared Works with your firewall No software on devices
Connects to standard IPsec firewalls and routers
No appliance to buy and nothing to install on your devices. Launch, connect, allow-list.
Pick a city and launch. In 10–15 minutes your gateway is ready, with its own static public IPv4, dedicated to you.
Add a tunnel for your office, export a ready-made config for your device and bring the IKEv2 tunnel up.
Give the gateway's IP to your SaaS apps, bank or partners, and watch the tunnel in the dashboard.
Give SaaS admin consoles and sign-in rules one office IP to trust.
Learn moreA fixed IP for banking portals, payment providers and partner APIs.
Learn moreSeveral offices, shops or OT sites leaving from one known IP.
Learn moreA dedicated gateway, managed for you, that works with the firewall you already run.
Your gateway's IP is yours alone, not a shared VPN exit. No other customer's traffic leaves from it.
38 locations in 20 countries today, so your traffic leaves from where you need it.
Export a config for Cisco, Fortinet, Palo Alto, Juniper, MikroTik, pfSense, OPNsense, Ubiquiti or OpenWrt.
Connect up to 4 offices on Business and unlimited on Enterprise, all leaving from the same IP.
Decide what your offices can reach through the gateway, with P2P blocking on every plan.
Alerts by email, webhook, Slack or Teams when a tunnel drops, with traffic and uptime history.
An ISP's static IP belongs to one line in one building. A TunnelYard gateway's IP is yours, whichever provider your offices use and wherever they are.
A practical guide to IPsec encryption, integrity, PRF and Diffie-Hellman groups for new tunnels, with recommended proposals and what to retire.
How each model decides what goes into the tunnel, what changes for traffic selectors and routing, how to mix the two, and when to pick which.
IKE, ESP, security associations, tunnel mode and the ports to open: how the IPsec protocol builds an encrypted VPN tunnel between two networks.
TunnelYard gives your office a dedicated static IP over IPsec. You launch your own gateway, a dedicated server with its own static public IPv4, and connect your office firewall to it with an IKEv2 tunnel. Your office's internet traffic then leaves from the gateway's IP, so SaaS apps, banks and partners can allow-list one address that doesn't change.
TunnelYard works at the firewall, not on each device: every device on the office network uses the IP, with no app or login to install. And the gateway is yours alone, a dedicated server rather than a shared VPN exit that other customers use too.
Update the office's new public IP in the tunnel and bring it up again. The gateway's static IP, and every allow-list that uses it, stay the same. Several offices can also share one gateway and its IP: up to 4 on Business and unlimited on Enterprise; see one IP for every branch.
No. TunnelYard carries your offices' outbound internet traffic, so it leaves from the gateway's static IP. Offices connected to the same gateway share its IP, but they don't reach each other's networks through it.
No. Only the replies to your offices' own outbound connections come back through the gateway. Inbound connections and port forwarding to your office are not offered.
You choose from 38 locations in 20 countries today, across North America, South America, Europe, the Middle East, Asia, Oceania and Africa; the list can change as locations are added. Gateways, tunnels and the static IP are IPv4 today, and IPv6 support is coming in a future version.
Launch a gateway, connect your firewall, and allow-list one IP today.