How to Set Up and Manage a Site-to-Site VPN Between Your Brisbane Office and Home Office
Summary
This guide helps you troubleshoot and resolve: How to Set Up and Manage a Site-to-Site VPN Between Your Brisbane Office and Home Office. Follow the steps below to fix the issue.
Common Causes
A Site-to-Site VPN creates a permanent, encrypted tunnel between your main office network and your home office network. This allows staff working from home to access shared drives, printers, and internal servers as if they were physically sitting in the office. This guide walks you through setting up and managing the connection using business-grade routers.
Before You Begin
You will need administrative access to the routers at both locations, the public IP addresses for each site, and a strong pre-shared key (PSK) for authentication. Before starting, ensure you are using business-grade hardware, as ISP-supplied routers often lack site-to-site VPN capability.
Prerequisites
- Change default router admin credentials on both devices.
- Disable WPS and UPnP on both routers for improved security.
- Update router firmware to the latest version on both sites.
- Export and back up existing router configurations before making changes.
- Ensure both routers are connected to a UPS to maintain tunnel uptime during power fluctuations.
- Enable NTP time synchronisation on both routers to ensure accurate IKEv2/IPSec negotiation.
Subnet Planning
192.168.1.0/24, traffic will not route correctly across the tunnel. Use unique ranges such as 192.168.10.0/24 for the main office and 192.168.20.0/24 for the home office.Dynamic DNS and Public IP Addresses
If one or both sites have a dynamic public IP address, configure Dynamic DNS (DDNS) so the tunnel can reconnect automatically when the IP changes.
Configuring DDNS
- Log into your router admin interface.
- Navigate to Dynamic DNS or DDNS under WAN or Internet settings.
- Select a DDNS provider and enter your hostname, username, and password or API key.
- Enable the DDNS service and save the settings.
- Use the DDNS hostname as the remote gateway in your VPN configuration instead of a static IP address.
If your router is behind an ISP gateway or you are on a CGNAT connection, inbound VPN traffic may be blocked. Contact your ISP to request a static public IP or enable port forwarding on the ISP gateway for UDP ports 500 and 4500 to your business router's WAN IP address.
Router Configuration Examples
DrayTek Vigor
- Log in to the router web interface.
- Go to VPN and Remote Access > LAN to LAN.
- Select an index number and click Edit.
- Check Enable this profile.
- Set Dial-Out Settings to the remote site's public IP or DDNS hostname.
- Set Dial-In Settings to Always On.
- Enter the pre-shared key in the Pre-Shared Key field.
- Enter the local and remote subnets under TCP/IP Network Settings.
- Click OK to save.
Ubiquiti UniFi
- Open UniFi Network Application.
- Go to Settings > VPN > Site-to-Site.
- Click Create New VPN.
- Enter the remote gateway IP address or hostname.
- Enter the pre-shared key.
- Define the local and remote subnets.
- Select IKEv2 and click Apply Changes.
MikroTik RouterOS
- Log in via WinBox or WebFig.
- Go to IP > IPsec > Peers and add a new peer with the remote address.
- Go to IP > IPsec > Policies and add a policy matching local and remote subnets.
- Go to IP > IPsec > Proposals and select your encryption and hash algorithms.
- Add firewall filter rules to accept ESP, UDP 500, and UDP 4500.
TP-Link Omada
- Log into the Omada SDN Controller.
- Go to Settings > VPN > Site-to-Site VPN.
- Click Add and select IPSec VPN.
- Enter the remote gateway address and pre-shared key.
- Specify local and remote subnet IDs.
- Click Save and apply to the gateway.
Cisco
- Access the router via CLI or web interface.
- Navigate to VPN > Site-to-Site VPN.
- Configure the IKEv2 policy with your chosen encryption, hash, and Diffie-Hellman group.
- Define the transform set using AES-256 and SHA-256.
- Create the crypto map and apply it to the WAN interface.
Netgear Business
- Log into the router admin page.
- Go to VPN > Site-to-Site VPN.
- Click Add and enter the remote gateway IP.
- Enter the shared key and define local/remote subnets.
- Enable the tunnel and click Apply.
VPN Security Settings
For stronger security, consider certificate-based authentication instead of a pre-shared key. Certificates require a PKI or certificate authority but minimise the risk of key compromise.
When configuring IPSec parameters, use the following guidance:
- Encryption algorithm: Use AES-256 where supported; AES-128 is acceptable for lower-powered hardware.
- Hash algorithm: Use SHA-256. Avoid SHA-1.
- Diffie-Hellman group: Use Group 14 or higher. Avoid Group 1, 2, or 5.
- Perfect Forward Secrecy (PFS): Enable PFS to ensure session keys are not compromised if the long-term key is exposed.
- IKE lifetime and rekeying: Set Phase 1 lifetime to 28,800 seconds and Phase 2 to 3,600 seconds as a starting point.
- Dead Peer Detection (DPD): Enable keep-alive or DPD with an interval of 30 seconds and a threshold of 3 failed attempts to detect and re-establish dropped tunnels automatically.
Split Tunneling vs Full Tunneling
Decide whether home office traffic should route through the VPN for all destinations or only for office resources.
- Split tunneling: Only traffic destined for the office subnet travels across the VPN. Internet traffic uses the local home connection. This reduces load on the office connection but means home office devices do not appear to originate from the office IP address.
- Full tunneling: All traffic from the home office travels across the VPN to the main office. This provides centralised filtering and security but increases bandwidth usage at the office and may slow general web browsing for home users.
MTU and MSS Clamping
VPN encapsulation adds overhead to packets. If the MTU is not adjusted, packets may be fragmented or dropped, causing slow or broken connections.
- Set the VPN tunnel MTU to 1400 bytes or lower.
- Enable MSS clamping on both routers, typically to 1360 bytes, to prevent packet fragmentation over the tunnel.
DNS Resolution Across the VPN
To access internal resources by hostname rather than IP address, configure DNS forwarding or conditional forwarding on both routers so queries for internal domains resolve through the tunnel. Without this, users must connect using IP addresses or UNC paths such as \\192.168.10.10\SharedFolder.
File Sharing and Authentication
If your office uses Active Directory or a domain controller, ensure home office users have valid domain credentials. File sharing authentication may fail if the home office device is not domain-joined or cannot reach the domain controller across the VPN.
Printer sharing across a VPN can be limited because mDNS and Bonjour traffic typically does not route between subnets. You may need to add printers by IP address or configure a print server at the main office that is reachable via the tunnel.
Testing the Connection
- From a computer at the home office, open Command Prompt or Terminal.
- Ping a device on the main office network (e.g.,
ping 192.168.10.10). - Attempt to access a shared folder using the UNC path (e.g.,
\\192.168.10.10\SharedFolder). - Repeat the test from the main office to a device at the home office.
- Test from macOS, Linux, and Windows devices to confirm cross-platform connectivity.
Bandwidth and QoS
If you plan to run VoIP or video conferencing over the VPN, verify that both internet connections have sufficient upload bandwidth. Configure QoS on both routers to prioritise voice and video traffic over general data to minimise latency and jitter.
Managing Your VPN
Monitoring Tunnel Status
Most business routers display the VPN tunnel status in the admin dashboard. Look for indicators such as Connected, Established, or Up. If the status shows Down or Negotiating, the tunnel is not active.
VPN Logs
Check router logs for troubleshooting. Common log locations include:
- DrayTek: Syslog or VPN Log under Maintenance.
- Ubiquiti: System Logs in the UniFi Network Application.
- MikroTik: Log menu under IP > IPsec or system logging.
- TP-Link Omada: Logs under Settings > System Tools.
- Cisco: Logging or Debug output via CLI.
- Netgear: Logs under Maintenance or System Logs.
Updating Subnets
If you add a new VLAN or change your office IP range, update the local and remote subnet settings on both routers. Mismatched subnets are the most common cause of VPN traffic failure.
Rotating Pre-Shared Keys
For security, change your pre-shared key periodically. You must update the key on both routers simultaneously, or the tunnel will drop until both sides match.
Failover and Redundancy
If one internet connection goes down, the VPN tunnel will fail. For critical operations, consider a secondary WAN connection or failover router at either site. Some business routers support dual WAN and can automatically switch to a backup connection, though the VPN tunnel may need to re-establish on the new interface.
Configuration Backup and Documentation
Export and save router configuration files after the VPN is working. Store these backups securely and document the following:
- Public IP addresses or DDNS hostnames for both sites.
- Local and remote subnets.
- Pre-shared key or certificate details.
- IPSec proposals, DH groups, and lifetimes.
- Firewall rules and port forwards.
- Router admin credentials (stored in a secure password manager).
Router Replacement or Factory Reset
If a router is replaced or factory reset, restore the backed-up configuration or reconfigure the VPN from scratch using your documentation. Re-establish the tunnel and verify connectivity before decommissioning the old device.
IPv6 Considerations
If your network uses IPv6, ensure the VPN configuration accounts for IPv6 addressing and that firewall rules permit IPv6 traffic across the tunnel if required. Many site-to-site VPN implementations operate over IPv4 only; confirm your router's capabilities before relying on IPv6.
Guest Network Isolation
Ensure guest Wi-Fi networks are isolated from the VPN tunnel. Guest devices should not be able to reach internal office subnets or resources across the site-to-site connection.
Australian NBN Considerations
If your office or home office is on the NBN, check whether your plan includes a static public IP. Many residential NBN plans use dynamic IP addresses or CGNAT, which can complicate site-to-site VPN setup. Business NBN plans are more likely to provide a static IP suitable for VPN gateways.
Power Protection
Connect both routers to a UPS. A power outage at either site will drop the VPN tunnel, and uninterrupted power helps maintain connectivity for remote staff.
Automated Monitoring
Set up automated health checks or monitoring to alert you if the VPN tunnel goes down. Some routers offer email notifications or SNMP monitoring for tunnel status. Regular checks minimise downtime for home office staff.
Compliance and Data Sovereignty
Australian businesses should consider data sovereignty and privacy obligations when transmitting data across a VPN. Ensure the tunnel encrypts data in transit and that access controls align with your organisation's compliance requirements.
If you are unable to establish the tunnel after following these steps, Open a Ticket and our support team can assist with your configuration.
Still Having Issues?
💻 Open a Ticket