OpenSimWorld is the directory of 3D Virtual Worlds based on OpenSimulator and connected through the HyperGrid. Learn More
New Members
Brea Brianna, Romafray, Fecxyd5pmn, MacDawson, Nolanpierce, Liradhel0, Hilde, ToniDellacroux, Lilwxck, NicholasK, Girlfriend0, Light_Ray, Babykat, Jemes, AmbarDarcy, FelixOrlov, Max Rilaxin, Dokternow, Vampy69, SeldonLikes
Allow external SIMs to attach to grid?
I was curious: how does one go about allowing external SIMs to attach to private (yet hypergrid enabled) grid the way that OSGrid allows you to?
I've searched through the documentation and don't see anything stating how to do so, but I could have easily scanned past it.
I've searched through the documentation and don't see anything stating how to do so, but I could have easily scanned past it.
Comments
If you want to allow external simulators to attach to a private but Hypergrid-enabled grid the way OSGrid does, you must explicitly configure region authentication and service trust. There is no single switch unless you are using an appliance like DreamGrid.
Step 1: Expose and enable grid services
On the grid host, Robust must expose:
GridService
GatekeeperService
AssetService
InventoryService
AuthenticationService
Hypergrid must be enabled in Robust.HG.ini:
Gatekeeper enabled
Foreign agent access allowed
External DNS name or public IP correctly set
Step 2: Enable external region registration
In GridCommon.ini on the grid:
Allow region registration from non-local simulators
Set a shared region authentication secret
Disable auto-accept if you want manual control
This is the mechanism OSGrid uses. External regions are not “trusted by default”, they authenticate.
Step 3: Issue credentials to the region operator
For each external region, provide:
GridURI
GatekeeperURI
Shared secret or region key
Required service endpoints
Without these, the region will never register.
Step 4: Configure the external simulator
On the external sim:
Run in region-only or standalone mode
Point all services to the grid’s Robust endpoints
Disable local asset, inventory, and user services
Use the shared secret issued by the grid
This is done in OpenSim.ini and GridCommon.ini.
Step 5: Start the external sim and register the region
When the sim starts:
It authenticates against the grid
Registers the region
Appears on the grid map
Behaves identically to a locally hosted region
Step 6: Control access
Optional but recommended:
Whitelist region IPs
Use unique secrets per region
Monitor region registrations
Revoke credentials if needed
Summary
OSGrid does not use a special feature. It allows external sims by:
Running Robust publicly
Authenticating regions explicitly
Treating regions as peers, not appliances
DreamGrid hides these steps behind a UI toggle. Manual grids must do the same work explicitly.
like(0)
Step 1: Expose and enable grid services
On the grid host, Robust must expose:
GridService
GatekeeperService
AssetService
InventoryService
AuthenticationService
Hypergrid must be enabled in Robust.HG.ini:
Gatekeeper enabled
Foreign agent access allowed
External DNS name or public IP correctly set
Step 2: Enable external region registration
In GridCommon.ini on the grid:
Allow region registration from non-local simulators
Set a shared region authentication secret
Disable auto-accept if you want manual control
This is the mechanism OSGrid uses. External regions are not “trusted by default”, they authenticate.
Step 3: Issue credentials to the region operator
For each external region, provide:
GridURI
GatekeeperURI
Shared secret or region key
Required service endpoints
Without these, the region will never register.
Step 4: Configure the external simulator
On the external sim:
Run in region-only or standalone mode
Point all services to the grid’s Robust endpoints
Disable local asset, inventory, and user services
Use the shared secret issued by the grid
This is done in OpenSim.ini and GridCommon.ini.
Step 5: Start the external sim and register the region
When the sim starts:
It authenticates against the grid
Registers the region
Appears on the grid map
Behaves identically to a locally hosted region
Step 6: Control access
Optional but recommended:
Whitelist region IPs
Use unique secrets per region
Monitor region registrations
Revoke credentials if needed
Summary
OSGrid does not use a special feature. It allows external sims by:
Running Robust publicly
Authenticating regions explicitly
Treating regions as peers, not appliances
DreamGrid hides these steps behind a UI toggle. Manual grids must do the same work explicitly.
Its a "region Server" . Its a setting in Dreamgrid. Go to Server type in settings and change it to Region Server. There is a help menu for every setting.
like(2)