Outbound Connections
This page lists the connections a PrivateLAN appliance makes by itself to systems outside your own network: which ones go to PrivateLAN, when, what is sent and how you control them. Connections to your own switches and devices are not listed here.
Connections to PrivateLAN
| Connection | When | What is sent | Controlled by |
|---|---|---|---|
| Update check | Every hour, at every update and, when you open the update page, at most once every ten minutes | Licence instance, installed version, update branch and licence fingerprint, signed with the appliance key | Always on: without it the appliance cannot learn about security updates |
| Updates | Automatic updates start between 04:00 and 05:00: each appliance waits a random time of up to an hour, so not all appliances contact PrivateLAN at once. Or when an administrator starts an update | A request signed with the appliance key; the appliance downloads the signed release | System > Update |
| Telemetry | When an event occurs in the web interface, during an update, an automatic repair or an automatic block of remote login | The event; see System Settings | Telemetry on the System page |
| Password reset and e-mail verification | Only when a user asks for a reset code or verifies an e-mail address | The e-mail address, the code and the purpose; PrivateLAN sends the mail | Used only on request. Without internet an administrator sets the password under Users |
| Tux assistant | Only when a user asks Tux a question, with the PrivateLAN-hosted backend | The question and the data Tux looks up to answer it; PrivateLAN forwards it to its AI provider, Anthropic | System > AI; with your own AI server there is no connection to PrivateLAN |
| Internet check | When the update, password reset or users page needs to know whether the internet is reachable | A single ping, no data | Not configurable |
| QR Support | Never from the appliance | The report leaves only as QR codes on the screen, read by a phone | Your licence and user roles |
The Telemetry setting controls only telemetry. Since 26.10.4, Disabled also stops the reports the appliance sends on its own about updates, automatic repairs and the blocking of remote login; the updates themselves keep working. Telemetry, mail and the hosted Tux assistant are only used by an appliance whose licence is linked to its update key.
What the update check sends is described in more detail under Software Updates. How PrivateLAN handles this data is described in the privacy statement.
Other outbound connections
- Ubuntu package servers — security updates of the operating system.
- MariaDB package servers — updates of the appliance's database. Since 26.10.4 the database comes straight from its maker, MariaDB, instead of through Ubuntu. The appliance downloads from
dlm.mariadb.com, which hands the download tostorage.googleapis.com;r.mariadb.comis used once, when the appliance first switches over. If your firewall only lets the appliance reach listed destinations, add these. - ClamAV — virus definitions for the appliance's own virus scanner.
- Your time server — the NTP server set under System > Networking.
- Your own AI server — only when Tux uses an on-prem backend you set under System > AI.
- Webhook receivers — only the receivers you configure yourself.
Without an internet connection
The appliance keeps working without internet. The connections above then simply do not happen. Updates are installed by replacing the OS disk, see Offline Updates.
