Domains, ports, power and physical infrastructure required to install and operate the simulator inside a corporate network.
Addressed to the Organization's IT and networking teams. To configure the corporate firewall or proxy, sections 01 and 02 are enough; WiFi configuration and casting to a PC are in sections 03 and 04, and room preparation (power and environment) in sections 06 and 07. It complements the Technical, Operational and Continuity Policies and the Security document.
For client devices to authenticate, synchronise licences and send usage reports to the Yoy Account platform, the following domain and port must be allowed in the corporate firewall and/or proxy rules.
| Port | Protocol | Direction | Purpose | Priority |
|---|---|---|---|---|
443 | TCP | Device → Internet | The only port used by the client device to communicate with Yoy Account: OAuth2 authentication (client credentials), licence synchronisation and usage reports. All over HTTPS/REST. | Mandatory |
accounts.yoy.cl: the device validates the server's standard certificate, and unauthorised interception breaks the connection.
The headsets must also communicate with Meta's infrastructure for account authentication, content download from Meta's servers and system updates. These domains must be included in the whitelist with priority over any category-based blocking rule (e.g. "social networks").
*.facebook.com and *.fbcdn.net are often blocked automatically by corporate web filtering policies. Blocking them completely prevents applications from being downloaded and updated on the headsets.
| Port | Protocol | Direction | Purpose | Priority |
|---|---|---|---|---|
443 | TCP | Headset → Internet | Operation of the headset's operating system, content download from Meta's servers and updates (including VR drivers). | Mandatory |
123 | UDP | Headset → Internet | Time synchronisation (NTP). Without the correct time, SSL/TLS certificates fail and the headset cannot authenticate with any server, Yoy Account included. | Mandatory |
Meta Quest headsets have specific wireless network requirements to guarantee stable operation during sessions and to enable casting to a PC.
Applies to standalone products. Casting is done through Meta Quest Developer Hub (MQDH), Meta's official tool for viewing in real time what is happening inside the headset on the instructor's or operator's screen.
| Requirement | Detail |
|---|---|
| WiFi network | Headset and PC on the same subnet (same VLAN). 5 GHz band mandatory. |
| Network port | 5555 TCP allowed between headset and PC on the internal network (wireless ADB). |
| Quality | Lower stream resolution compared with USB-C to USB-C. |
In addition to Yoy Account and Meta's domains (section 02, which already cover VR driver updates), outbound access is needed to the following platforms for remote support and updates.
Domains: *.teamviewer.com, *.teamviewer.net
Outbound ports: TCP 5938 (primary), TCP 443 (alternative), TCP 80 (fallback).
Pulling from authorised private repositories. Outbound access to: github.com, api.github.com, raw.githubusercontent.com.
Domains: drive.google.com, accounts.google.com, googleapis.com.
Components to be connected to the mains and their estimated consumption:
| Component | Estimated consumption |
|---|---|
| LED TV | 120 W (per television used) |
| High-end PC | 450 W – 700 W |
| Meta Quest 3S headset with charger | 25 W |
These requirements help the system reduce headset tracking problems and avoid damage to its internal displays.
Technical and access controls implemented on the Yoy Account platform, which concentrates the management of licences, users and usage reports. See the Security — Methodologies, Technologies and Communication document for the full detail.
Service hours: Monday to Friday, 09:00 to 18:00 (Chile time).
+56 9 7880 6021
soporte@yoy.cl