Home Networking

Networking

By D
• 9 articles

Connect your office with a VPN tunnel

A VPN tunnel links your office network to your private network on Gewape Cloud over an encrypted connection. Computers in the office reach your cloud servers on their private addresses, and the servers do not need public IPs. You give us two things: your office's public IP address and your office network range. We build a dedicated gateway in your project and generate the encryption settings. You then enter the same settings on your office router or firewall. Before you start - Your office router or firewall must support IPsec with IKEv2 and a pre-shared key. Most business firewalls do. - It needs a fixed public IPv4 address. - Your office network range, for example 192.168.10.0/24, must be /16 or smaller and must not overlap your private network on Gewape Cloud. If both use the same range, change one of them first. - You need a private network with an internet router in the region. One is created the first time you launch a server there. Order the tunnel 1. In the console menu open VPN and click Order VPN Tunnel. 2. Gewape Cloud side: choose the region your servers are in (Kigali, Huye or Nairobi). 3. Your side (peer): - Your public gateway IP: the public IPv4 address of your office router. - Your LAN subnet (CIDR): your office network range, for example 192.168.10.0/24. - Tunnel name (optional): for example head-office. 4. Click Order VPN tunnel. It usually takes a minute or two. 5. The result page shows Gewape Cloud gateway (peer IP), Gewape Cloud subnet and Pre-shared key (PSK). Click Copy credentials and store them somewhere safe. This page shows the key only once. Set up your office router Create a site-to-site IPsec tunnel with these settings: | Setting | Value | |---|---| | Remote gateway | the Gewape Cloud gateway (peer IP) | | Remote network | the Gewape Cloud subnet | | Local network | your LAN subnet | | Authentication | pre-shared key: the Pre-shared key (PSK) | | IKE version | IKEv2 | | Phase 1 (IKE) | AES-256, SHA-256, DH group 14, lifetime 8 hours | | Phase 2 (ESP) | AES-256, SHA-256, PFS off, lifetime 1 hour | | NAT traversal | on (UDP 4500) | Allow UDP ports 500 and 4500 between your router and the Gewape Cloud gateway's public IP. The Gewape Cloud gateway starts the connection itself and keeps retrying, so the tunnel comes up as soon as your side is ready. What we set up for you - A gateway server in your project, named vpn-gw-…, with its own public IP. Leave it alone in Cloud Servers; to remove it, delete the tunnel from VPN. - A route on your private network's router that sends traffic for your office range through the gateway. Your servers need no changes. - A security group on the gateway that accepts tunnel traffic only from your office's public IP. Your servers' own security groups still apply. To reach a service from the office, allow its port from your office range, for example 192.168.10.0/24. See Open a port. See or remove tunnels The VPN page lists your tunnels with their region, your gateway IP, your subnet and the Gewape Cloud gateway. To remove one, choose Delete on its row. That removes the gateway server, its public IP, the route and its security group. What it costs A tunnel is billed by the hour while it exists. The first hour is charged from your wallet when you order, and the result page shows the hourly rate. Your usage is in Wallet & Usage. If the tunnel does not come up - Check that every setting matches the table above, especially the pre-shared key, IKEv2 and DH group 14. - Check that your office firewall allows UDP 500 and 4500 to and from the Gewape Cloud gateway's public IP. - If your office public IP changes, the tunnel stops working. Delete it and order a new one with the new address. - Still stuck? Contact support with the tunnel name and region. The far end is equipment we cannot see, so an early message saves time.

Last updated on Nov 02, 2026