> ## Documentation Index
> Fetch the complete documentation index at: https://docs.atomscale.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Connection Sharing

> Let workstations without internet access upload through another gateway on the same network

Many instrument workstations have no internet access. Connection Sharing lets one internet-connected computer running Atomscale (the **Hub**) relay Atomscale traffic for gateways on the same local network (the **Outposts**).

```text theme={null}
┌─────────┐
│ Outpost │──┐  LAN     ┌─────┐  HTTPS  ┌───────────┐
└─────────┘  ├────────► │ Hub │ ──────► │ Atomscale │
┌─────────┐  │ TCP 8484 └─────┘   443   └───────────┘
│ Outpost │──┘
└─────────┘
```

Each computer runs in one of three modes:

| Mode | Description |
| - | - |
| **Normal** | Connects to Atomscale directly, using the computer's own network settings. The default. |
| **Hub** | Also carries traffic for nearby Atomscale computers that can't reach the internet. |
| **Outpost** | Reaches Atomscale through a Hub on this network. |

Open Connection Sharing from the globe button in the **Integrations** page header, or from Connection Settings on the sign-in screen. First-run setup also offers both roles: an Outpost in the [Connection](https://docs.atomscale.ai/gateway/first-run.md#1-connection) step, and a Hub in the [Sharing](https://docs.atomscale.ai/gateway/first-run.md#6-sharing) step.

## Set Up a Hub

**1. Pick the Hub computer**

Choose a computer that has internet access, stays on, and is on the same subnet as the instrument
workstations. Atomscale must keep running on it for the Outposts to connect.

**2. Switch to Hub mode**

Select Hub and click Save. The Hub listens on port
**8484** by default; you can choose any port from 1024 to 65535.

**3. Approve the firewall prompt**

The first time you turn on Hub mode, Windows asks an administrator to approve an inbound firewall
rule limited to the local subnet (see
[Windows Firewall Rules](https://docs.atomscale.ai/gateway/reference/network.md#windows-firewall-rules)). Approve it, or ask IT to
allow Atomscale through Windows Firewall.

**4. Note the Hub address**

The Hub lists the addresses other computers connect to, for example `10.1.10.50:8484`, and the
Outposts connected to it.

While Hub mode is on, quitting the app asks for confirmation, because Outposts lose their connection when the Hub stops. Give the Hub a static IP address or a DHCP reservation: Outposts don't search the network, so if the Hub's address changes, each Outpost must be updated by hand.

## Set Up an Outpost

**1. Enter the Hub address**

On the instrument workstation, open Connection Sharing, select Outpost, and enter the Hub's
address and port.

**2. Test and save**

Click Test connection. The test confirms the Hub is reachable
and that a secure connection to Atomscale works through it. Click
Save once it passes.

An Outpost never falls back to a direct connection. When its Hub is down, it keeps collecting and queues data on disk, but can't upload or sign in.

## Changing It from the Web App

On the gateway's page in the web app, **Settings > Connection sharing > Configure** switches the gateway between modes remotely. The gateway checks the new route first and refuses the change if, for example, the Hub is unreachable or the port is in use. After switching, it must reach Atomscale through the new route within 60 seconds, or it restores the previous settings and reports Rolled back.

A remote switch to Hub mode never shows the Windows Firewall prompt, because nobody may be at the computer to approve it. If the rule was never approved, the Hub shows a firewall warning until someone at the computer turns Connection Sharing off and on again and approves the prompt.

## Security

> [!WARNING]
>
> The Hub doesn't authenticate Outposts. Any computer on the same subnet can relay traffic through
> it. Turn on Hub mode only on lab networks you control.

The Hub limits what it relays:

* It accepts connections only from the same IPv4 subnet, or from the Hub computer itself.
* It relays only encrypted HTTPS tunnels to port 443 on a fixed list of Atomscale hostnames (see [Network Requirements](https://docs.atomscale.ai/gateway/reference/network.md)). It can't be used as a general web proxy.
* It refuses destinations that resolve to private or internal addresses.
* Traffic stays encrypted end to end between the Outpost and Atomscale. The Hub can't read it.

## Troubleshooting

| Symptom | What to do |
| - | - |
| The Outpost shows Hub unreachable | It retries after 5, 10, and 30 seconds, then every 60 seconds. Check that the Hub computer is on with Atomscale running in Hub mode, that its IP address hasn't changed, and that its firewall allows the Hub port from the local subnet. |
| The Hub shows a Windows Firewall warning | The firewall rule wasn't created, usually because approval was declined or the change came from the web app. At the Hub computer, turn Connection Sharing off and on again to be asked again, or ask IT to allow Atomscale through Windows Firewall. |
| Atomscale could not start safely on an Outpost | The saved Hub connection couldn't be applied, and the app closed rather than connect directly. Check the Hub is reachable, then start Atomscale again, or change the connection with Connection Settings on the sign-in screen. |


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.