Hypergrid networking: DNS, ports, NAT and traffic
Three different communications · Public addresses and DNS
Three different communications
The viewer contacts login services. Grid services exchange information over HTTP/HTTPS. The viewer then reaches the destination simulator on its advertised ports. A working website does not prove the other traffic paths work.
Public addresses and DNS
Check DNS records, advertised URIs, public IP addresses and HTTPS certificate names when used. A HomeURI reachable only on a private network cannot reliably serve other grids.
ROBUST and regions do not necessarily use the same ports
Public port 8002 is commonly used for ROBUST, but it is a configurable example. Simulators have their own ports, often 9000 or others. Distinguish HTTP/TCP services from UDP traffic needed by the viewer.
NAT, hairpinning and double NAT
Behind a router, forwarding must reach the correct hosts and protocols. Hairpin NAT lets some LAN systems use the public address; its absence does not necessarily mean external visitors fail. Double NAT and CGNAT can prevent ordinary inbound forwarding.
Firewall and test method
Check operating-system, hypervisor, provider and router firewalls. Test endpoints from an external network, then simulator ports and logs. A successful TCP test does not prove UDP works. Never expose SQL or private ROBUST ports merely to fix Hypergrid.
Explore more Hypergrid guides
- Hypergrid installation and configuration
- Principles and architecture
- Visitor identity
- Cross-grid teleports
- Inventory and assets
- Hypergrid friends
- Security
- Troubleshooting