When an employee works from home or a cafe, protecting their traffic only takes a regular client VPN like LiMP VPN — install the app, turn it on, turn it off. But when you need to connect a head office and a branch so that an internal server, a shared database, or a network printer is reachable from both locations without installing a VPN client on every computer, that is a different job, and a site-to-site VPN is what solves it.
Before configuring the tunnel, check whether the two office subnets overlap: if both use the same range, for example 192.168.1.0/24, routing between the networks will not work. The LiMP VPN subnet calculator quickly works out the mask, address range, and host count for a subnet — a free online tool, nothing to install.
Below: how a site-to-site VPN differs from a regular device VPN, which protocols fit the job, how to plan office addressing without conflicts, a step-by-step WireGuard setup with a sample configuration, and an honest answer to whether LiMP VPN can be used for this task.
What a Site-to-Site VPN Is and How It Differs from Remote Access VPN
A site-to-site VPN is a tunnel between two network gateways (routers or servers) that runs permanently in the background and connects entire networks: devices in office A reach devices in office B by their internal IP addresses, as if they were on the same local network. A remote access VPN (regular client VPN) is a tunnel between ONE device and a VPN server, which a person turns on and off manually whenever they need to protect their connection or reach a specific resource.
| Aspect | Site-to-Site VPN | Remote Access VPN (Client) |
|---|---|---|
| What it connects | Network to network (office to office, office to data center) | One device to a server |
| Who sets it up | A network administrator, on both gateways | The user, by installing an app |
| Operating mode | Always on, in the background, no employee action needed | Turned on and off manually as needed |
| Typical scenario | Connecting offices, branch to headquarters, office to cloud | Protecting traffic on public Wi-Fi, in a cafe or hotel |
| What each office needs | A router or server with VPN support on each side | Just an app on a phone or laptop |
| Pros | Transparent access to the whole network, no client needed on every machine | Quick to install and turn on, no admin required |
| Cons | Harder to set up, needs a static or public address on at least one side | Does not connect whole networks, protects one device at a time |
When You Actually Need a Site-to-Site VPN
A site-to-site VPN makes sense when the goal is connecting networks, not protecting one person's traffic.
- A head office and a branch constantly exchange files or work in a shared database, and access needs to work without a VPN client on every workstation.
- You need access to an internal server (file storage, a video surveillance system, a phone system) from another location, as if that server were physically in the same building.
- The company rents a server or virtual machine in a data center or cloud provider and wants it to behave like part of the office network rather than a separate external resource.
- Two companies are merging, or one is opening a new branch, and two previously independent networks need to be joined into one.
- An office has equipment (a printer, a terminal, an IP phone system) that staff in another location need to reach without exposing ports directly to the public internet.
Which Protocols to Use for Site-to-Site VPN
Most site-to-site VPNs are built on one of three protocols — WireGuard, IPsec/IKEv2, or OpenVPN — and the choice depends on what equipment is already in the offices and how much performance matters.
| Protocol | Hardware Support | Setup Complexity | Performance |
|---|---|---|---|
| WireGuard | Modern router firmware (OpenWrt, MikroTik RouterOS 7+, pfSense/OPNsense) | Low — a compact, few-line config on each side | High, minimal encryption overhead |
| IPsec/IKEv2 | Supported by nearly all office routers and firewalls across vendors | Medium-to-high — more parameters: IKE phases, cipher choice, PFS, key lifetime | High, many devices have hardware acceleration |
| OpenVPN | Supported almost everywhere in software, even on older hardware | Medium — its own configuration and certificate format | Lower than WireGuard or IPsec, since it runs in userspace |
If you are building infrastructure from scratch and speed and simplicity matter most, WireGuard is usually the pick. If you need to connect mixed-vendor hardware in an already-established corporate network, IPsec/IKEv2 is often chosen as the more universal industry standard. Picking a specific router brand or firmware is a separate decision for your IT team — here we are only describing classes of protocols and devices, not recommending a purchase.
How to Plan Office Addressing So Subnets Do Not Overlap
The single most common reason an already-configured site-to-site tunnel "does not route" traffic is overlapping office subnets, not a flaw in the VPN protocol itself.
If office A uses 10.10.0.0/24 and office B uses 10.20.0.0/24, there is no conflict: devices in one network route unambiguously into the other through the tunnel, and every IP address is unique across the combined network. The problem appears when both offices are configured, by default, with the same range — for example 192.168.1.0/24, which is the most common factory setting on consumer and some office routers. In that case the gateway cannot tell which office a packet addressed to 192.168.1.50 belongs to, and traffic either fails to arrive or goes to the wrong place.
There are two ways to resolve overlapping subnets: renumber one of the networks onto a unique range (for example, move the branch to 192.168.20.0/24) — the most reliable fix, though it requires reconfiguring DHCP and some devices; or configure NAT on the VPN gateway, which remaps one network's addresses to a separate technical range only for the tunnel, without touching device settings inside the office — harder to debug, but it does not require changing local addressing. Before choosing an approach, work out the actual ranges and free addresses of both networks with the LiMP VPN subnet calculator — faster than estimating masks by hand.
How to Set Up a Site-to-Site VPN with WireGuard — Step by Step
Below is a minimal setup for a tunnel between two gateways using WireGuard; the commands are the same whether you are on a Linux server or most router firmware with WireGuard support.
- Install WireGuard on both gatewaysOn Linux distributions (Debian/Ubuntu), via the system package manager; on a router, through built-in firmware support (OpenWrt, MikroTik RouterOS 7+, pfSense/OPNsense).
- Generate a key pair on each sideThe
wg genkeyandwg pubkeycommands create a private and public key for office A's gateway, and separately for office B's. - Confirm the office subnets do not overlap(see the section above) — there is no point configuring further until this is settled.
- Configure the interface on office A's gatewayExample configuration:
[Interface]
PrivateKey = <office A private key>
Address = 10.0.0.1/30
ListenPort = 51820
[Peer]
PublicKey = <office B public key>
Endpoint = <office B public IP>:51820
AllowedIPs = 10.20.0.0/24
PersistentKeepalive = 25 - Configure a mirrored interface on office B's gateway— with its own private key, office A's public key, and
AllowedIPs = 10.10.0.0/24(office A's network). - Add a static routeon each gateway so traffic to the other office's network goes through the WireGuard interface rather than the default route to the internet.
- Bring the interface up and check the handshakewith
wg show— thelatest handshakefield should keep updating, confirming both gateways see each other. - Check the MTU if the connection is unstableDropped large file transfers or video calls over the tunnel are often caused by packet fragmentation — see our guide on VPN protocols for background on how tunneling overhead affects throughput.
PersistentKeepalive = 25 matters especially if at least one side is behind a carrier NAT without a static public IP: without periodic keep-alive packets, the tunnel will go idle and only re-establish when new outbound traffic appears.
How to Verify the Tunnel Between Offices Is Actually Working
After setup, check connectivity at three levels: the tunnel itself, routing, and reachability of specific services.
- Tunnel check. On WireGuard — the
wg showcommand, looking for a freshlatest handshake. On IPsec — check the security association (SA) state through your gateway's tools. - Routing check.
pingfrom a device in office A to an internal IP in office B — if there is no reply despite a live tunnel, the usual cause is a missing static route or a firewall rule blocking traffic between the subnets. - Hop-by-hop check.
traceroute(ortracerton Windows) shows where traffic stops if a directpingfails. - External port reachability. The tunnel will not come up if an ISP or firewall blocks the needed port: UDP 51820 for WireGuard (or whichever port you configured), UDP 500 and UDP 4500 for IPsec/IKEv2. You can check whether a port is reachable without touching the gateway itself using the LiMP VPN port checker, which shows whether a given port is open on an external address.
Can LiMP VPN Be Used to Connect Two Offices?
Honestly: no. LiMP VPN is a consumer client VPN for individual devices on Android, Windows, and Chrome — not hardware, and not a site-to-site tunneling service between offices. It protects one user's traffic, an employee's laptop at a cafe or phone while traveling, but it does not join entire networks together and does not replace the gateway-level configuration described above.
Where LiMP VPN genuinely helps in a business context is protecting individual remote employees on untrusted networks: a cafe, an airport, a hotel on a business trip. Building a permanent channel between two offices requires an actual site-to-site tunnel on network hardware, as described in this article, not a client application.



