Ports, TCP/UDP and firewalls
Allow only flows required by viewers, simulators and services.
Understanding TCP, UDP and ports
TCP provides ordered reliable connections, commonly used for HTTP and capabilities. UDP sends datagrams without built-in delivery guarantees, suitable for simulator real-time traffic. OpenSimulator regions may require the same numeric port under both protocols; exact rules depend on version and live INI configuration.
Common ports and service roles
In a typical grid, TCP 8002 commonly serves public ROBUST login services; TCP 8003 is usually private/internal and must not be publicly exposed. Regions often use 9000 and other configured TCP/UDP ports. Some deployments use separate HTTP listeners: inspect InternalPort, network settings and actual listeners. This example is not a universal required-port list.
Three layers of filtering
A connection may be filtered by provider firewall, router and OS firewall (Windows Defender Firewall, ufw, nftables and so on). Proxmox can add host-level and VM-level rules. Check the complete path without disabling every firewall just to test.
Example rules on Linux
Educational example for a verified port layout and existing firewall policy: explicitly allow TCP to public ROBUST and TCP/UDP to a region. Do not paste onto a remote server without preserving SSH management access and verifying source networks. TCP 8003 should only be allowed on trusted internal networks when required, never to the entire internet.
Illustrative example: adapt to the actual installation.
# EXEMPLE seulement : valider la politique SSH et les vrais ports. sudo ufw status verbose sudo ufw allow 8002/tcp sudo ufw allow 9000/tcp sudo ufw allow 9000/udp # Pour ROBUST interne, restreindre à une IP ou sous-réseau autorisé.
Windows firewall example
On Windows, use Microsoft Defender Firewall with Advanced Security to create targeted inbound rules for port, protocol and ideally allowed source addresses. A TCP rule does not allow UDP. Use the correct network profile and test after each change.
Ports used by additional modules
A self-hosted voice backend, web API or currency service may use additional ports. Open only what the enabled service needs, understand whether access should be public or private, and document the flows. Currency services and MySQL should not be exposed without appropriate controls.