Opening a New Office: How to Connect an Existing Office to Reuse Headquarters and Business Entry Points?

Link the new and existing offices over existing broadband and forward designated business traffic to the existing site entry point

As long as the new office has standard broadband and basic power ready, we can ship a physical gateway preconfigured with access parameters and forwarding policies to the site; if the existing office or new site server room already has a virtualisation platform, we can deploy a virtual gateway directly or peer with the existing office firewall gateway over IPSec. Once appliances at both ends are in place and online, they establish a stable inter-site internal network connection over our cross-region transmission channel, provisioning faster than installing a new traditional carrier physical dedicated line.

For traffic routing, we configure precise forwarding paths and access controls by target system subnet or domain name: only when staff at the new office access the overseas headquarters internal network, a remote data centre, or designated external client systems does the gateway send that traffic across the inter-site channel to the existing office, which then forwards it upstream through its established headquarters tunnel, data centre dedicated line, or fixed public IP egress. High-volume daily public internet traffic at the new office breaks out directly over local broadband, neither consuming inter-site channel capacity nor adding load to the existing office's outbound bandwidth. During daily operations, our network also provides DNS query records and 5-tuple connection logs to help administrators distinguish traffic destinations by the private subnets of the new and existing offices.

Routing, allowlist, and link coordination requirements when integrating with an existing site entry point

Delivering traffic from the new office to the existing office is only half the path; for upstream headquarters systems or external client platforms to respond properly, gateways at both ends must also align routing, source addresses, and upstream permissions—you cannot simply assume all legacy resources will work automatically once the two internal networks are linked:

• Distinguish forwarding configurations for private internal network sources vs. public IP allowlist egress: If you are reusing an internal network tunnel from the existing office to headquarters or a data centre, the existing site gateway and headquarters administrator need to allow the new office's private subnet and configure return routes back to the new office. If you are reusing a fixed public IP at the existing office that has been added to an external client system's allowlist, the egress gateway at the existing site must perform source network address translation (SNAT) or proxy forwarding on traffic arriving from the new office so the external client system continues to see the approved public IP address of the existing office as the source.
• Confirm shared-use permission with headquarters, external clients, and existing carrier contracts: Before enabling forwarding, we recommend that enterprise administrators confirm with headquarters or external clients that staff at the new office are permitted to access upstream systems through the existing site entry point, and check any terms in the existing office's carrier dedicated line contract regarding cross-site traffic aggregation. We provide inter-site interconnection and gateway routing coordination, and do not act as an agent for carrier dedicated line relocation or legacy contract modifications.

At the same time, reusing an existing site entry point creates a daisy-chained path: if power, access broadband, or the egress firewall carrying that path at the existing office goes down for maintenance, access from the new office through that entry point will pause as well. Although our cross-region transmission channel supports on-demand bandwidth scaling without waiting for physical construction, actual usable bandwidth when two locations share an entry point remains bounded by the new site's local broadband, the existing site's access link and remaining dedicated line headroom, and gateway processing capacity at both ends. Where multiple broadband links are available on site, we can also help plan multi-link load balancing or automatic failover.

How to connect the new office directly to the same enterprise network when routing through the existing office is impractical

If the new office has a small headcount or is a short-term project site, and the existing office has ample channel headroom with upstream approval for unified forwarding, reusing the existing site entry point is a convenient choice. However, if the new office houses a long-term core R&D or business team with frequent large file syncs and real-time collaboration that could saturate the existing office's outbound bandwidth—or if external clients or legacy carrier contracts explicitly prohibit cross-site hair-pinning, or the new team cannot afford downtime during power maintenance at the old building—there is no need to force traffic through the existing office.

In those cases, we can use the new office's existing local broadband and a preconfigured access appliance to connect the new site directly to our cross-region and cross-border transmission network, establishing direct peer connections from the new office to overseas headquarters, public cloud private networks, or data centres while still keeping internal network connectivity between the new and existing offices. If an external client system requires the new office to register an independent source public IP on its allowlist, we can also provision a dedicated fixed public IP egress for the new site (with egress region, dedicated vs. shared use, and failover behaviour confirmed prior to activation) so the new office can connect directly once the new address is allowlisted.