Connecting offices is a business-access project, not simply a tunnel between two routers. The design should state which users and services need to communicate and how each location behaves when the link fails.
Define the requirements
List locations, working hours, circuits, equipment, critical applications, and local dependencies. Identify whether sites need shared files, centralized applications, phones, or only cloud services. Document existing IT providers and who is allowed to change each site's equipment.
Plan addressing and access
- Use an addressing plan that avoids overlapping site networks.
- Define the approved networks and services carried between sites.
- Select a supported connectivity method with appropriate authentication and encryption.
- Restrict administration separately from ordinary user traffic.
- Consider DNS behavior, application dependencies, and available bandwidth.
Do not grant all-to-all access simply because the connection is trusted. A problem at one branch should not automatically expose every other location.
Plan independent operation
Decide which functions can continue locally if the WAN or central site is unavailable. Include alternate connectivity, local power, provider escalation, and any manual process the business needs.
Validate and hand over
Test required applications in both directions and confirm that prohibited paths remain blocked. Test the agreed outage scenario, document recovery behavior, and update diagrams and monitoring. Assign one owner for coordination when a fault could involve more than one site or provider.
Get help with your network
For an existing service issue, open an AvrinTech support ticket. For an assessment or planned improvement, request a scoped proposal and review our networking services. Work, coverage, and response targets depend on your agreement.
