Install and configure Hypergrid
Gatekeeper, HomeURI, suitcase inventory, architecture files, networking and cross-grid tests.
Understanding Hypergrid
Hypergrid lets avatars visit other OpenSimulator worlds while retaining their account on their home grid. It does not merge user databases. Identity, Gatekeeper and inventory-related services must work across grids.
Plan public connectivity
Before enabling Hypergrid, verify stable public DNS, externally reachable grid URL, NAT and DNS resolution from other networks. Distinguish the public ROBUST service, private service connectors and region UDP traffic.
Standalone Hypergrid architecture
On a working Standalone installation, back up OpenSim.ini. Under [Architecture], select StandaloneHypergrid.ini rather than Standalone.ini. Keep StandaloneCommon.ini: its [Hypergrid] should have HomeURI and GatekeeperURI appropriate to the hosted services. Changing one line does not guarantee correct networking.
Adapt this example: do not apply it blindly.
[Architecture] Include-Architecture = "config-include/StandaloneHypergrid.ini" ; Dans config-include/StandaloneCommon.ini : [Hypergrid] HomeURI = "http://world.example.org:9000" GatekeeperURI = "http://world.example.org:9000"
Grid Hypergrid: matching configuration files
For a distributed grid, select GridHypergrid.ini on simulators and use matching ROBUST HG configuration based on Robust.HG.ini.example. These are complementary: HG region modules alone are insufficient without Gatekeeper and UserAgent endpoints on ROBUST.
Adapt this example: do not apply it blindly.
; Sur chaque simulateur, dans OpenSim.ini : [Architecture] Include-Architecture = "config-include/GridHypergrid.ini" ; Sur ROBUST : copier et adapter Robust.HG.ini.example ; puis démarrer ROBUST avec ce fichier INI.
ROBUST HG public services
Robust.HG.ini.example places public services on 8002 and private services on 8003. Public HG connectors include GatekeeperServiceInConnector, UserAgentServerConnector, HeloServiceInConnector, HGFriendsServerConnector, InstantMessageServerConnector, HGInventoryServiceConnector and HGAssetServiceConnector. Check active sections and ports rather than blindly copying defaults.
Adapt this example: do not apply it blindly.
[Const]
BaseHostname = "grid.example.org"
BaseURL = "http://${Const|BaseHostname}"
PublicPort = "8002"
PrivatePort = "8003"HomeURI and GatekeeperURI: different roles
HomeURI locates the avatar's home/identity service. GatekeeperURI identifies the entry point into a Hypergrid world. They may share an URL if services are colocated, but the settings have distinct roles. Configure [Hypergrid] for your actual architecture and validate from another grid.
Adapt this example: do not apply it blindly.
[Hypergrid] HomeURI = "http://grid.example.org:8002" GatekeeperURI = "http://grid.example.org:8002"
Traveller inventory and suitcase
StandaloneHypergrid.ini refers to HGInventoryBroker and HGSuitcaseInventoryService. Cross-grid traveller inventory differs from ordinary local inventory. Do not remove these services without understanding visitor impact.
Region public addresses
Regions must advertise an ExternalHostName and InternalPort that match reachable addresses and ports. Visitors may reach Gatekeeper but fail teleport if region ports or announced external address are wrong.
Adapt this example: do not apply it blindly.
[MaRegion] RegionUUID = 11111111-2222-3333-4444-555555555555 InternalAddress = 0.0.0.0 InternalPort = 9000 ExternalHostName = region.example.org
Test both travel directions
First test local login and internal teleports. Then try inbound travel from a foreign grid and outbound travel from your own grid. Check identity, appearance, transferable inventory, home return and logs on both grids. One successful teleport does not validate all HG features.
Security boundaries
A Hypergrid-enabled world accepts traffic from separately administered installations. Keep ROBUST private ports and SQL private, protect inventory, review region permissions and maintain backups. Do not assume remote content or scripts are trustworthy.