OpenSimulator - User contributions [en]

NPC

2022-09-19T13:33:19Z

Arielle: /* Resources */

{{Languages|NPC}}
= Introduction =

Broadly speaking, there are 3 ways in which Non Player Characters (NPCs) aka bots, can be operated in OpenSimulator.

== 1. Client side approaches ==

For instance, use [http://openmetaverse.org/projects/libopenmetaverse libopenmetaverse] to operate an avatar as if it were being controlled through the viewer.

This wiki does contain some information on how to do this - see

* [[Building a bot]] - Getting started with bot design using libomv from the client side
* [[pCampBot]] - A facility for stress-testing opensim which can be used as bot example code.

However, better information can be found elsewhere, since this method applies to both Linden Lab and other third party grids.

This is how bots have been traditionally done in SL, since Linden Lab provide no scripting methods for NPCs or direct access to the server software. One advantage of this method, as stated above, is that it can easily be ported between Linden Lab and third party grids, since it only relies on the client interface (leaving aside whether the grid has a policy about allowing bots). It also allows bots to go anywhere and do anything that a human could do, with the right programming. One disadvantage is that it requires user accounts to exist for the bots.

== 2. osNpc*() scripting functions ==

OpenSimulator provides a set of OSSL NPC functions for creating and manipulating bots. Please see [[OSSLNPC]] for more details.

One advantage of this approach is that no external client is necessary for a bot, and bot appearances can be saved in OpenSimulator Archives (OARs). One disadvantage is that there is a much more limited subset of functionality available, since script methods have to be written to control different aspects of an NPC. Also, such bots cannot move out of the region in which they are created.

== 3. Region Module ==

In OpenSim, the osNpc*() script methods use the internal NPCModule to actually manage and manipulate bots. Another region module could call the NPCModule methods directly. One advantage of this approach is that bot management may be easier in C# than in LSL/OSSL. One disadvantage is that any change to a region module requires recompilation and restart of the simulator in which it is hosted.

= Resources =

* The [https://grimore.org/opensim/npc Wizardry and Steamworks NPC page] contains some freely available NPC scripts, including a wandering NPC, and an NPC that uses a simple notecard-based language to "playwright" an NPC. It was used for creating "scenarios" on an educational, health-related simulator.

* [[User:Fritigern/Scripts]] contains NPC utilities.

* [[User:Dz]] provides utilities for generating, removing, and animating NPC's

[[Category:Scripting]]

Feature Matrix

2018-12-06T15:15:39Z

Arielle:

{{Quicklinks}}
 

= Einführung =

This is a matrix of the features currently implemented in OpenSimulator. Please feel free to correct existing entries and add new ones. The data in this matrix refers to the currently released version of OpenSimulator unless otherwise stated.

OpenSimulator can run on Linux & Mac with MONO, see the [http://www.mono-project.com/Main_Page Mono project] for availability or your distribution provider. Windows requires Net Framework 3.51 available from [http://www.microsoft.com/downloads/en/details.aspx?FamilyID=ab99342f-5d1a-413d-8319-81da479ab0d7&displaylang=en MS Downloads]

 

== Prims ==

{| border="1"
|-
! Feature Name
! Core OpenSim?
! Notes
|-
| Create/change/move/delete prims
| bgcolor="#00ff00" align="center" | Yes
|  
|-
| Prim sizing
| bgcolor="#00ff00" align="center" | Yes
| Default supported sizes 0.001m to 256.000m (Viewer Support Required)
|-
| Prim hollows
| bgcolor="#00ff00" align="center" | Yes
| Default supported hollows to 99% or 0.001 (Viewer Support Required)
|-
| Persistent prim inventories
| bgcolor="#00ff00" align="center" | Yes
|  
|-
| Basic asset types
| bgcolor="#00ff00" align="center" | Yes
| Basic asset types include textures, sounds, notecards, etc.
|-
| Coalesced object groups
| bgcolor="#00ff00" align="center" | Yes
| Coalesced object groups means being able to take a selection of unlinked objects as one group that can be rezzed back in the same spatial arrangements. Support added in OpenSimulator 0.7.1
|-
| Linksets
| bgcolor="#00ff00" align="center" | Yes
| Bugs (some fairly fundamental) remain with linksets but basic support is implemented.
|-
| Linkset Limits
| bgcolor="#00ff00" align="center" | Yes
| Can be larger than 255 prims, and can cover an entire region. (Viewer Support Required)
|-
| [http://community.secondlife.com/t5/English-Knowledge-Base/Shared-Media/ta-p/700145 Media on a prim/Shared Media]
| bgcolor="#00ff00" align="center" | Yes
| Support added in OpenSimulator 0.7.1.
|-
| [[Dynamic textures]]
| bgcolor="#00ff00" align="center" | Yes
| Dynamic textures are textures that can be created on the fly via draw commands.
|-
| Sculpties
| bgcolor="#00ff00" align="center" | Yes
|  
|-
| [[Mesh]]
| bgcolor="#00ff00" align="center" | Yes
| Mesh was implemented in OpenSimulator 0.7.2 onwards. Complies with current Linden Lab viewer 3 specs. Previous OpenSimulator versions contained the initial beta implementation. Please note that this feature is experimental and should be used cautiously.
|}

 

== Users ==

{| border="1"
|-
! Feature Name
! Core OpenSim?
! Notes
|-
| Walking
| bgcolor="#00ff00" align="center" | Yes
|  
|-
| Flying
| bgcolor="#00ff00" align="center" | Yes
|  
|-
| Sitting
| bgcolor="#00ff00" align="center" | Yes
|  
|-
| Animations
| bgcolor="#00ff00" align="center" | Yes
|  
|-
| Gestures
| bgcolor="#00ff00" align="center" | Yes
|  
|-
| Attachments
| bgcolor="#ffd700" align="center" | Partial
| Both worn attachments and Head Up Displays (HUDs) are implemented. Outfits are implemented. Wearing multiple attachments at a single point will be a feature of the forthcoming OpenSimulator 0.7.6. Temporary attachments may be buggy.
|-
| Combat
| bgcolor="#00ff00" align="center" | Yes
|  
|-
| Region crossing
| bgcolor="#00ff00" align="center" | Yes
|  
|-
| Teleport
| bgcolor="#00ff00" align="center" | Yes
|  
|-
| Persistent avatar inventories
| bgcolor="#00ff00" align="center" | Yes
|  
|-
| Inventory library
| bgcolor="#00ff00" align="center" | Yes
|  
|-
| Chat
| bgcolor="#00ff00" align="center" | Yes
|  
|-
| Instant messaging
| bgcolor="#00ff00" align="center" | Yes
| Offline IM storage requires third party packages such as http://forge.opensimulator.org/gf/project/opensimwi/ in releases before 0.7.2. And between 0.7.2 and current dev code (pre 0.7.6) it still required external PHP scripts. See [[Offline Messaging]] for more details.
|-
| Names
| bgcolor="#ffd700" align="center" | Partial
| Ordinary names consisting of a first and last name separated by a space are implemented. 'Display' names are not yet implemented.
|-
| Archiving
| bgcolor="#00ff00" align="center" | Yes
| Users inventories and parts of inventories can be saved and loaded as [[Inventory Archives|OpenSimulator Inventory Archives]].
|-
| Friends
| bgcolor="#00ff00" align="center" | Yes
|  
|-
| Lure
| bgcolor="#00ff00" align="center" | Yes
|  
|-
| [[Enabling Groups|Groups]]
| bgcolor="#ffffff" align="center" | 3rd party
| Group support is only available as third party projects:
* [https://github.com/mcortez/flotsam Group service implementation from the Flotsam project]. '''Please note: this is not working properly with OpenSimulator 0.7.0.1 or 0.7.0.2, though it is fixed in OpenSimulator 0.7.1 and onwards. 0.6.9 should also work okay.'''
* [https://github.com/jor3l/OSModules/tree/master/osgroups/ osgroups from jor3l]
* [http://code.google.com/p/openmetaverse SimianGrid] also provides a Groups connector as part of its grid services package.

These services have connectors that are bundled with core OpenSimulator. See [[Enabling Groups]] and the OpenSim.ini.example file for more details.

|-
| Profiles
| bgcolor="#ffffff" align="center" | 3rd party
|
Only avatar names are stored in core OpenSimulator. Profile support (e.g. interests, 1st Life, etc.) is available via 3rd party modules, though these may currently only support OpenSimulator 0.6.9. Please add suitable links here.

* [http://forge.opensimulator.org/gf/project/osprofile forge.opensimulator.org/gf/project/osprofile]

|-
| Search
| bgcolor="#ffffff" align="center" | 3rd party
| Search support is only available via third party modules.
* [[OpenSimSearch]]
|}

== Scripting ==

{| border="1"
|-
! Feature Name
! Core OpenSim?
! Notes
|-
| [[Developer Documentation#Scripting|Scripts]]
| bgcolor="#00ff00" align="center" | Yes
| A large percentage (though not all) of LSL is implemented by OpenSimulator. There are also OpenSimulator specific OSSL functions available.
|-
| [[Non-LSL scripting|C# scripting]]
| bgcolor="#00ff00" align="center" | Yes
| C# scripting is experimental and insecure. However, it can be useful in some situations
|-
| Script control
| bgcolor="#00ff00" align="center" | Yes
| There are some facilities to control what user types can create and edit scripts. This can help secure an implementation using C# scripts. See the OpenSim.ini.example file in the OpenSimulator distribution for more details.
|}

 

== World ==

{| border="1"
|-
! Feature Name
! Core OpenSim?
! Notes
|-
| Terrain
| bgcolor="#00ff00" align="center" | Yes
|  
|-
| Sun
| bgcolor="#00ff00" align="center" | Yes
|  
|-
| Wind
| bgcolor="#00ff00" align="center" | Yes
|  
|-
| Cloud
| bgcolor="#00ff00" align="center" | Yes
|  
|-
| Vegetation
| bgcolor="#00ff00" align="center" | Yes
|  
|-
| Sound
| bgcolor="#ffd700" align="center" | Yes
| Queueing sounds will be supported in the forthcoming OpenSimulator 0.7.6. However, not all sound facilities have been well tested (if there are gaps please set this back to partial and list them).
|-
| Minimap
| bgcolor="#00ff00" align="center" | Yes
|  
|-
| World Map
| bgcolor="#00ff00" align="center" | Yes
|  
|-
| Neighbouring regions
| bgcolor="#00ff00" align="center" | Yes
| Regions can neighbour each other, even if hosted on different servers.
|-
| Archiving
| bgcolor="#00ff00" align="center" | Yes
| Entire regions can be saved and loaded as [[OpenSim Archives]].
|-
| [[PhysicsEngines|Physics]]
| bgcolor="#00ff00" align="center" | Yes
| There are several physics modules bundled with current Opensimulator. The two most popular and best supported are Bulletsim and as of .9.0.0 UbOde. BulletSim is the current default.
|-
| Parcel management
| bgcolor="#00ff00" align="center" | Yes
|  
|-
| Region settings
| bgcolor="#00ff00" align="center" | Yes
|  
|-
| Region / Parcel Lightshare / Windlight
| bgcolor="#00ff00" align="center" | Yes
| Lightshare implemented March 30,2010 (Git: ec637e2b8). LightShare/WindLight from Region to Client enables full environmental control of the simulation, providing a more complete immersive experience. Supported in most V3 and some modified V1 Viewers.
|-
| Telehubs
| bgcolor="#00ff00" align="center" | Yes
|  
|-
| Estates
| bgcolor="#ffd700" align="center" | Partial
| Partial estate support is implemented. However, the only way to manipulate estates currently is via direct changes to the database.
|-
| Avatar limits
| bgcolor="#00ff00" align="center" | Yes
| Avatar limits were implemented in OpenSimulator 0.7.2.
|-
| Prim limits
| bgcolor="#00ff00" align="center" | Yes
| Prim limits where implement in OpenSimulator 0.7.2.
|-
| Teleports
| bgcolor="#ffd700" align="center" | Partial
| Teleporting in can be done to any point in or off world (if hypergrid enabled) however, Blocking teleports to a parcel is not currently enforced.
|-
| Megaregions
| bgcolor="#ff0000" align="center" | Deprecated
| Megaregions are deprecated after vers. .8.2.1. Please see Varregions for its replacement. This is a system that allows regions to be created on the simulator that are larger than 256m x 256m. This is implemented purely on the server without requiring a specially adapted client. However, this is not fully implemented and you may encounter various issues with megaregions.
|-
| [[OSSLNPC|NPCs]]
| bgcolor="#00ff00" align="center" | Yes
| Allow NPCs to be created and manipulated on a region. This is handled purely on the server-side - NPCs are different from bots controlled as external clients via a library such as libomv.
|-
| Pathfinding
| bgcolor="#ff0000" align="center" | No
|-
| Varregions
| bgcolor="#00ff00" align="center" | Yes
| This is a system that allows regions to be created on the simulator that are larger than 256m x 256m. Please see http://opensimulator.org/wiki/Varregion for the most up-to-date information.
|
|}

 

== Other Simulation Features ==

{| border="1"
|-
! Feature Name
! Core OpenSim?
! Notes
|-
| IRC
| bgcolor="#00ff00" align="center" | Yes
| Relay chat back and forth to an Internet Relay Channel.
|-
| Money
| bgcolor="#ffffff" align="center" | 3rd party
| There are no plans to directly provide economy modules in OpenSimulator though custom currency names are supported in 0.7.2 and after. Third party facilities include:
* [http://forge.opensimulator.org/melanie/OpenCurrency OpenCurrency]
* [http://forge.opensimulator.org/gf/project/currency/ DTL Currency]
* [http://github.com/SnoopyPfeffer/Mod-PayPal Mod-PayPal]
* [https://www.virwox.com/omc-open-metaverse-currency.php Open Metaverse Currency (OMC)]
* [http://www.nsl.tuis.ac.jp/xoops/modules/xpwiki/?OpenSim%2FMoneyServer DTL/NSL Money Server]
|-
| Permissions
| bgcolor="#00ff00" align="center" | Yes
| Permissions (e.g. controlling whether objects can be modified or copied) must be enabled in OpenSim.ini - these are not enabled by default
|-
| [[Monitoring]]
| bgcolor="#ffd700" align="center" | Partial
| A number of monitoring facilities exist, though none of them yet cover everything that one would want to monitor.
|-
| Voice
| bgcolor="#ffd700" align="center" | Partial
| Voice support is currently primitive. OpenSimulator currently bundles a Vivox module (only usable with a Vivox voice server) and a [[Freeswitch Module|Freeswitch module]]. A third party [[Mumble]] voice module also exists which supports indication of which avatar is speaking. No module yet supports spatial voice.
|-
| Web frontends
| bgcolor="#ffffff" align="center" | 3rd party
| Various third-party web frontends are available, detailed on the [[Webinterface]] page.
|}

 

== Server Features ==

{| border="1"
|-
! Feature Name
! Core OpenSim?
! Notes
|-
| Local console
| bgcolor="#00ff00" align="center" | Yes
| The local command console in OpenSimulator is the one present when you start an OpenSimulator instance
|-
| [[RestConsole|Remote console]]
| bgcolor="#ffd700" align="center" | Partial
| This is not yet widely used and a few bugs have been reported with current functionality.
|-
| [[RemoteAdmin|Remote admin]]
| bgcolor="#00ff00" align="center" | Yes
| The remote admin plugin allows OpenSimulator commands to be executed remotely.
|-
| [[Logging]]
| bgcolor="#00ff00" align="center" | Yes
| OpenSimulator uses the log4net package. More details on the logging page.
|}

 

== Architectures ==

{| border="1"
|-
! Feature Name
! Core OpenSim?
! Notes
|-
| Single server (standalone) mode
| bgcolor="#00ff00" align="center" | Yes
| Persistent databases supported in standalone mode are SQLite and MySQL. A MSSQL exists and should work, but is not officially supported.
|-
| Grid (multi-server) mode
| bgcolor="#00ff00" align="center" | Yes
| In grid mode, only persistence to a MySQL database is officially supported. Persistence can also be done with a MSSQL database but this is not officially supported.
|-
| [[Hypergrid]]
| bgcolor="#ff0000" align="center" | Experimental
| This is an architecture, [http://en.wikipedia.org/wiki/Orthogonal orthogonal] to the previous two, that allows users to visit completely separate OpenSimulator installations while retaining their appearance, identity and inventory. This is under active development and should be considered experimental.
|}

Feature Matrix

2018-12-06T15:04:26Z

Arielle:

{{Quicklinks}}
 

= Einführung =

This is a matrix of the features currently implemented in OpenSimulator. Please feel free to correct existing entries and add new ones. The data in this matrix refers to the currently released version of OpenSimulator unless otherwise stated.

OpenSimulator can run on Linux & Mac with MONO, see the [http://www.mono-project.com/Main_Page Mono project] for availability or your distribution provider. Windows requires Net Framework 3.51 available from [http://www.microsoft.com/downloads/en/details.aspx?FamilyID=ab99342f-5d1a-413d-8319-81da479ab0d7&displaylang=en MS Downloads]

 

== Prims ==

{| border="1"
|-
! Feature Name
! Core OpenSim?
! Notes
|-
| Create/change/move/delete prims
| bgcolor="#00ff00" align="center" | Yes
|  
|-
| Prim sizing
| bgcolor="#00ff00" align="center" | Yes
| Default supported sizes 0.001m to 256.000m (Viewer Support Required)
|-
| Prim hollows
| bgcolor="#00ff00" align="center" | Yes
| Default supported hollows to 99% or 0.001 (Viewer Support Required)
|-
| Persistent prim inventories
| bgcolor="#00ff00" align="center" | Yes
|  
|-
| Basic asset types
| bgcolor="#00ff00" align="center" | Yes
| Basic asset types include textures, sounds, notecards, etc.
|-
| Coalesced object groups
| bgcolor="#00ff00" align="center" | Yes
| Coalesced object groups means being able to take a selection of unlinked objects as one group that can be rezzed back in the same spatial arrangements. Support added in OpenSimulator 0.7.1
|-
| Linksets
| bgcolor="#00ff00" align="center" | Yes
| Bugs (some fairly fundamental) remain with linksets but basic support is implemented.
|-
| Linkset Limits
| bgcolor="#00ff00" align="center" | Yes
| Can be larger than 255 prims, and can cover an entire region. (Viewer Support Required)
|-
| [http://community.secondlife.com/t5/English-Knowledge-Base/Shared-Media/ta-p/700145 Media on a prim/Shared Media]
| bgcolor="#00ff00" align="center" | Yes
| Support added in OpenSimulator 0.7.1.
|-
| [[Dynamic textures]]
| bgcolor="#00ff00" align="center" | Yes
| Dynamic textures are textures that can be created on the fly via draw commands.
|-
| Sculpties
| bgcolor="#00ff00" align="center" | Yes
|  
|-
| [[Mesh]]
| bgcolor="#00ff00" align="center" | Yes
| Mesh was implemented in OpenSimulator 0.7.2 onwards. Complies with current Linden Lab viewer 3 specs. Previous OpenSimulator versions contained the initial beta implementation. Please note that this feature is experimental and should be used cautiously.
|}

 

== Users ==

{| border="1"
|-
! Feature Name
! Core OpenSim?
! Notes
|-
| Walking
| bgcolor="#00ff00" align="center" | Yes
|  
|-
| Flying
| bgcolor="#00ff00" align="center" | Yes
|  
|-
| Sitting
| bgcolor="#00ff00" align="center" | Yes
|  
|-
| Animations
| bgcolor="#00ff00" align="center" | Yes
|  
|-
| Gestures
| bgcolor="#00ff00" align="center" | Yes
|  
|-
| Attachments
| bgcolor="#ffd700" align="center" | Partial
| Both worn attachments and Head Up Displays (HUDs) are implemented. Outfits are implemented. Wearing multiple attachments at a single point will be a feature of the forthcoming OpenSimulator 0.7.6. Temporary attachments may be buggy.
|-
| Combat
| bgcolor="#00ff00" align="center" | Yes
|  
|-
| Region crossing
| bgcolor="#00ff00" align="center" | Yes
|  
|-
| Teleport
| bgcolor="#00ff00" align="center" | Yes
|  
|-
| Persistent avatar inventories
| bgcolor="#00ff00" align="center" | Yes
|  
|-
| Inventory library
| bgcolor="#00ff00" align="center" | Yes
|  
|-
| Chat
| bgcolor="#00ff00" align="center" | Yes
|  
|-
| Instant messaging
| bgcolor="#00ff00" align="center" | Yes
| Offline IM storage requires third party packages such as http://forge.opensimulator.org/gf/project/opensimwi/ in releases before 0.7.2. And between 0.7.2 and current dev code (pre 0.7.6) it still required external PHP scripts. See [[Offline Messaging]] for more details.
|-
| Names
| bgcolor="#ffd700" align="center" | Partial
| Ordinary names consisting of a first and last name separated by a space are implemented. 'Display' names are not yet implemented.
|-
| Archiving
| bgcolor="#00ff00" align="center" | Yes
| Users inventories and parts of inventories can be saved and loaded as [[Inventory Archives|OpenSimulator Inventory Archives]].
|-
| Friends
| bgcolor="#00ff00" align="center" | Yes
|  
|-
| Lure
| bgcolor="#00ff00" align="center" | Yes
|  
|-
| [[Enabling Groups|Groups]]
| bgcolor="#ffffff" align="center" | 3rd party
| Group support is only available as third party projects:
* [https://github.com/mcortez/flotsam Group service implementation from the Flotsam project]. '''Please note: this is not working properly with OpenSimulator 0.7.0.1 or 0.7.0.2, though it is fixed in OpenSimulator 0.7.1 and onwards. 0.6.9 should also work okay.'''
* [https://github.com/jor3l/OSModules/tree/master/osgroups/ osgroups from jor3l]
* [http://code.google.com/p/openmetaverse SimianGrid] also provides a Groups connector as part of its grid services package.

These services have connectors that are bundled with core OpenSimulator. See [[Enabling Groups]] and the OpenSim.ini.example file for more details.

|-
| Profiles
| bgcolor="#ffffff" align="center" | 3rd party
|
Only avatar names are stored in core OpenSimulator. Profile support (e.g. interests, 1st Life, etc.) is available via 3rd party modules, though these may currently only support OpenSimulator 0.6.9. Please add suitable links here.

* [http://forge.opensimulator.org/gf/project/osprofile forge.opensimulator.org/gf/project/osprofile]

|-
| Search
| bgcolor="#ffffff" align="center" | 3rd party
| Search support is only available via third party modules.
* [[OpenSimSearch]]
|}

== Scripting ==

{| border="1"
|-
! Feature Name
! Core OpenSim?
! Notes
|-
| [[Developer Documentation#Scripting|Scripts]]
| bgcolor="#00ff00" align="center" | Yes
| A large percentage (though not all) of LSL is implemented by OpenSimulator. There are also OpenSimulator specific OSSL functions available.
|-
| [[Non-LSL scripting|C# scripting]]
| bgcolor="#00ff00" align="center" | Yes
| C# scripting is experimental and insecure. However, it can be useful in some situations
|-
| Script control
| bgcolor="#00ff00" align="center" | Yes
| There are some facilities to control what user types can create and edit scripts. This can help secure an implementation using C# scripts. See the OpenSim.ini.example file in the OpenSimulator distribution for more details.
|}

 

== World ==

{| border="1"
|-
! Feature Name
! Core OpenSim?
! Notes
|-
| Terrain
| bgcolor="#00ff00" align="center" | Yes
|  
|-
| Sun
| bgcolor="#00ff00" align="center" | Yes
|  
|-
| Wind
| bgcolor="#00ff00" align="center" | Yes
|  
|-
| Cloud
| bgcolor="#00ff00" align="center" | Yes
|  
|-
| Vegetation
| bgcolor="#00ff00" align="center" | Yes
|  
|-
| Sound
| bgcolor="#ffd700" align="center" | Yes
| Queueing sounds will be supported in the forthcoming OpenSimulator 0.7.6. However, not all sound facilities have been well tested (if there are gaps please set this back to partial and list them).
|-
| Minimap
| bgcolor="#00ff00" align="center" | Yes
|  
|-
| World Map
| bgcolor="#00ff00" align="center" | Yes
|  
|-
| Neighbouring regions
| bgcolor="#00ff00" align="center" | Yes
| Regions can neighbour each other, even if hosted on different servers.
|-
| Archiving
| bgcolor="#00ff00" align="center" | Yes
| Entire regions can be saved and loaded as [[OpenSim Archives]].
|-
| [[PhysicsEngines|Physics]]
| bgcolor="#00ff00" align="center" | Yes
| There are several physics modules bundled with OpenSim, but only the ODE module (Open Dynamics Engine) really works.
|-
| Parcel management
| bgcolor="#00ff00" align="center" | Yes
|  
|-
| Region settings
| bgcolor="#00ff00" align="center" | Yes
|  
|-
| Region / Parcel Lightshare / Windlight
| bgcolor="#00ff00" align="center" | Yes
| Lightshare implemented March 30,2010 (Git: ec637e2b8). LightShare/WindLight from Region to Client enables full environmental control of the simulation, providing a more complete immersive experience. Supported in most V3 and some modified V1 Viewers.
|-
| Telehubs
| bgcolor="#00ff00" align="center" | Yes
|  
|-
| Estates
| bgcolor="#ffd700" align="center" | Partial
| Partial estate support is implemented. However, the only way to manipulate estates currently is via direct changes to the database.
|-
| Avatar limits
| bgcolor="#00ff00" align="center" | Yes
| Avatar limits were implemented in OpenSimulator 0.7.2.
|-
| Prim limits
| bgcolor="#00ff00" align="center" | Yes
| Prim limits where implement in OpenSimulator 0.7.2.
|-
| Teleports
| bgcolor="#ffd700" align="center" | Partial
| Teleporting in can be done to any point in or off world (if hypergrid enabled) however, Blocking teleports to a parcel is not currently enforced.
|-
| Megaregions
| bgcolor="#ff0000" align="center" | Deprecated
| Megaregions are deprecated after vers. .8.2.1. Please see Varregions for its replacement. This is a system that allows regions to be created on the simulator that are larger than 256m x 256m. This is implemented purely on the server without requiring a specially adapted client. However, this is not fully implemented and you may encounter various issues with megaregions.
|-
| [[OSSLNPC|NPCs]]
| bgcolor="#00ff00" align="center" | Yes
| Allow NPCs to be created and manipulated on a region. This is handled purely on the server-side - NPCs are different from bots controlled as external clients via a library such as libomv.
|-
| Pathfinding
| bgcolor="#ff0000" align="center" | No
|-
| Varregions
| bgcolor="#00ff00" align="center" | Yes
| This is a system that allows regions to be created on the simulator that are larger than 256m x 256m. Please see http://opensimulator.org/wiki/Varregion for the most up-to-date information.
|
|}

 

== Other Simulation Features ==

{| border="1"
|-
! Feature Name
! Core OpenSim?
! Notes
|-
| IRC
| bgcolor="#00ff00" align="center" | Yes
| Relay chat back and forth to an Internet Relay Channel.
|-
| Money
| bgcolor="#ffffff" align="center" | 3rd party
| There are no plans to directly provide economy modules in OpenSimulator though custom currency names are supported in 0.7.2 and after. Third party facilities include:
* [http://forge.opensimulator.org/melanie/OpenCurrency OpenCurrency]
* [http://forge.opensimulator.org/gf/project/currency/ DTL Currency]
* [http://github.com/SnoopyPfeffer/Mod-PayPal Mod-PayPal]
* [https://www.virwox.com/omc-open-metaverse-currency.php Open Metaverse Currency (OMC)]
* [http://www.nsl.tuis.ac.jp/xoops/modules/xpwiki/?OpenSim%2FMoneyServer DTL/NSL Money Server]
|-
| Permissions
| bgcolor="#00ff00" align="center" | Yes
| Permissions (e.g. controlling whether objects can be modified or copied) must be enabled in OpenSim.ini - these are not enabled by default
|-
| [[Monitoring]]
| bgcolor="#ffd700" align="center" | Partial
| A number of monitoring facilities exist, though none of them yet cover everything that one would want to monitor.
|-
| Voice
| bgcolor="#ffd700" align="center" | Partial
| Voice support is currently primitive. OpenSimulator currently bundles a Vivox module (only usable with a Vivox voice server) and a [[Freeswitch Module|Freeswitch module]]. A third party [[Mumble]] voice module also exists which supports indication of which avatar is speaking. No module yet supports spatial voice.
|-
| Web frontends
| bgcolor="#ffffff" align="center" | 3rd party
| Various third-party web frontends are available, detailed on the [[Webinterface]] page.
|}

 

== Server Features ==

{| border="1"
|-
! Feature Name
! Core OpenSim?
! Notes
|-
| Local console
| bgcolor="#00ff00" align="center" | Yes
| The local command console in OpenSimulator is the one present when you start an OpenSimulator instance
|-
| [[RestConsole|Remote console]]
| bgcolor="#ffd700" align="center" | Partial
| This is not yet widely used and a few bugs have been reported with current functionality.
|-
| [[RemoteAdmin|Remote admin]]
| bgcolor="#00ff00" align="center" | Yes
| The remote admin plugin allows OpenSimulator commands to be executed remotely.
|-
| [[Logging]]
| bgcolor="#00ff00" align="center" | Yes
| OpenSimulator uses the log4net package. More details on the logging page.
|}

 

== Architectures ==

{| border="1"
|-
! Feature Name
! Core OpenSim?
! Notes
|-
| Single server (standalone) mode
| bgcolor="#00ff00" align="center" | Yes
| Persistent databases supported in standalone mode are SQLite and MySQL. A MSSQL exists and should work, but is not officially supported.
|-
| Grid (multi-server) mode
| bgcolor="#00ff00" align="center" | Yes
| In grid mode, only persistence to a MySQL database is officially supported. Persistence can also be done with a MSSQL database but this is not officially supported.
|-
| [[Hypergrid]]
| bgcolor="#ff0000" align="center" | Experimental
| This is an architecture, [http://en.wikipedia.org/wiki/Orthogonal orthogonal] to the previous two, that allows users to visit completely separate OpenSimulator installations while retaining their appearance, identity and inventory. This is under active development and should be considered experimental.
|}

Chat log from the meeting on 2017-10-24

2017-10-24T20:41:07Z

Arielle: Created page with "<pre>[11:10] Arielle Popstar: anyone seen issues? [11:10] Kayaker Magic: Well, I submitted a mantis about that slowdown in list fetches in mono 5.x [11:11] Andrew Hellershan..."

<pre>[11:10] Arielle Popstar: anyone seen issues?
[11:10] Kayaker Magic: Well, I submitted a mantis about that slowdown in list fetches in mono 5.x
[11:11] Andrew Hellershanks: Yes, I saw it.
[11:11] Kayaker Magic: List fetches are ~50 times slower than mono 4.2, which is livable compared to the AppDomain problem that slowed fetches down to 1000 times slower!
[11:12] Andrew Hellershanks: The problem is in mono?
[11:12] Kayaker Magic: Probably.
[11:13] Kayaker Magic: I'm hoping there is something Ubit can do, like change the data type for lists or something.
[11:13] OtakuMegane Desu: It seems something in Mono 5 changed which triggers the slowdown with AppDomainLoading active.
[11:14] Ubit Umarov is online.
[11:14] Kayaker Magic: No, the AppDomainLoading problem is still there. If I set that to true, then I get BOTH slowdowns and fetches are 3000 times slower.
[11:14] Arielle Popstar: what is the current recommended mono version for Opensim?
[11:14] Andrew Hellershanks: I wonder what could have been changed to affect list handling so drastically.
[11:14] OtakuMegane Desu: So two issues that stack
[11:14] Leighton.Marjoram @grid.lighthousepoint.co.uk:8002: Hi Ubit
[11:15] Ubit Umarov: Hi
[11:15] Andrew Hellershanks: brb
[11:15] Kayaker Magic: Yeah, so I started a new mantis (8251) instead of adding it to the old (and different) one (8127)
[11:15] Selby.Evans @grid.kitely.com:8002: hi Ubit
[11:16] Andrew Hellershanks: Arielle, IIRC, not 4.2 :)
[11:16] Ubit Umarov: the lsl lists thing ?
[11:16] Kayaker Magic: Yes, there are apparently two problems.
[11:16] Kayaker Magic: Mono 5.x makes list fetches ~50 times slower.
[11:17] Kayaker Magic: If you also set AppDomainLoading=true they stack and you get list fetches 3000 times slower.
[11:17] Ubit Umarov: think we did pass the AppDomain issue.. it can't be use if you want some performance from scripts
[11:18] Ubit Umarov: leaves us with the problem of deleted script resources not being released
[11:18] Ubit Umarov: but appdomains are not a good solution for this case
[11:19] Ubit Umarov: they are 2 heavy on any simple function call
[11:20] Ubit Umarov: now diferent performance on diferent mono versions.. is a diferent issue... and possible harder
[11:20] George Equus: Hi to those I missed while away :)
[11:20] Ubit Umarov: hmm ? you are all so silent..
[11:21] Arielle Popstar pats herr windows server
[11:21] Andrew Hellershanks: I was looking over the two mantis
[11:24] Andrew Hellershanks: I was thinking of some other tests to check the difference in execution times
[11:24] Kayaker Magic: I looked up mono on the opensimulator.org page, it says "mono 5.x seems to work"
[11:25] Kayaker Magic: "mono 4.0 to 4.6 not ok" I certainly noticed that I could not compile opensim on mono 4.2
[11:25] Arielle Popstar: guess a 1000 times slower qualifies as "seems"
[11:25] Ubit Umarov: well on my home i7 i need to increase the look to 100 000 to see meaninful time
[11:25] OtakuMegane Desu: For the most part yes it seems to. Not perfect though.
[11:25] Kayaker Magic: But mono 4.2 seems to run it OK, even though it cannot compile
[11:25] Andrew Hellershanks: Arielle, not likely to notice the problem unless you run timing tests.
[11:26] Ubit Umarov: 0.000 009 time with 100 000 loops
[11:26] Kayaker Magic: I only noticed because I have some terraforming scripts that loop for every meter of a region.
[11:26] Ubit Umarov: err
[11:26] Ubit Umarov: 0.000 09 ms
[11:27] Kayaker Magic: ms or seconds?
[11:27] Ubit Umarov: oops s
[11:27] Ubit Umarov: its yr script jsut c&p so guess seconds
[11:27] Kayaker Magic: what's 3 orders of magnitude between friends? :)
[11:27] OtakuMegane Desu: It may not be a huge issue in many cases but it shouldn't be chewing up that much extra time without a good reason.
[11:28] Kayaker Magic: I suppose I could go find the mono bug report page and try to write a report up for them.....
[11:28] Ubit Umarov: well a lot slower on the linux VM on mono 5.2
[11:28] Ubit Umarov: 0,0106 S , 100 000 loops
[11:29] Ubit Umarov: hmm i hope im not running with appdomain on it lol
[11:30] Andrew Hellershanks: :)
[11:31] Ubit Umarov: screen -r
[11:31] Ubit Umarov: hmm doesn't work here
[11:32] Arielle Popstar: e and you know it
[11:33] Ubit Umarov: AppDomainLoading = false nopes
[11:33] Ubit Umarov: well that vm is on a old Xeon.. and it is a VM
[11:34] Ubit Umarov: BIll coild tell its details
[11:34] Ubit Umarov: ( i know it does not suport AVX.. so older then 2012 )
[11:35] Arielle Popstar: HAi Brian
[11:35] Brian.. @hg.viewtwo.net:8654: hello
[11:35] Ubit Umarov: there is also that odd up/down keys issue.. i have no clue at the moment
[11:35] Leighton.Marjoram @grid.lighthousepoint.co.uk:8002: Hi Brian
[11:35] Kayaker Magic: What C# data structure does OpenSim use to implement lists?
[11:35] George Equus: Hi Brian
[11:35] Selby.Evans @grid.kitely.com:8002: Hi Brian
[11:35] Andrew Hellershanks: My standalone has ADL set to false. I'll have to run some tests to see what sort of times I get with lists.
[11:36] Andrew Hellershanks: Welcome, Brian.
[11:36] Ubit Umarov: oops ppl just attached the test scripts to mantis
[11:37] Ubit Umarov: hmm does sound like colsion btw vehicle and attachments
[11:37] Ubit Umarov: ADL ?
[11:38] Ubit Umarov: kay at moment think it uses a array
[11:38] Arielle Popstar: app domain loading
[11:39] Ubit Umarov: well adl was a try to release script resources as i said, but it was not done for than on .net... it is a lot heavy
[11:39] Ubit Umarov: it is just a simplicified inter process comunication.. but still a IPC
[11:40] Ubit Umarov: that means tons a extra code on each simple call
[11:40] Arielle Popstar: IPC?
[11:40] Ubit Umarov: ( Inter Process Comunication)
[11:40] Arielle Popstar: ty
[11:40] Ubit Umarov: like word putting things on excel etc..
[11:41] Ubit Umarov: domains where created for a lot simpler cases.. but still IPC
[11:42] Ubit Umarov: so.. we can't really use them on scripts, that do need to have some minimal performance
[11:43] Ubit Umarov: ( and yes that leaves us with the memory and resources leak :( )
[11:43] Andrew Hellershanks: Ubit, I was looking at the code. From what I can tell lists are handled as an array.
[11:44] Andrew Hellershanks: it is defined in LSL_Types.cs
[11:44] Ubit Umarov: but if its a compiler issue.. well we are in trouble...
[11:46] Ubit Umarov: r=llList2Float(test,(integer)llFrand(500.0)); no reason for this to be slower
[11:46] Ubit Umarov: hmm or is it the frand ?
[11:46] Ubit Umarov: lets see with a constant index
[11:47] Kayaker Magic: I never measured the time to create the list, only the time to read it.
[11:47] Andrew Hellershanks: easy to determine that. Just change it to a sequential check of the list elements.
[11:49] Ubit Umarov: r=llList2Float(test,i & 0x1ff); //random fetch same time
[11:50] Andrew Hellershanks: Another test is whether it is a problem with floats or all data types
[11:50] Ubit Umarov: r=llList2Integer(test,i & 0x1ff); same time
[11:50] Kayaker Magic: i originally saw the problem in a mixed list with string and floats.
[11:50] Andrew Hellershanks: ok
[11:51] Ubit Umarov: well i can't test other versions of mono on that VM
[11:52] Ubit Umarov: just can tell my I7, compiled as release and running in 32B it a lot faster
[11:52] Ubit Umarov: ( and on win7 64b)
[11:52] Ubit Umarov: at least 100x
[11:52] Andrew Hellershanks: My machine has mono 3.2.8 that I compiled and 5.2 installed via packages.
[11:53] Andrew Hellershanks: I can test it later with both of those versions.
[11:53] Ubit Umarov: odd the numbers do look a lot like ADL false/true no ?
[11:54] Ubit Umarov: hmm ADL was like 100000x no ?
[11:54] Kayaker Magic: No, it is two orders of magnitude less bad than the ADL results.
[11:54] Ubit Umarov: ok
[11:55] Ubit Umarov: hm and we do use arrays elsewhere on main code... lets hope this is not a larger issue
[11:56] Ubit Umarov: i do expect adding/removing items from lists to be slow
[11:56] Ubit Umarov: not getting them
[11:56] Kayaker Magic: exactly
[11:57] Ubit Umarov: anymore issues?
[11:58] Ubit Umarov: im not beeing very active creating new bugs.. just keep looking to mantis
[11:58] Ubit Umarov: and did mess up the C ( C++) ubOde ODE code
[11:58] Kayaker Magic: Ubit, I would rather that you did not create bugs! Please work on fixing them instead! :)
[11:59] Ubit Umarov: ufff fixing bugs, most time implies add new ones :p
[11:59] Andrew Hellershanks nods
[11:59] Ubit Umarov: but you should know how i say somethings by now ;)
[12:00] Ubit Umarov: well i do see a few things that can be improved on the unmanaged part of ODE
[12:00] Andrew Hellershanks: I've had a couple reports come my way that I'm looking at to see if they are really bugs or not..
[12:00] Ubit Umarov: so playing with that
[12:00] Ubit Umarov: ( yes my test region is now running a odd version )
[12:01] Ubit Umarov: did also some testing using AVX instruction set... but.. yeack no visible improvements
[12:01] Andrew Hellershanks: Wow. This hour really flew by.
[12:02] Ubit Umarov: ( of course fell free to give any tips/donations to my paypal account )
[12:02] Ubit Umarov: :)
[12:03] Ubit Umarov: at some point the httptests branch will be merged into master
[12:03] Andrew Hellershanks: Any other topics for todays meeting?
[12:03] Leighton.Marjoram @grid.lighthousepoint.co.uk:8002: just one quick question
[12:03] Ubit Umarov: that will have some issues with some external modules.. ( one money module at least)
[12:03] Ubit Umarov: due to changes on SSL suport
[12:03] Leighton.Marjoram @grid.lighthousepoint.co.uk:8002: Is SSL fully implemented
[12:03] Leighton.Marjoram @grid.lighthousepoint.co.uk:8002: I am testing it out and not having huge success getting it setup properly
[12:04] Ubit Umarov: i have still a issue with SSL certs control on the several connection types
[12:04] Ubit Umarov: we need diferent rules applied acording to the connection,
[12:04] Ubit Umarov: and .net does not make that any easy
[12:05] Ubit Umarov: adicionallyi do not find some sources of things we use, that needed some change for that
[12:05] Ubit Umarov: (XMLRPC for example)
[12:05] Ubit Umarov: so on SSL part im a bit stuck on that
[12:06] Ubit Umarov: but it does read and uses certs now and we can run a region with SSL enabled
[12:06] Leighton.Marjoram @grid.lighthousepoint.co.uk:8002: Ok that is the bit I am trying to get working
[12:06] Ubit Umarov: just as i said, the control of the validations rules is not good
[12:06] Leighton.Marjoram @grid.lighthousepoint.co.uk:8002: I was also wondering with Robust and OpenSim running SSL is the chat encrypted
[12:07] Ubit Umarov: Robust is another nightmare
[12:07] Ubit Umarov: what services should use SSL... make that configurable... yeack
[12:08] Ubit Umarov: on regions, if you have a valid cert, enforce its use on all things.. httptests should work now
[12:08] Ubit Umarov: ( i did fix the certs load code etc (
[12:08] Ubit Umarov: was dead since 2009 or something :(
[12:08] Leighton.Marjoram @grid.lighthousepoint.co.uk:8002: ok :(
[12:09] Ubit Umarov: well the changes related to that, will make some money modules unhappy
[12:09] Ubit Umarov: bc they do depend on SSL of course
[12:10] Ubit Umarov: and do even patch our code.. something we need to avoid in future
[12:10] Andrew Hellershanks: Ubit, again? :) We already got complaints about money modules breaking due to the API change.
[12:10] Ubit Umarov: since it is a maintnance nightmare
[12:10] Leighton.Marjoram @grid.lighthousepoint.co.uk:8002: Is there any information about SSL support and how to enable it any where
[12:11] Leighton.Marjoram @grid.lighthousepoint.co.uk:8002: I am using Bill BLights version of Opensim osCore2
[12:11] Ubit Umarov: Changed affecting external modules are to be expected.. the surprise was people not understanding that, specially on a major release
[12:12] Ubit Umarov: and at a point where some of those modules do even patch our code, all over
[12:12] Ubit Umarov: impossible to not break things in this case
[12:12] Andrew Hellershanks nods
[12:12] George Equus: Must run along as well, Interesting to follow discussion as always.
[12:12] Leighton.Marjoram @grid.lighthousepoint.co.uk:8002: Bye George
[12:13] George Equus try finding the exit... hmmm
[12:13] Andrew Hellershanks: Just need to make sure the information gets in to the release notes next time.
[12:13] Arielle Popstar: nod
[12:13] Ubit Umarov: and we still need to improve a bit our basic suport for money actions
[12:13] Ubit Umarov: ( not doing any true money code.. that is a opensim NO NO )
[12:14] Ubit Umarov: we will not do code to handle real money.. ( even limited with fake money )
[12:14] Andrew Hellershanks: np, Kayaker. It took a while to get the cast ray stuff sorted out. This may take a while too but eventually we'll get to the bottom of it.
[12:15] Leighton.Marjoram @grid.lighthousepoint.co.uk:8002: I am going to head off too bye for now and see you again next week.
[12:16] Ubit Umarov: a "compilers" diference is not a easy thing
[12:16] Andrew Hellershanks: Ubit, not it isn't. I didn't say how long it would take. :) The raycast thing took a while.
[12:17] Ubit Umarov: raycasts worked for ages ( on ubOde :p )</pre>

Office hours

2017-10-24T20:21:20Z

Arielle: /* Logs */

{{Quicklinks}}
 

OpenSimulator has weekly meetings to discuss parts of the project. These take place on Wright Plaza on OSGrid.

= Meetings =

Meetings on Wright Plaza serve two purposes. One is the meeting described below. The second, and equally important is as a stress test so we can all see how our sim reliability is functioning at each meeting.

Additionally, others are welcome to use the conference room on Wright Plaza for any other meetings they wish. This conference room is setup for meetings and the more use of it, the more testing and development is enhanced.

The two html-on-a-prim on each side of the main screen are both controlled from the chat channel and can be used to present arbitrary web pages to enhance a meeting.

== Tuesday - '''Office Hour''' ==
This meeting is a general technical meeting for the opensim community. All are welcome to participate, but be forewarned that it is developer focused, so attention is mostly given to near term development goals of the project, and those that are contributing code to meet those goals.

In general, we tend to follow a fairly simple agenda format for our one hour.

* First, developers are encouraged to bring up any subjects they wish. Helping the developers focus our efforts is #1.
* Second, testers and users are encouraged to bring up items of community interest that will help development.

At this meeting, anything previously mentioned is fair for discussion for the balance of the meeting. Lets try to keep it moving even at the expense of getting all questions answered as we have a limited time.


'''This meeting is scheduled for 1100 PST, 1400 EST, 1900 UTC, 2000 CET on Projet Secret at OSGrid (osgrid.org). http://hg.osgrid.org:80:Projet Secret'''

== Logs ==




* [[Chat log from the meeting on 2017-10-24]]
* [[Chat log from the meeting on 2017-10-17]]
* [[Chat log from the meeting on 2017-10-10]]
* [[Chat log from the meeting on 2017-10-03]]
* [[Chat log from the meeting on 2017-09-26]]
* [[Chat log from the meeting on 2017-09-19]]
* [[Chat log from the meeting on 2017-09-12]]
* [[Chat log from the meeting on 2017-09-05]]
* [[Chat log from the meeting on 2017-08-29]]
* [[Chat log from the meeting on 2017-08-22]]
* [[Chat log from the meeting on 2017-08-15]]
* [[Chat log from the meeting on 2017-08-08]]
* [[Chat log from the meeting on 2017-08-01]]
* [[Chat log from the meeting on 2017-07-25]]
* [[Chat log from the meeting on 2017-07-18]]
* [[Chat log from the meeting on 2017-07-11]]
* [[Chat log from the meeting on 2017-07-04]]
* [[Chat log from the meeting on 2017-06-27]]
* [[Chat log from the meeting on 2017-06-20]]
* [[Chat log from the meeting on 2017-06-13]]
* [[Chat log from the meeting on 2017-06-06]]
* [[Chat log from the meeting on 2017-05-30]]
* [[Chat log from the meeting on 2017-05-23]]
* [[Chat log from the meeting on 2017-05-16]]
* [[Chat log from the meeting on 2017-05-09]]
* [[Chat log from the meeting on 2017-05-02]]
* [[Chat log from the meeting on 2017-04-25]]
* [[Chat log from the meeting on 2017-04-18]]
* [[Chat log from the meeting on 2017-04-11]]
* [[Chat log from the meeting on 2017-04-04]]
* [[Chat log from the meeting on 2017-03-28]]
* [[Chat log from the meeting on 2017-03-21]]
* [[Chat log from the meeting on 2017-03-14]]
* [[Chat log from the meeting on 2017-03-07]]
* [[Chat log from the meeting on 2017-02-28]]
* [[Chat log from the meeting on 2017-02-21]]
* [[Chat log from the meeting on 2017-02-14]]
* [[Chat log from the meeting on 2017-02-07]]
* [[Chat log from the meeting on 2017-01-31]]
* [[Chat log from the meeting on 2017-01-24]]
* [[Chat log from the meeting on 2017-01-31]]
* [[Chat log from the meeting on 2017-01-24]]
* [[Chat log from the meeting on 2017-01-17]]
* [[Chat log from the meeting on 2017-01-10]]
* [[Chat log from the meeting on 2017-01-03]]
* [[Chat log from the meeting on 2016-12-27]]
* [[Chat log from the meeting on 2016-12-20]]
* [[Chat log from the meeting on 2016-12-13]]
* [[Chat log from the meeting on 2016-12-06]]
* [[Chat log from the meeting on 2016-11-29]]
* [[Chat log from the meeting on 2016-11-22]]
* [[Chat log from the meeting on 2016-11-15]]
* [[Chat log from the meeting on 2016-11-08]]
* [[Chat log from the meeting on 2016-11-01]]
* [[Chat log from the meeting on 2016-10-25]]
* [[Chat log from the meeting on 2016-10-18]]
* [[Chat log from the meeting on 2016-10-11]]
* [[Chat log from the meeting on 2016-10-04]]
* [[Chat log from the meeting on 2016-09-27]]
* [[Chat log from the meeting on 2016-09-20]]
* [[Chat log from the meeting on 2016-09-13]]
* [[Chat log from the meeting on 2016-09-06]]
* [[Chat log from the meeting on 2016-08-30]]
* [[Chat log from the meeting on 2016-08-23]]
* [[Chat log from the meeting on 2016-08-16]]
* [[Chat log from the meeting on 2016-08-09]]
* [[Chat log from the meeting on 2016-08-02]]
* [[Chat log from the meeting on 2016-07-26]]
* [[Chat log from the meeting on 2016-07-19]]
* [[Chat log from the meeting on 2016-07-12]]
* [[Chat log from the meeting on 2016-07-05]]
* [[Chat log from the meeting on 2016-06-28]]
* [[Chat log from the meeting on 2016-06-21]]
* [[Chat log from the meeting on 2016-06-14]]
* [[Chat log from the meeting on 2016-06-07]]
* [[Chat log from the meeting on 2016-05-31]]
* [[Chat log from the meeting on 2016-05-24]]
* [[Chat log from the meeting on 2016-05-17]]
* [[Chat log from the meeting on 2016-05-10]]
* [[Chat log from the meeting on 2016-05-03]]
* [[Chat log from the meeting on 2016-04-26]]
* [[Chat log from the meeting on 2016-04-19]]
* [[Chat log from the meeting on 2016-04-12]]
* [[Chat log from the meeting on 2016-04-05]]
* [[Chat log from the meeting on 2016-03-29]]
* [[Chat log from the meeting on 2016-03-22]]
* [[Chat log from the meeting on 2016-03-15]]
* [[Chat log from the meeting on 2016-03-08]]
* [[Chat log from the meeting on 2016-03-01]]
* [[Chat log from the meeting on 2016-02-23]]
* [[Chat log from the meeting on 2016-02-16]]
* [[Chat log from the meeting on 2016-02-09]]
* [[Chat log from the meeting on 2016-02-02]]
* [[Chat log from the meeting on 2016-01-26]]
* [[Chat log from the meeting on 2016-01-19]]
* [[Chat log from the meeting on 2016-01-12]]
* [[Chat log from the meeting on 2016-01-05]]
* [[Chat log from the meeting on 2015-12-29]]
* [[Chat log from the meeting on 2015-12-22]]
* [[Chat log from the meeting on 2015-12-15]]
* [[Chat log from the meeting on 2015-12-08]]
* [[Chat log from the meeting on 2015-12-01]]
* [[Chat log from the meeting on 2015-11-24]]
* [[Chat log from the meeting on 2015-11-17]]
* [[Chat log from the meeting on 2015-11-10]]
* [[Chat log from the meeting on 2015-11-03]]
* [[Chat log from the meeting on 2015-10-27]]
* [[Chat log from the meeting on 2015-10-20]]
* [[Chat log from the meeting on 2015-10-13]]
* [[Chat log from the meeting on 2015-10-06]]
* [[Chat log from the meeting on 2015-09-29]]
* [[Chat log from the meeting on 2015-09-22]]
* [[Chat log from the meeting on 2015-09-15]]
* [[Chat log from the meeting on 2015-09-08]]
* [[Chat log from the meeting on 2015-09-01]]
* [[Chat log from the meeting on 2015-08-25]]
* [[Chat log from the meeting on 2015-08-18]]
* [[Chat log from the meeting on 2015-08-11]]
* [[Chat log from the meeting on 2015-08-04]]
* [[Chat log from the meeting on 2015-07-28]]
* [[Chat log from the meeting on 2015-07-21]]
* [[Chat log from the meeting on 2015-07-14]]
* [[Chat log from the meeting on 2015-07-07]]
* [[Chat log from the meeting on 2015-06-30]]
* [[Chat log from the meeting on 2015-06-23]]
* [[Chat log from the meeting on 2015-06-09]]
* [[Chat log from the meeting on 2015-06-02]]
* [[Chat log from the meeting on 2015-05-26]]
* [[Chat log from the meeting on 2015-05-19]]
* [[Chat log from the meeting on 2015-05-12]]
* [[Chat log from the meeting on 2015-05-05]]
* [[Chat log from the meeting on 2015-04-28]]
* [[Chat log from the meeting on 2015-04-21]]
* [[Chat log from the meeting on 2015-04-14]]
* [[Chat log from the meeting on 2015-04-07]]
* [[Chat log from the meeting on 2015-03-31]]
* [[Chat log from the meeting on 2015-03-24]]
* [[Chat log from the meeting on 2015-03-17]]
* [[Chat log from the meeting on 2015-03-10]]
* [[Chat log from the meeting on 2015-03-03]]
* [[Chat log from the meeting on 2015-02-24]]
* [[Chat log from the meeting on 2015-02-17]]
* [[Chat log from the meeting on 2015-02-10]]
* [[Chat log from the meeting on 2015-02-03]]
* [[Chat log from the meeting on 2015-01-27]]
* [[Chat log from the meeting on 2015-01-20]]
* [[Chat log from the meeting on 2015-01-13]]
* [[Chat log from the meeting on 2015-01-06]]

Older chat logs can be found on the [[Chat Logs]] page.

== Saturday - '''Q&A Hour''' ==
'''This meeting is currently not occuring, if you would like to run this meeting please see visit our IRC channel #osgrid on irc.freenode.net''' 
This is meeting tries to drive testing on OpenSimulator. All members of the opensim community are welcome to participate. Through your testing, we create a better project. Also the possibility to get answers of the questions you would have about setting up your own Grid or connect your region to the OSGrid. This meeting is less structured then "Office Hour" and is focused on the users and adopters rather then the developers.

* First, any announcements by OSGrid admins.
* Second, any information to share that helps other grids.
* third, any user or tester subjects that anyone wishes to bring up.

'''This meeting always occurs at 19:00 UTC/GMT (see google calendar below) at Wright Plaza.''' After the one hour is finished, anyone is welcome to continue meeting for as long as they wish.

== Logs ==

* [[Chat log from the meeting on 2016-02-27]]

[[Category:Development]]
[[Category:Office Hours]]

Chat log from the meeting on 2017-04-11

2017-04-13T12:18:07Z

Arielle: Removed duplicated chat log

[10:58] Arielle Popstar: was hoping Ubit might have but not seen him this morning
 [10:59] Sheera.Khan @hypergrid.org:8002: Did you ask Ubit for a new location maybe?
 [10:59] Arielle Popstar: it was talked about but nothing confirmed
 [10:59] Selby.Evans @grid.kitely.com:8002: I don't see Ubit online
 [10:59] Arielle Popstar: he did make it here for the osgrid town meeting
 [11:00] Marcus Llewellyn: I just reminded people on the irc dev channel about the meeting.
 [11:00] Arielle Popstar: irc very chatty lately?
 [11:00] Marcus Llewellyn: Not paricularly.
 [11:04] Andrew Hellershanks: I tried to get someone to fill in for me for the meetings I was fairly certain I would miss but neither person turned up to run them from what I read in the meeting transcripts.
 [11:04] Marcus Llewellyn: We found things to talk about. :)
 [11:05] Selby.Evans @grid.kitely.com:8002: Re: the Testing project, IMA is quite intereste in setting up a working group in cooperation with the Devs
 [11:06] Selby.Evans @grid.kitely.com:8002: The Devs should not have to do their own testing
 [11:06] Andrew Hellershanks: I have done very little OS related stuff in the last month (approximately)
 [11:07] Selby.Evans @grid.kitely.com:8002: Understand
 [11:07] Marcus Llewellyn: Do any IMA member have an IRC presence on Freenode?
 [11:08] Andrew Hellershanks: It is really hard typing things today. I try and fix a typo and it doesn't want to change what I entered. :P
 [11:09] Arielle Popstar: no idea
 [11:09] Andrew Hellershanks: It might just be a form of chat lag.
 [11:09] Marcus Llewellyn: I have a feeling that the IRC channels are the best way to start, and that IMA should reach out with their offer to help test there.
 [11:10] Selby.Evans @grid.kitely.com:8002: I don't know, Marcus
 [11:10] Selby.Evans @grid.kitely.com:8002: I will ask
 [11:10] Arielle Popstar: are Mel and Diva present on irc?
 [11:10] Marcus Llewellyn nods amiably.
 [11:10] Marcus Llewellyn: Yes,
 [11:10] Andrew Hellershanks: If I don't get too many other distractions today I will be the final tests on the changes I made to the OpenSimSearch and OpenSimProfile modules.
 [11:10] Arielle Popstar: Andrew and Ubit are accessable elsewhere
 [11:10] Marcus Llewellyn: They're at least lurking on the dev channel pretty much 24/7
 [11:11] Andrew Hellershanks: Marcus, I'm not in IRC 24/7. If my computer is not sleeping I have it connected to the IRC channel.
 [11:11] Selby.Evans @grid.kitely.com:8002: Asking Steve -- he may be availavble
 [11:12] Marcus Llewellyn: I meant Mel mostly. :)
 [11:12] Arielle Popstar: i think part of the question might be in what way the IMA may be a better testing environment then Osgrid itself
 [11:13] Andrew Hellershanks: Yes, Melanie is connected 24/7 AFAIK. I haven't seen Diva online for a while.
 [11:13] Arielle Popstar: heard she is busy on another project
 [11:13] Marcus Llewellyn: She's there now, but wether she's paying attention at anty given time is always an open question.
 [11:14] Andrew Hellershanks: Arielle: Mel or Diva?
 [11:14] Arielle Popstar: Diva
 [11:14] Andrew Hellershanks: ok
 [11:14] Marcus Llewellyn: Diva has several pots on the stove. ;)
 [11:14] Arielle Popstar: nods
 [11:14] Andrew Hellershanks: hehe... in my case I'd need a bigger stove. :)
 [11:15] Marcus Llewellyn: Hehe. Well, it's just that she's an academic, so there's a lot of baggage with that, as well as other projects she does more commercially.
 [11:15] Andrew Hellershanks nods
 [11:15] Selby.Evans @grid.kitely.com:8002: IMA may not be a better testing environment, but a group could muster more people to do the work
 [11:16] Andrew Hellershanks: Testing is a big job. If it can be split up amongst multiple people it would make it easier on everyone. It just needs the testing to be coordinated.
 [11:16] Arielle Popstar: yes a more organized group effort would expedite the testing of any new stuff
 [11:17] Marcus Llewellyn: Really, what the IMA should consider when trying to create a bridge with OpenSim core devs is that they're the mountain, and Mohammad needs to them. OpenSim and any ancillary projects they have that use it occupy a lot of their time. They can't keep track of every other project out there.
 [11:18] Marcus Llewellyn: That means using their communication and bug reporting tools.
 [11:18] Arielle Popstar: sounds good but how effective has that been in the past 6 months or so?
 [11:18] Selby.Evans @grid.kitely.com:8002: IMA envisions a Working Group to organize testers
 [11:19] Andrew Hellershanks: OpenSim already has a bug tracking system. Are you suggesting using another system for work done in conjunction with the IMA?
 [11:19] Marcus Llewellyn: A working group sounds great! Just so long as they coordinate their efforts with core in a way that'll work,
 [11:20] Marcus Llewellyn: Any working group should make use of OpenSim's mantis tracker.
 [11:20] Andrew Hellershanks: yes
 [11:21] Selby.Evans @grid.kitely.com:8002: Bug tracking is fine, but testing is needed to veryfy cure and sometime to isolate bug
 [11:21] Selby.Evans @grid.kitely.com:8002: as with permissions.
 [11:21] Andrew Hellershanks: Has the IMA set up a working group for testing or is that still a work in progress, or under discussion?
 [11:21] Selby.Evans @grid.kitely.com:8002: Is under discussion.
 [11:22] Marcus Llewellyn waits for the lists complaint. ;)
 [11:22] Selby.Evans @grid.kitely.com:8002: could set it up fast, but need members
 [11:22] Marcus Llewellyn: Does IMA have it's test grid(s) up and running?
 [11:22] Andrew Hellershanks: Selby, it also needs to document the tests being done.
 [11:23] Selby.Evans @grid.kitely.com:8002: IMA hopes to have the test grid up in 2 vweeks
 [11:24] Marcus Llewellyn: I"ve pointed it out before, but the SL wiki has some pretty good test procedures for things like permissions. That'd be a great place to start.
 [11:24] Andrew Hellershanks: The core devs may want to review the test methodology and/or what actual tests are being done to make sure that the tests are valid and to make sure that some important feature/change isn't missed.
 [11:24] Arielle Popstar: looking at Mantis it seems mostly Ubit from the core team doing the majority of comments and fixes
 [11:24] Arielle Popstar: over the past few months
 [11:24] Andrew Hellershanks: Ubit has been the most active commiter to OS in the past few months with some changes from Melanie.
 [11:25] Selby.Evans @grid.kitely.com:8002: The job of the WG is to specify the test procedures and the results reporting.
 [11:25] Marcus Llewellyn: Ubit can be prolific. ;) But a commit isn't *necessarily* his work. He could be adding other people's patches in there as well.
 [11:25] Arielle Popstar: but usually attributes if so?
 [11:26] Marcus Llewellyn: The last patch I submitted was back when we were still on SVN... so I dunno. Hehe.
 [11:26] Andrew Hellershanks: Marcus, true. Sometimes patches come in from other users and Ubit is just the first to be available to commit and push the change.
 [11:26] Selby.Evans @grid.kitely.com:8002: The job of the WG is to satisfy all the stakeholders in their work -- The Devs are major strakeholders
 [11:26] Arielle Popstar: what i am getting at is that perhaps the one to chat with about testing would be Ubit?
 [11:27] Andrew Hellershanks: Ubit or Melanie. Mel is the one who said some of her work is on hold pending perms testing.
 [11:27] Selby.Evans @grid.kitely.com:8002: OH -- that makes sense if he is a major channel -- I have his email -- I will ask him
 [11:28] Marcus Llewellyn: Regardless of which core devs take an interest in the testing, the IRC channel will provide the greatest "surface area" if you will to communicate directly with core members.
 [11:28] Andrew Hellershanks nods
 [11:29] Arielle Popstar: which core devs can make the decision to include ot not include patches?
 [11:29] Marcus Llewellyn: All core devs have a say.
 [11:29] Arielle Popstar: or does that depend on the area of master being affected?
 [11:29] Selby.Evans @grid.kitely.com:8002: I will arrange for us to contact Ubit or Mel
 [11:32] Andrew Hellershanks: Arielle, any core dev can commit and push a patch. One or more other devs may look at the changes and if they have an issue with a commit it will be discussed.
 [11:32] Arielle Popstar: ok
 [11:33] Andrew Hellershanks: The section of code affected by a patch will have some impact on who may comment on it.
 [11:34] Arielle Popstar: these are the current core devs? http://opensimulator.org/wiki/Development_Team
 [11:35] Andrew Hellershanks: That looks up-to-date with the exception of one of the IRC Nicks.
 [11:38] Andrew Hellershanks: Seeing the list of interests column makes me remember I was updating the wiki documentation for the OSSL functions and still need to finish the updates.
 [11:38] Arielle Popstar: bigger stove yet
 [11:38] Andrew Hellershanks: I also haven't finished summarizing the list of changes from the AVN mega code dump.
 [11:40] Arielle Popstar: not sure if this might help
 [11:40] Arielle Popstar: http://binders.world/coding/changelog-2016.html
 [11:40] Arielle Popstar: if i understood you correctly
 [11:43] Andrew Hellershanks: It might help a bit but there was a 3,000 line set of changes in one month. I don't remember when that happened.
 [11:43] Andrew Hellershanks: I was organizing my change summary in to categories.
 [11:44] Andrew Hellershanks: misterblue, you may want to change your IRC nick on the web page at http://opensimulator.org/wiki/Development_Team
 [11:45] Misterblue Waves: does need some updating...
 [11:45] Arielle Popstar: the Avination merge was January 2016 wasnt it?
 [11:46] Andrew Hellershanks: Don't ask me to remember things that far back. :D
 [11:47] Simulator Version v0.5 ruft: OpenSim 0.9.1.0 Dev 1848b1f: 2017-04-06 12:56:00 +0100 (Unix/Mono)
 [11:49] Andrew Hellershanks: I can't tell from that summary page when the big commit hit master. It might depend on how that page summarizes things. The list of changes for the different months don't show the amount of changes that were made because of the big code dump.
 [11:49] Arielle Popstar: November 16 2015 it was announced that it had happened http://opensim-dev.2196679.n2.nabble.com/avination-merged-td7580720.html
 [11:50] Marcus Llewellyn: If I remember right (I may not) the merge started on a branch.
 [11:50] Arielle Popstar: it did
 [11:50] Andrew Hellershanks: I don't see a summary for 2015
 [11:50] Andrew Hellershanks: at that binders.world site
 [11:51] Arielle Popstar: me either
 [11:51] Arielle Popstar: i looked for it before
 [11:51] Arielle Popstar: would be handy
 [11:51] Andrew Hellershanks: oh, well. I'm down to a little under 2,000 lines still to summarize.
 [11:52] Arielle Popstar: oh is that all? ;)
 [11:52] Andrew Hellershanks: It was over 3,000 lines when I first got the file of changes.
 [11:52] Arielle Popstar: big job
 [11:53] Misterblue Waves: it looks like the old branch was 'avinationmerge'... it went into 'master' on Nov 6 '15 (commit f93ce485b1df8c1c8a7ff1a44b280ce30b8707b9)
 [11:53] Marcus Llewellyn: Yay people who get git. :)
 [11:54] Andrew Hellershanks: I have it broken down to 21 categories of changes.
 [11:54] Andrew Hellershanks: Marcus, I can search history but I don't always get it.
 [11:54] Misterblue Waves: there were many... that's a large job, Andrew... it's great that you're doing it
 [11:54] Andrew Hellershanks: Its been on hold for a while with other projects.
 [11:55] Arielle Popstar: i think in the long term it will be important
 [11:55] Misterblue Waves: Other projects get in the way :)
 [11:55] Andrew Hellershanks: I'm sure I will miss some change that might be important, or at least worthy to mention, as the changelog entries are often terse or cryptic (to me).
 [11:55] Misterblue Waves: same for me... I haven't had a lot of time for digging around in OS code
 [11:55] Andrew Hellershanks: I don't always really know what was actually changed based on some of the commit messages.
 [11:56] Andrew Hellershanks: What I find interesting is when I see changes mentioned for things that I thought had not been touched recently or were working features.
 [11:56] Misterblue Waves: if you have the commit number, you can do a 'git show b2592ab132d5ec69a6c04c9051174057e522c0cd" to get the diff of that commit
 [11:57] Marcus Llewellyn: Do what companies like Samsung, Sony, etc do... "Various updates to stability."
 [11:57] Arielle Popstar: lol@Marcus
 [11:57] Andrew Hellershanks: I need to add documentation under Areas of Interest for my listing on the development team page
 [11:58] Andrew Hellershanks: oh, that will be covered by "and many other bug fixes", or something along that line. :)
 [11:58] Marcus Llewellyn: hehe
 [11:58] Andrew Hellershanks: I will be stating upfront it is a list of the more noteworthy changes.
 [11:59] Andrew Hellershanks: There are a lot of changes that affect the code but won't change anything seen by people using the code.
 [11:59] Marcus Llewellyn: Famous last words. :D
 [11:59] Andrew Hellershanks: hehe, yea.
 [11:59] Andrew Hellershanks: well, probably some of those commits where I don't understand the implication of the change from the short changelog entry.
 [12:00] Misterblue Waves: does anyone know what VIrtual Outworlding is up to?
 [12:00] Selby.Evans @grid.kitely.com:8002: I do
 [12:00] Marcus Llewellyn points at Selby.
 [12:00] Andrew Hellershanks: Is that YAG (yet another grid)?
 [12:01] Selby.Evans @grid.kitely.com:8002: Virtual outworlding is a blog
 [12:01] Selby.Evans @grid.kitely.com:8002: my blog
 [12:01] Andrew Hellershanks: oh, ok.
 [12:01] Marcus Llewellyn: And a major supporter of many VW endeavors. Thank you. :)
 [12:01] Andrew Hellershanks: I don't often read blogs
 [12:02] Arielle Popstar: well there is a world to it too isnt there?
 [12:02] Selby.Evans @grid.kitely.com:8002: VO is intended to support VW endeavors
 [12:03] Marcus Llewellyn: Misterblue is the BulletSim Physics wizard. The IMA may want his name on their radar. :)
 [12:04] Arielle Popstar: yes, i agree
 [12:04] Selby.Evans @grid.kitely.com:8002: Arielle -- Is working with a web-world builder to develop web-world for use by nonprofits
 [12:04] Arielle Popstar: https://virtualoutworlding.blogspot.ca/2017/02/2017-edu-oshg-proposal-for-web-world-to.html
 [12:04] Selby.Evans @grid.kitely.com:8002: ty re mister blue
 [12:05] Misterblue Waves: that what I was wondering.... how best to connect with such efforts
 [12:05] Marcus Llewellyn: Check out the IMA, Robert.
 [12:05] Selby.Evans @grid.kitely.com:8002: I passed that suggestion on to ima
 [12:06] Marcus Llewellyn: http://infinitemetaverse.com/
 [12:06] Misterblue Waves: there are so many different web based systems going together at the moment
 [12:06] Misterblue Waves: they are all small... I've been wondering how best to leverage existing OS content and communities
 [12:07] Selby.Evans @grid.kitely.com:8002: The web-based system I am working with is the simplest --WebGL and Javascript
 [12:08] Selby.Evans @grid.kitely.com:8002: Is connected with NonProfit commons in SL
 [12:08] Andrew Hellershanks: hm... I thought the high temperature for today was supposed to be about 12C and it is up to 18C. Nice. Time for a walk after this meeting.
 [12:08] Misterblue Waves: my goal with a web viewer is to have an OS avatar standing next to a High Fidelity avatar :)
 [12:08] Arielle Popstar: (was supposed to be over 20 C)
 [12:09] Arielle Popstar: that would be cool Robert
 [12:09] Selby.Evans @grid.kitely.com:8002: I am reporting on the system on my blog
 [12:09] Andrew Hellershanks: Anything else for today?
 [12:09] Arielle Popstar: I think HF is open to that
 [12:09] Selby.Evans @grid.kitely.com:8002: and am in that world about 10 am pacifictime
 [12:10] Selby.Evans @grid.kitely.com:8002: daily
 [12:10] Selby.Evans @grid.kitely.com:8002: here is link: https://nonprofitvirtualworld.org/location.html?locationid=800000002&dl=true
 [12:10] Andrew Hellershanks: Misterblue: That could make the OS avatars look bad compared to the HF ones.
 [12:12] Misterblue Waves: the tech exists to make browser 3d worlds... the problem I see is community and content
 [12:12] Arielle Popstar: in what way Robert?
 [12:12] Arielle Popstar: security?
 [12:13] Misterblue Waves: we all are here because of the OS community... we could all split up into lots of little grids and worlds and that would dissipate the energy
 [12:14] Misterblue Waves: grids work when there are lots of people
 [12:14] Marcus Llewellyn: A web client is a worthwhile project, but most people's computers/browsers/etc. haven't yet gotten to the point where you can do it as well as a thick client.
 [12:14] Arielle Popstar: i agree Robert but think it is not justy based on the community but also the ones developing
 [12:14] Marcus Llewellyn: Sinewave's Space is a great example. They have a web viewer via Unity, and it works pretty well. But most user opt to download and use the thick client.
 [12:14] Andrew Hellershanks: Grids work best when there are lots of people using them. That's another topic.
 [12:14] Arielle Popstar: they in effect are the leaders
 [12:15] Arielle Popstar: even a hyper grid of worlds can have community if there is ongoing efforts to continue development
 [12:16] Arielle Popstar: seems to me the thick client are still faster and more powerful
 [12:16] Marcus Llewellyn: That will change eventually, but not yet.
 [12:16] Arielle Popstar: whereas the web based are more for tourists then actual inworld building
 [12:17] Andrew Hellershanks: Web based clients can lower the bar on trying out a vw.
 [12:17] Arielle Popstar: yes true Andrew
 [12:17] Marcus Llewellyn: And there's a huge focus on VR for a lot of new entrants in the VW ring. Until VR headsets become more appealing to consumers, that's kinda gonna put a crimp in things like community building.
 [12:18] Misterblue Waves: what VR means in the long run is an open question
 [12:18] Arielle Popstar: yes
 [12:18] Marcus Llewellyn: Very much so.
 [12:18] Arielle Popstar: really depends where the technology goes and how fast
 [12:18] Marcus Llewellyn: There are new entrants to the headset market coming, and they'll be cheaper. But nobody knows how good of an experience they'll provide yet.
 [12:18] Andrew Hellershanks: As long as headsets are somewhat large and bulky VR isn't going to catch on with the mainstream user.
 [12:19] Arielle Popstar: i run lumiya on a $10 headset with bluetooth mouse and its cool
 [12:19] Arielle Popstar: but not for long term
 [12:19] Andrew Hellershanks: $10 headset?
 [12:19] Misterblue Waves: I love Lumiya
 [12:19] Marcus Llewellyn: The Windows Creator update will have support for those new VR headsets, although it's a little buried at the moment. The next update will probably have a major focus on it.
 [12:19] Arielle Popstar: yes she is doing amazing things with it
 [12:20] Marcus Llewellyn: We're talking $200-300 USD from companies like Acer, Dell, and a few others.
 [12:20] Marcus Llewellyn: That's the promise, anyway.
 [12:21] Arielle Popstar: thing is the desktops and laptops are slowing in sales and tablets and phones picking up
 [12:21] Arielle Popstar: people going to want to use those for VR imo
 [12:22] Marcus Llewellyn: Mobile will provide a very different VR experience than one hooked up to a decent computer. It's more suitable for things like tours or VR movies than for VWs.
 [12:22] Misterblue Waves: I tend to think that browser based VWs is good for tablets and mobile while dedicated is good for desktop and headsets (when you need the resolution and speed)
 [12:23] Misterblue Waves: I know there are utility reasons for web based VWs also (ease of installation)
 [12:23] Arielle Popstar: mmm, my new LG 5 does pretty good with Lumiya and opensim
 [12:23] Marcus Llewellyn: So does my old Nexus 9. :) But compared to the full viewer, there's no contest in terms of quality, speed, features, etc.
 [12:23] Misterblue Waves: but keeping the same VW with many different 'connections' to it (dedicated, mobile, chat, ...) is more universally usable
 [12:23] Arielle Popstar: more cores in my phone then in my current laptop
 [12:24] Kayaker Magic: Is Lumiya under active development? Are new features added, new versions come out often?
 [12:24] Arielle Popstar: Yes Andrew
 [12:24] Marcus Llewellyn: Mobile SOC cores are a tricky thing.
 [12:24] Arielle Popstar: best $3 i spent on Google play
 [12:25] Arielle Popstar: oh sorry Kayaker :)
 [12:26] Arielle Popstar: is anyone currently working on a web based Opensim?
 [12:26] Marcus Llewellyn: MOSES still is, as far as I know.
 [12:26] Arielle Popstar: wish they would get HG back in :(
 [12:26] Marcus Llewellyn: Well, guess that's Halcyon based.
 [12:27] Misterblue Waves: yes MOSES (working with inWorldz/Halcyon) is working on a viewer
 [12:27] Arielle Popstar: every fork other then Freakys drops HG
 [12:27] Misterblue Waves: they are defining their own protocol so it's not a general solution
 [12:27] Kayaker Magic: MOSES has changed the protocol for their web based Halcyon viewer, so it will not work with Opensim unless one of our developers adds that protocol
 [12:28] Andrew Hellershanks: They are? That is going to make their work even less compatible with the main OS code base.
 [12:28] Misterblue Waves: I've been playing with building my own that will work with OS, but it requires a lot of content manipulation work with with WebGL
 [12:28] Marcus Llewellyn: I'd assume a new protocol stack would be requisite for a proper web client. I mean, you could shoehorn LLUDP into websockets with effort, but that seems like a wierd way to go.
 [12:28] Andrew Hellershanks nods
 [12:29] Kayaker Magic: Everybody hates the LL viewer protocol, but the TPV people are not interested in changing that.
 [12:30] Misterblue Waves: I was going to build a converter that talks LLLP (Linden Lab Legacy Protocol) on one side and an optimized protocol on the other -- need a different asset representation as well as better LOD support
 [12:30] Andrew Hellershanks: It needs cooperation between the viewer end and the back end code.
 [12:30] Arielle Popstar: at least on the LL they have a community of people that will use it
 [12:30] Marcus Llewellyn: That's because 99.9% of te TPV devs aren't protocol level people. Their projects are highly dependent on upstream code from LL>
 [12:30] Kayaker Magic: Only MOSES had an opportunity to break away. with their own viewer.
 [12:31] Marcus Llewellyn: I've always been of the opinion that as long as OpenSim doesn't have it's own viewer, in whatever form, it's only half a project.
 [12:32] Arielle Popstar: hmm i would hate to see Opensim down to having only one choice for viewer
 [12:32] Andrew Hellershanks: There is talk of an OS specific viewer but that would still be down the road aways.
 [12:32] Marcus Llewellyn: Yes, I've heard.... rumbles. ;)
 [12:33] Misterblue Waves: who's doing the rumbles, Marcus?
 [12:33] Arielle Popstar: if there was to be a seperate ops viewer then i would hope because there would be more inworld building tools
 [12:33] Andrew Hellershanks: Wonderful. Now the temp has dropped 2 degrees and I see it saying its raining.
 [12:33] Arielle Popstar: keep it where you are Andrew
 [12:33] Arielle Popstar: I have outside chores to do yet
 [12:34] Marcus Llewellyn: I won't say, cuz the person doing the rumbling has been very non-commital and secretive. Sooo... I'd just be sharing vapor right now.
 [12:34] Andrew Hellershanks: Areille, I don't want it where I am.
 [12:34] Arielle Popstar: vapor ware
 [12:34] Andrew Hellershanks nods
 [12:35] Marcus Llewellyn: Hopefully not. Doesn't hurt to keep an eye open. :)
 [12:35] Arielle Popstar: true
 [12:35] Andrew Hellershanks: yea, one never knows.
 [12:35] Arielle Popstar: doing anymore on Bullet Robert?
 [12:35] Misterblue Waves: haven't done anything in a while
 [12:36] Andrew Hellershanks: If the person(s) wanting to do an OS specific viewer can also get some financial support that can help encourage them to work on it if they otherwise need to get other paid work that might prevent them from working on a viewer.
 [12:37] Misterblue Waves: if I was to get back into it, I'd want to rearchitect is so it handles linksets and dynamics better while also simplifying the interface between the C# and C++ code
 [12:37] Arielle Popstar: big project?
 [12:37] Andrew Hellershanks: I've been thinking of setting up a Patreon account to see if I could get a few $'s to help pay the bills based on all the Open Source projects I work on and support.
 [12:37] Misterblue Waves: keeping backward compatibilty for all the OS simulator modules is holding back adding new features
 [12:37] Marcus Llewellyn: Justin used to accept donations. I forget which service he used.
 [12:38] Andrew Hellershanks: Misterblue, back when I last looked at some of the code re: linksets I saw the potential for some optimization.
 [12:38] Misterblue Waves: there have been several efforts to fund work... I don't remember all the details, though
 [12:38] Marcus Llewellyn: Hierarchical linksets! :D
 [12:38] Arielle Popstar: IMA is looking to do that
 [12:39] Arielle Popstar: might be worth checking out
 [12:39] Andrew Hellershanks: I'm involved in 2 major Open Source projects and help support them via IRC channels along with helping run a grid and supporting others.
 [12:39] Misterblue Waves: the interface for linksets between the simulator and the physics engine needs to be changed (like was done in Aurora) where the linkset is defined all at once rather than individual prim link calls.... that makes object state hard to manage
 [12:39] Misterblue Waves: the definition of linksets is simple for content creators but difficult for implementation
 [12:40] Andrew Hellershanks: Misterblue, I noticed a lot of linking and unlinking that seemed a waste when dealing with manipulating link sets. it was done on a per prim basis.
 [12:40] Andrew Hellershanks: Linking two sets of prims should just be little more than adding one linkset to the end of other other and updating a few link numbers for the prims.
 [12:40] Andrew Hellershanks: and probably position/rotation data for the new child prims.
 [12:41] Arielle Popstar: Robert, IMA is open to doing testing etc if you did decide to go further on that
 [12:41] Misterblue Waves: exactly Andrew... linksets should have a link/delink interface for the content creator but should be whole object to the simulator internals
 [12:41] Andrew Hellershanks: It should not need to delink a prim and add the prim one at a time.
 [12:41] Andrew Hellershanks: Misterblue, that stuff is buried in the SOP/SOG code.
 [12:41] Marcus Llewellyn: As a user, that process is a noticable one at times.
 [12:42] Andrew Hellershanks: Marcus, I also notice it at times as a builder.
 [12:42] Misterblue Waves would love to rewrite a lot of OS internals... but that's close to starting over :)
 [12:42] Arielle Popstar: ;)\
 [12:42] Marcus Llewellyn: BlueSim! >:D
 [12:43] Arielle Popstar: Hehe
 [12:43] Andrew Hellershanks: The linking code is a smaller set of changes isolated to a few files.
 [12:43] Andrew Hellershanks: Misterblue, sounds like one more pot for your stove. :)
 [12:43] Misterblue Waves: and my wife would like to see me sometimes :)
 [12:44] Andrew Hellershanks: :)
 [12:44] Arielle Popstar: a couple people are actually in process of redoing everything but as a solo project that would be a huge undertaking
 [12:44] Andrew Hellershanks: Sit on the couch beside her while you are coding and she can see you. ;)
 [12:44] Arielle Popstar: present but not quite present
 [12:45] Marcus Llewellyn: She can visit you inworld. ;)
 [12:45] Arielle Popstar: meet you inworld
 [12:45] Misterblue Waves: I'm sure that would go over well ;-)
 [12:45] Marcus Llewellyn: teehee
 [12:45] Andrew Hellershanks: hehe
 [12:46] Arielle Popstar: anyway interesting discussion
 [12:47] Arielle Popstar: glad it went in overtime because i think there was some good info put out
 [12:47] Marcus Llewellyn: Best to you and your family, Andrew.

[[Category:Office Hour Logs]]

Server Commands

2014-01-19T20:01:45Z

Arielle: /* Simulator Commands */

{{Quicklinks}}

= What are server commands? =

Server commands are those you can type on the console to make the server do various things.

Commands can be divided up into those that apply to the simulator (simulator commands) and those that apply to grid services (service commands).

On a standalone system, both simulator and service commands will be available on the single standalone system console.

On a grid architecture, the simulator commands will be available on the simulators, whilst the service commands will be available on the ROBUST console.

'''Disclaimer''': some commands may not work as expected, some may not work at all, and there is a chance that you may even lose all your settings/contents. This summary quickly goes out of date - the best place to find commands is by typing "help" on the region console.

Except where noted, this list should be accurate for OpenSimulator 0.7.1 onwards.

= Commands =

== General Server Commands ==

These commands are available in both simulator and robust consoles.

=== General ===

* command-script [scriptfile] - Runs a command script containing console commands.
* quit - shutdown the server.
* show info - show server information (version and startup path). Before OpenSimulator 0.7.5 this is only available on the simulator console.
* show uptime - show server startup time and uptime. Before OpenSimulator 0.7.5 this is only available on the simulator console.
* show version - show server version. Before OpenSimulator 0.7.5 this is only available on the simulator console.
* shutdown - synonym for quit
* get log level - In OpenSimulator 0.7.5 and later, print the current console logging level. In OpenSimulator 0.7.4 and earlier please use the "set log level" command instead without a level parameter.
* set log level [level] - change the console logging level only. For example, off or debug. See [[Logging]] for more information. In OpenSimulator 0.7.4 and earlier, if called without the level argument prints the current level. In OpenSimulator 0.7.5 and later please use the "get log level" command instead. Only available on ROBUST console from OpenSimulator 0.7.5.

=== Debug ===

* debug http [<level>] - Turn on/off extra logging for HTTP request debugging. Only available on robust console from commit 94517c8 (dev code post 0.7.3.1). In current development code (for OpenSimulator 0.7.5) this is debug http in|out|all [<level>] since outbound HTTP messages can also now be logged (this was only possible for inbound before).

== Simulator Commands ==

=== General ===

* change region <region name> - subsequent commands apply only to the specified region. If region name is "root" then all regions are selected
* create region [name] [filename] - Create a new region
* debug packet <level> - Turn on packet debugging, where OpenSimulator prints out summaries of incoming and outgoing packets for viewers, depending on the level set
* debug scene - Turn on scene debugging
* delete-region <name> - Delete a region from disk
* emergency-monitoring - turn emergency debugging monitoring mode on or off.
* export-map [<path>] - Save an image of the world map (default name is exportmap.jpg)
* help [<command>] - Get general command list or more detailed help on a specific command or set of commands
* link-mapping - Set a local grid co-ordinate to link to a remote hypergrid
* link-region - Link a HyperGrid region. Not sure how this differs from link-mapping
* modules list - List modules
* modules load <name> - Load a module
* modules unload <name> - Unload a module
* monitor report - Returns a variety of statistics about the current region and/or simulator
* region restart abort [<message>] - Abort a scheduled region restart, with an optional message
* region restart bluebox <message> <delta seconds>+ - Schedule a region restart. If one delta is given then the region is restarted in delta seconds time. A time to restart is sent to users in the region as a dismissable bluebox notice. If multiple deltas are given then a notice is sent when we reach each delta.
* region restart notice <message> <delta seconds>+ - Schedule a region restart. Same as above except showing a transient notice instead of a dismissable bluebox.
* reload estate - reload estate data
* remove-region - remove a region from the simulator
* restart - Restarts all sims in this instance
* set region flags <Region name> <flags> - Set database flags for region
* set terrain heights <corner> <min> <max> [<x>] [<y>] - Sets the terrain texture heights on corner #<corner> to <min>/<max>, if <x> or <y> are specified, it will only set it on regions with a matching coordinate. Specify -1 in <x> or <y> to wildcard that coordinate. Corner # SW = 0, NW = 1, SE = 2, NE = 3.
* set terrain texture <number> <uuid> [<x>] [<y>] - Sets the terrain <number> to <uuid>, if <x> or <y> are specified, it will only set it on regions with a matching coordinate. Specify -1 in <x> or <y> to wildcard that coordinate.
* show caps - show all registered capabilities URLs
:NOTE: In OpenSimulator 0.7.1, "show capabilities" is shown as a result for help command, but actually only "show caps" will be accepted. ([http://opensimulator.org/mantis/view.php?id=5467 #5467])
* show circuits - Show agent circuit data
* show connections - show connections data
* show http-handlers - show all registered http handlers
* show hyperlinks - list hg regions
* show modules - show module data
* show neighbours - Shows the local regions' neighbours
* show pending-objects - show number of objects in the pending queues of all viewers
* show pqueues [full] - show priority queue data for each client. Without the 'full' option, only root agents are shown. With the 'full' option child agents are also shown.
* show queues - Show queue data for agent connections.
* show ratings - Show rating data
* show region [region name] - Show region data (Region Name, Region UUID, Location, URI, Owner ID, Flags)
* show regions - Show regions data (Region Names, XLocation YLocation coordinates, Region Ports, Estate Names)
* show stats - show usefull statistical information for this server. See [[#Frame Statistics Values|Frame Statistics Values]] below for more information.
* show threads - shows the persistent threads registered with the system. Does not include threadpool threads.
* show throttles [full] - Show throttle data for each client connection, and the maximum allowed for each connection by the server. Without the 'full' option, only root agents are shown. With the 'full' option child agents are also shown.
* unlink-region <local name> - unlink a hypergrid region

=== Appearance Commands ===

* appearance show - Show information about avatar appearance. Currently just checks whether the baked texture is "OK" or "corrupt". Still in development. Only exists in development code at the moment.

=== Archive Commands ===

* load iar <first> <last> <inventory path> <password> [<archive path>] - Load user inventory archive. See [[Inventory Archives]].
* load oar [filename] - load an OpenSimulator archive. This entirely replaces the current region. Default filename is '''region.oar'''. See [[OpenSim Archives]].
* load xml [-newIDs [<x> <y> <z>]] - Load a region's data from XML format (0.7.*: DEPRECATED and may be REMOVED soon. Use "load xml2" instead)
:those xml are the result of the export save or *export save-all
* load xml2 [filename] - optional parameters not supported for XML2 format as at 1-Jul-2008
* save iar <first> <last> <inventory path> <password> [<archive path>] - Save user inventory archive. See [[Inventory Archives]]
* save oar [filename] - save the current region to an OpenSimulator archive. Default filename is '''region.oar'''. See [[OpenSim Archives]].
* save prims xml2 [<prim name> <file name>] - Save named prim to XML2
* save xml [filename] - save prims to XML
* save xml2 [filename] - save prims to XML (Format 2 - rearrangement of some nodes, to make loading/saving easier)

=== Asset Commands ===

The fcache commands only currently appearance if you are using the fcache asset cache. This is the default on OpenSimulator.

* fcache assets - Attempt a deep scan and cache of all assets in all scenes
* fcache clear [file] [memory] - Remove all assets in the cache. If file or memory is specified then only this cache is cleared.
* fcache expire <datetime> - Purge cached assets older then the specified date/time
* fcache status - Display cache status
* j2k decode <ID> - Do JPEG2000 decoding of an asset.

=== Config Commands ===

* config get [<section>] [<key>] - Get the current configuration, either for a particular key, a particular section or the whole config.
* config save <path> - Save the current configuration to a file.
* config set <section> <key> - Set a particular configuration value. On the whole, this is useless since neither OpenSimulator nor modules dynamically reload config values.
* config show [<section>] [<key>] - Synonym for 'config get'

=== Land Commands ===

* land show - Shows all parcels on the current region.

=== Object Commands ===

* backup - Persist currently unsaved object changes immediately instead of waiting for the normal persistence call. This shouldn't normally be required - the simulator persists region objects automatically at regular intervals and on shutdown.
* delete object creator <UUID> - Delete a scene object by creator
* delete object name [--regex] <name> - Delete a scene object by name.
* delete object outside - Delete all scene objects outside region boundaries. This is currently if z < 0 or z > 10000. Object outside these bounds have been known to cause issues with OpenSimulator's use of some physics engines (such as the Open Dynamics Engine).
* delete object owner <UUID> - Delete a scene object by owner
* delete object uuid <UUID> - Delete a scene object by uuid. In current dev code (post 0.7.5) this is "show object id" and also allows a local ID.
* dump object id <UUID-or-localID> - Dump the serialization of the given object to a file for debug purposes.
* edit scale <name> <x> <y> <z> - Change the scale of a named prim
* force update - Force the region to send all clients updates about all objects.
* show object name [--regex] <name> - Show details of scene objects with the given name.
* show object uuid <UUID> - Show details of a scene object with the given UUID. In current dev code (post 0.7.5) this is "show object id" and also allows a local ID.
* show part name [--regex] <name> - Show details of scene object parts with the given name.
* show part uuid <UUID> - Show details of a scene object parts with the given UUID. In current dev code (post 0.7.5) this is "show object id" and also allows a local ID.

=== Scene Commands ===

*rotate scene <degrees> - Rotates scene around 128,128 axis by x degrees where x=0-360.
*scale scene <factor> - Scales all scene objects by a factor where original size =1.0.
*translate scene <x,y,z> - Translate (move) the entire scene to a new coordinate. Useful for moving a scene to a different location on either a Mega or Variable region.
(please back up your region before using any of these commands and be aware of possible floating point errors the more they are used.)

=== Script Commands ===

These currently only exist in git master OpenSimulator development code post the 0.7.2 release.

* scripts resume [<script-item-uuid>] - Resumes all suspended scripts
* scripts show [<script-item-uuid>] - Show script information. <script-item-uuid> option only exists from git master 82f0e19 (2012-01-14) onwards (post OpenSimulator 0.7.2).
* scripts start [<script-item-uuid>] - Starts all stopped scripts
* scripts stop [<script-item-uuid>] - Stops all running scripts
* scripts suspend [<script-item-uuid>] - Suspends all running scripts

=== Terrain Commands ===

Note that some of these may require a sim restart to show properly.
* terrain load - Loads a terrain from a specified file.
* terrain load-tile - Loads a terrain from a section of a larger file.
* terrain save - Saves the current heightmap to a specified file.
* terrain fill - Fills the current heightmap with a specified value.
* terrain elevate - Raises the current heightmap by the specified amount.
* terrain lower - Lowers the current heightmap by the specified amount.
* terrain multiply - Multiplies the heightmap by the value specified.
* terrain bake - Saves the current terrain into the regions revert map.
* terrain revert - Loads the revert map terrain into the regions heightmap.
* terrain newbrushes - Enables experimental brushes which replace the standard terrain brushes. WARNING: This is a debug setting and may be removed at any time.
* terrain stats - Shows some information about the regions heightmap for debugging purposes.
* terrain effect - Runs a specified plugin effect

=== Tree Commands ===

* tree active - Change activity state for the trees module
* tree freeze - Freeze/Unfreeze activity for a defined copse
* tree load - Load a copse definition from an xml file
* tree plant - Start the planting on a copse
* tree rate - Reset the tree update rate (mSec)
* tree reload - Reload copse definitions from the in-scene trees
* tree remove - Remove a copse definition and all its in-scene trees
* tree statistics - Log statistics about the trees

=== User Commands ===

* alert <message> - send an in-world alert to everyone
* alert-user <first> <last> <message> - send an an in-world alert to a specific user
* bypass permissions <true / false> - Bypass in-world permission checks
* debug permissions - Turn on permissions debugging
* force permissions - Force permissions on or off.
* kick user <first> <last> [message]: - Kick a user off the simulator
* login disable - Disable user entry to this simulator
* login enable - Enable user entry to this simulator
* login status - Show whether logins to this simulator are enabled or disabled
* show users [full]- show info about currently connected users to this region. Without the 'full' option, only users actually on the region are shown. With the 'full' option child agents of users in neighbouring regions are also shown.
* teleport user <destination> - Teleport a user on this simulator to a specific destination. Currently only in OpenSimulator development code after the 0.7.3.1 release (commit bf0b817).

=== Windlight/[[LightShare]] Commands ===

* windlight load - Load windlight profile from the database and broadcast
* windlight enable - Enable the windlight plugin
* windlight disable - Enable the windlight plugin

== ROBUST Service Commands ==

These can also be accessed on the simulator command console itself in standalone mode.

=== Asset Service ===

* delete asset - Delete an asset from the database. Doesn't appear to be implemented.
* dump asset <ID> - Dump an asset to the filesystem. OpenSimulator 0.7.3 onwards.
* show digest <ID> - Show summary information about an asset. From OpenSimulator 0.7.3 onwards this will be renamed to "show asset"

=== Grid Service ===

* set region flags <Region name> <flags> - Set database flags for region
* show region <Region name> - Show the details of a given region. This command is renamed to "show region name" in development versions of OpenSimulator.

The following commands currently only exist in development versions of OpenSimulator (post 0.7.3.1). These are currently found in the "Regions" help section.

* deregister region id <Region UUID> - Deregister a region manually. This can be helpful if a region was not properly removed due to bad simulator shutdown and the simulator has not since been restarted or its region configuration has been changed.
* show region at <x-coord> <y-coord> - Show details on a region at the given co-ordinate.
* show region name <Region name> - Show details on a region
* show regions - Show details on all regions. In standalone mode this version of the command is not currently available - the simulator version of "show regions" is used instead, which shows similar information.

=== User Service ===
* create user [first] [last] [passw] [RegionX] [RegionY] [Email] - creates a new user and password
:or just: create user - and server prompts for all data
:
:'''Note for use of create user in standalone mode:''' use the user default coordinates
:of 1000,1000 for Start Region X and Y position otherwise server
:gives error of "[LOGIN]: Not found region"

* reset user password - reset a user's password.
* show account <firstname> <lastname> - show account details for the given user name (0.7.2-dev)

=== Login Service ===
* login level <value> - Set the miminim userlevel allowed to login.
* login reset - reset the login level to its default value.
* login text <text to print during the login>
* set user level <firstname> <lastname> <level> - Set UserLevel for the user, which determines whether a user has a god account or can login at all (0.7.2-dev)

== Details of Terrain Module Commands ==

==== terrain load ====
Loads a terrain from a specified file.

Parameters
* filename (String)
The file you wish to load from, the file extension determines the loader to be used. Supported extensions include: .r32 (RAW32) .f32 (RAW32) .ter (Terragen) .raw (LL/SL RAW) .jpg (JPEG) .jpeg (JPEG) .bmp (BMP) .png (PNG) .gif (GIF) .tif (TIFF) .tiff (TIFF)

==== terrain load-tile ====
Loads a terrain from a section of a larger file.

Parameters
* filename (String)
The file you wish to load from, the file extension determines the loader to be used. Supported extensions include: .r32 (RAW32) .f32 (RAW32) .ter (Terragen) .raw (LL/SL RAW) .jpg (JPEG) .jpeg (JPEG) .bmp (BMP) .png (PNG) .gif (GIF) .tif (TIFF) .tiff (TIFF)
* file width (Integer)
The width of the file in tiles
* file height (Integer)
The height of the file in tiles
* minimum X tile (Integer)
The X region coordinate of the first section on the file
* minimum Y tile (Integer)
The Y region coordinate of the first section on the file

==== terrain save ====
Saves the current heightmap to a specified file.

Parameters
* filename (String)
The destination filename for your heightmap, the file extension determines the format to save in. Supported extensions include: .r32 (RAW32) .f32 (RAW32) .ter (Terragen) .raw (LL/SL RAW) .jpg (JPEG) .jpeg (JPEG) .bmp (BMP) .png (PNG) .gif (GIF) .tif (TIFF) .tiff (TIFF)

==== terrain fill ====
Fills the current heightmap with a specified value.

Parameters
* value (Double)
The numeric value of the height you wish to set your region to.

==== terrain elevate ====
Raises the current heightmap by the specified amount.

Parameters
* amount (Double)

==== terrain lower ====
Lowers the current heightmap by the specified amount.

Parameters
* amount (Double)
The amount of height to remove from the terrain in meters.

==== terrain multiply ====
Multiplies the heightmap by the value specified.

Parameters
* value (Double)
The value to multiply the heightmap by.

==== terrain bake ====
Saves the current terrain into the regions revert map.

==== terrain revert ====
Loads the revert map terrain into the regions heightmap.

==== terrain newbrushes ====
Enables experimental brushes which replace the standard terrain brushes. WARNING: This is a debug setting and may be removed at any time.

Parameters
* Enabled? (Boolean)
true / false - Enable new brushes

==== terrain stats ====
Shows some information about the regions heightmap for debugging purposes.

==== terrain effect ====
Runs a specified plugin effect

Parameters
* name (String)
The plugin effect you wish to run, or 'list' to see all plugins

== Details of Hypergrid Commands ==

For full details and explanations of Hypergrid Commands, see the [http://opensimulator.org/wiki/Installing_and_Running_Hypergrid#Linking_regions_.28Optional.29 Linking Regions] sections of the [http://opensimulator.org/wiki/Installing_and_Running_Hypergrid Installing and Running Hypergrid] page.

'''show hyperlinks'''

This command will show a list of all hypergrid linked regions.

'''link-region <Xloc> <Yloc> <host> <port> <location-name>'''

* Use Xloc and Yloc that make sense to your world, i.e. close to your regions, but not adjacent.
* replace osl2.nac.uci.edu and 9006 with the domain name / ip address and the port of the region you want to link to

E.g. link-region 8998 8998 osl2.nac.uci.edu 9006 OSGrid Gateway

'''unlink-region <local region name>'''

This command will unlink the specified hypergrid linked region - be sure to use the exact local name as reported by the "show hyperlinks" command.

'''Important Note'''

Due to a viewer [https://jira.secondlife.com/browse/SVC-2941 bug], you can only TP between regions that are no more than 4096 cells apart in any dimension. What this means in practice is that if you want to link to OSGrid, you must have your own regions reachable from the (10,000; 10,000) point on the map, which is where OSGrid is centered. Place your regions somewhere in the 8,000s or the 12,000s.

link-mapping
== Frame Statistics Values ==

The labels of the Frame Statistics values shown by the console command "show stats" are a bit cryptic. Here is a list of the meanings of these values:

* Dilatn - time dilation
* SimFPS - sim FPS
* PhyFPS - physics FPS
* AgntUp - # of agent updates
* RootAg - # of root agents
* ChldAg - # of child agents
* Prims - # of total prims
* AtvPrm - # of active prims
* AtvScr - # of active scripts
* ScrLPS - # of script lines per second
* PktsIn - # of in packets per second
* PktOut - # of out packets per second
* PendDl - # of pending downloads
* PendUl - # of pending uploads
* UnackB - # of unacknowledged bytes
* TotlFt - total frame time
* NetFt - net frame time
* PhysFt - physics frame time
* OthrFt - other frame time
* AgntFt - agent frame time
* ImgsFt - image frame time

[[Category:Support]]
[[Category:Help]]
[[Category:Configuration]]
[[Category:Getting Started]]
[[Category:Development]]

Mesh

2013-09-03T12:14:16Z

Arielle: /* Phantom mesh */

{{quicklinks}}
{{content}}
== Introduction ==
OpenSimulator supports the use of collada meshes. It must be noted that at the time of this writing, mesh support is still under development at Linden Labs, and they make changes to that all the time. Therefore, we can not guarantee that the current implementation of mesh support in OpenSimulator will be 100% compatible to the final version on SecondLife, once that gets rolled out. If you plan on using OpenSimulator to develop meshes for SecondLife, make sure you update Opensim frequently.

== Enabling mesh support ==
To make sure that your OpenSimulator server has mesh support enabled, edit OpenSim.ini, and look for the lines that should read:
[Mesh]
; enable / disable Collada mesh support
; default is true
AllowMeshUpload = true
If you do not have that section in Opensim.ini, then you can safely add it yourself.

== Free Software to make meshes with ==
==== Windows ====
* [http://www.wings3d.com/ Wings3D]
* [http://www.blender.org/ Blender]

==== MacOS ====
* [http://www.wings3d.com/ Wings3D]
* [http://www.blender.org/ Blender]

==== Linux ====
* [http://www.wings3d.com/ Wings3D]
* [http://www.blender.org/ Blender]

== Viewers with Mesh support ==
* [http://wiki.secondlife.com/wiki/Linden_Lab_Official:Alternate_Viewers#Second_Life_Project_Viewers LL Project Viewer] - An experimental mesh supporting viewer by Linden Labs
* [http://www.kirstensviewer.com/ Kirsten's Viewer] - A v2 based viewer with heavy emphasis on nice graphics.
* [http://www.singularityviewer.org/ Singularity] - A V1 based viewer, with the good stuff from v2 added. Supports mesh, [[OSSL]], and more.
* [http://sldev.free.fr/ Cool VL Viewer] - one of the oldest Third Party Viewers around (former name: Cool SL Viewer), fully OpenSimulator compatible.
* [http://www.phoenixviewer.com/ Firestorm Viewer] - A V2 based viewer,Supports mesh viewing and uploading, grid menu for Opensim, also Pheonix Viewer - V1 viewer with mesh view and upload, grid Manager.

'''Working on including Mesh support'''
* [http://blog.kokuaviewer.org/ Imprudence and Kokua] - Imprudence is v1 based, Kokua is v2 based. Both are develped by the same team.

== Other Meshes ==

You may not realize it, but sculpties too are meshes. One important difference with sculpties on Secondlife, is that in OpenSim, you can completely disable the bounding box (the invisible wall that you bump into, when you have a large sculptie). This will allow you to make working sculptie stars, without having to use tricks like invisible prims. By default, this feature is turned on, so no need to worry about that.
However, should you find that you keep running into bounding boxes anyway, you may want to edit OpenSim.ini, and look for the following lines:

[ODEPhysicsSettings]
;# {mesh_sculpted_prim} {[Startup]physics:OpenDynamicsEngine} {Mesh sculpties so they
collide as they look?} {true false} true
;; Do we want to mesh sculpted prim to collide like they look?
;; If you are seeing sculpt texture decode problems
;; (messages such as "Decoded image with unhandled number of components: 0 shortly followed by a physcs exception")
;; then you might want to try setting this to false.
; mesh_sculpted_prim = true
The current default for this is "true".

Since in OpenSimulator, prim size is set to a maximum of 256 meters by default, it can be worthwhile to use sculpties instead of collada mesh, especially if the mesh you need is a relatively simple one.

== Troubleshooting ==
=== Phantom mesh ===
As of begin of February 2013, when uploading a mesh, do not use steps 2 and 3 in the "physics" tab of the mesh upload panel because it is breaking physics so if using them, your object will be as phantom and you will see a "[MESH]: No recognized physics mesh found in mesh asset....." in the simulator console.

source : https://lists.berlios.de/pipermail/opensim-users/2013-February/011702.html

NAT Loopback Routers

2013-08-26T14:37:08Z

Arielle: /* Windows XP, Win7 Loopback Adapter Install: */

{{Quicklinks}} {{content}}

= INTRODUCTION =

What is NAT Loopback and why is it needed to host a public Opensimulator Region?

Currently (as at August 2010), a hosted region on a home connection with a broadband router needs, what is known as ''NAT Loopback'' functionality.

Many DSL routers/modems prevent loopback connections as a security feature. This means that a machine on your local network (e.g. behind your DSL router/modem) cannot connect to a forward facing IP address (such as 199.149.252.44) of a machine that it also on your local network. Connecting to the local IP address (such as 192.168.2.40) of that same machine works fine.

This is an issue since each region has to specify an IP address for the client to connect. This is the ExternalHostName parameter in a regions config file (e.g. bin/Regions/Regions.ini). In the absence of NAT loopback, if a forward facing IP address is specified (such as 199.149.252.44) then external clients will be able to connect to the region but clients on your local network will not. If the internal address were put in ExternalHostName instead (e.g. 192.168.2.40) then viewers on the local network will be able to connect but viewers from an external network would not.

This page shows a list of routers supporting NAT Loopback. Please add both known working and non-working routers to the list.

= Router/Modem Table =
==== Router / Modem Table ====
(this information gathered from the OpenSimulator WIKI and OSGrid forums information collectively and assembled into this sortable formatted table for ease of use and quick access. Links provided are either to the Manufactures pages or Pages which can further assit in configuration and troubleshooting.)

{| cellspacing="0" cellpadding="5" border="1" align="centre" class="sortable"
|-
| '''Make''' || '''Model''' || '''Status''' || '''Notes'''
|-
| Actiontec || [http://www.actiontec.com/support/product_details.php?pid=71 GT701-WG] || Works || [http://portforward.com/english/routers/port_forwarding/Actiontec/GT701WG/default.htm]
|-
| Actiontec || [http://www.actiontec.com/products/product.php?pid=189 Verizon FiOS Router Model # 424WR] || Works || [http://www.actiontec.com/support/product_details.php?pid=189#q23] Set TCP and UDP separately
|-
| Airlink || Airlink 101 Super G || Works || older model, search for reference
|-
| Airlink || Airlink 101 802.11G wireless || Works || older model, search for reference
|-
| Apple || [http://www.apple.com/airportextreme/ AirPort Extreme] || Works ||
|-
| Arris || TM502b || Works || [http://portforward.com/english/routers/port_forwarding/Arris/TM502b/]
|-
| Astoria Networks || Bright Box Wireless Router || Not Working || |
|-
| Asus || [http://www.asus.com/Networks/Wireless_Routers/WL520gC/ WL-520GC] || Works || [http://portforward.com/english/routers/port_forwarding/Asus/WL-520GC/defaultguide.htm]
|-
| AVM || FRITZ!Box || Works || [http://www.avm.de/en/Produkte/FRITZBox/index.html] Except 3790 VDSL Router (old stock)
|-
| Belgacom BBox-2 || [http://support.en.belgacom.be/app/answers/detail/a_id/14453/~/how-to-install-and-manage-my-wireless-modem%3F BBox-2 Docs] || Works || Also known as [http://www.sagemcom.com/index.php?id=1226&L=0 SAGEM 3464]. BBox-1 work, BBox-2 = Method 1: flash the firmare (in this case we lose the guarantee provider) Method 2: Configure Bbox Bridge mode and put a second router for OpenSim-Sim.
|-
| BT || BT Home Hub V2 || Works || [http://portforward.com/english/routers/port_forwarding/BT/BT_Home_Hub_v2/defaultguide.htm]
|-
| BT || BT Home Hub 3 (model B) || Works || [Tested using firmware V100R001C01B031SP12_L_B on standalone ]
|-
| BT || BT2700HGV || Works || [ http://portforward.com/english/routers/port_forwarding/BT/BT2700HGV/defaultguide.htm]
|-
| Cisco || [http://www.cisco.com/en/US/products/ps9925/index.html RV042] || Works ||
|-
| Dlink || [http://www.dlink.com/products/?pid=DGL-4500 DGL-4500] || Works || [http://portforward.com/english/routers/port_forwarding/Dlink/DGL-4500/defaultguide.htm]
|-
| Dlink || [http://www.dlink.com/products/?pid=370 DGL-4300] || Works || [http://portforward.com/english/routers/port_forwarding/Dlink/DGL-4300/defaultguide.htm]
|-
| Dlink || [http://www.dlink.ca/products/?tab=3&pid=DI-524&rev=DI-524 DI-524] || Works || [http://portforward.com/english/routers/port_forwarding/Dlink/DI-524/defaultguide.htm]
|-
| Dlink || [http://www.dlink.com/products/?pid=DIR-600 DIR-600] || Works || [http://portforward.com/english/routers/port_forwarding/Dlink/DIR-600/defaultguide.htm]
|-
| Dlink || [http://www.dlink.com/products/?pid=DIR-601 DIR-601] || Works || [http://portforward.com/english/routers/port_forwarding/Dlink/DIR-601/defaultguide.htm]
|-
| Dlink || [http://www.dlink.com/products/?pid=DIR-635 DIR-635] || Works || [http://portforward.com/english/routers/port_forwarding/Dlink/DIR-635/defaultguide.htm]
|-
| Dlink || [http://www.dlink.com/products/?pid=DIR-655 DIR-655] || Works || [http://portforward.com/english/routers/port_forwarding/Dlink/DIR-655/defaultguide.htm] Current hardware version "B" doesn't work.
|-
| Dlink || [http://www.dlink.com/uk/en/home-solutions/connect/modems-and-gateways/dsl-2680-wireless-n-150-adsl2--home-router DSL-2680] || Not Working ||
|-
| Draytek || [http://www.draytek.com/user/PdInfoDetail.php?Id=71 Vigor120] || Works || Nat Loopback out of the box. Great router.
|-
| Draytek || [http://www.draytek.com/user/PdInfoDetail.php?Id=82 Vigor2710] || Works || [http://portforward.com/english/routers/port_forwarding/DrayTek/Vigor_2710n/defaultguide.htm] firmware 3.2.4.3 (or higher).
|-
| Inventel / Livebox || DV42190WA || Works || Sold as Livebox 3420 by Orange/SFR in Europe. Set port forwarding for UDP and TCP separately
|-
| Linksys/Cisco || [http://homesupport.cisco.com/en-us/wireless/lbc/BEFSR41/ BEFSR41] || Works || [http://portforward.com/english/routers/port_forwarding/Linksys/BEFSR41/defaultguide.htm]
|-
| Linksys/Cisco || RT31P2 || Works || [http://portforward.com/english/routers/port_forwarding/Linksys/RT31P2/defaultguide.htm]
|-
| Linksys/Cisco || [http://www.linksysbycisco.com/APAC/en/support/AG241 AG241] || Works || [http://portforward.com/english/routers/port_forwarding/Linksys/AG241/defaultguide.htm]
|-
| Linksys/Cisco || [http://www.linksysbycisco.com/EU/en/support/WAG200G WAG200G] || Works || [http://portforward.com/english/routers/port_forwarding/Linksys/WAG200G/default.htm] Firmware Version: 1.01.09 or better
|-
| Linksys/Cisco || [http://en.wikipedia.org/wiki/Linksys_WRT54G_series WRT54G] || Works || [http://portforward.com/english/routers/port_forwarding/Linksys/WRT54G/default.htm]
|-
| Linksys/Cisco || [http://www.linksysbycisco.com/ANZ/en/products/WAG160N WAG160N] || Works || [http://portforward.com/english/routers/port_forwarding/Linksys/WAG160N/default.htm]
|-
| Linksys/Cisco || [http://homesupport.cisco.com/en-us/wireless/lbc/WAG54G WAG54G v3] || Works ||
|-
| Linksys/Cisco || [http://www.linksysbycisco.com/ANZ/en/products/E3000 E3000] || Works || [http://portforward.com/english/routers/port_forwarding/Cisco/Linksys-E3000/default.htm]
|-
| Linksys/Cisco || [http://homesupport.cisco.com/en-us/wireless/lbc/WAG54G WAG54G v2 - NZ/AU] || Works || Faster processor, more memory and larger NAT table
|-
| Linksys/Cisco || WAG120N || Works ||
|-
| Linksys/Cisco || Linksys RT31P2 || Works ||
|-
| Netgear || WNR834M || Works ||
|-
| Netgear || WNR2000 || Works || With firmware 1.2.3.7 Loop back now enabled 'out of the box'
|-
| Netgear || WGR614 || Works || confirmed to work out of the box
|-
| Netgear || RP614 || Works || Version 3 or better
|-
| Netgear || DG834G || Works || v1, v2, v3 & v4 are end of line in most markets. The v3 & v4 are proven good performers.
|-
| Netgear || Pro Safe VPN FVS318 || Not Working || [http://www.netgear.com/service-provider/products/security/wired-VPN-firewalls/FVS318.aspx#two]
|-
| Netgear || WGR614 || Not Working || [http://www.netgear.com/home/products/wirelessrouters/simplesharing/WGR614.aspx] does not work with ISP required gateway modems
|-
| Netgear || [http://support.netgear.com/app/products/family/a_id/8213 WNR3500 ] || Works || [http://portforward.com/english/routers/port_forwarding/Netgear/WNR3500/defaultguide.htm] NB restart after configuration
|-
| Netgear || RP614v3 and Newer revisions || Works || [http://portforward.com/english/routers/port_forwarding/Netgear/RP614v3/defaultguide.htm]
|-
| Netgear || [http://www.netgear.com/home/products/wirelessrouters/high-performance/WNDR3700.aspx WNDR3700] || Works || [http://portforward.com/english/routers/port_forwarding/Netgear/WNDR3700/default.htm]
|-
| SMC || [http://www.smc.com/index.cfm?event=viewProduct&cid=1&scid=17&localeCode=EN%5FUSA&pid=924 SMC-7004VBR] || Works || [http://portforward.com/english/routers/port_forwarding/SMC/SMC7004ABR/defaultguide.htm]
|-
| Thomson SpeedTouch || TG585 || Works || [http://portforward.com/english/routers/port_forwarding/Thomson-Alcatel/SpeedTouch585/default.htm] new ver. Only
|-
| Thomson SpeedTouch || ST-585i || Works || [http://portforward.com/english/routers/port_forwarding/Thomson-Alcatel/SpeedTouch585i/default.htm] May need to enable loopback through telnet
|-
| Thomson SpeedTouch || ST-780 || Works || [http://portforward.com/english/routers/port_forwarding/Thomson-Alcatel/ST780/default.htm] May need to enable loopback through telnet
|-
| Thomson SpeedTouch || ST-516 || Works || [http://portforward.com/english/routers/port_forwarding/Thomson-Alcatel/SpeedTouch516/default.htm]May need to enable loopback through telnet
|-
| TP-Link || TL-WR740N || Works || All TP-Link wired routers are said to support loopback, including the wifi ones. This one has been confirmed by support staff.
|-
| TP-Link || [http://www.tp-link.com/en/products/details/?categoryid=227&model=TL-R470T%2b TL-R470T+] || Works || All TP-Link wired routers are said to support loopback, including the wifi ones. This one has been confirmed by support staff.
|-
| Scientific Atlanta || WebSTAR-DPR2320 || Works || [http://portforward.com/english/routers/port_forwarding/Scientific-Atlanta/WebSTAR-DPR2320/default.htm] Google for more info
|-
| Ubee || DDW2600 || Works || [http://www.ubeeinteractive.com/index.php/products/product-overview/wireless_cable_router1/] Cable Router
|-
| 3Com / HP || 3CRWDR100A-72 || Works || [http://portforward.com/english/routers/port_forwarding/3com/3CRWDR100A-72/default.htm]
|-
| 3Com / HP || 3CRWDR101A-75 || Works || [http://portforward.com/english/routers/port_forwarding/3com/3CRWDR101A-75/eMule.htm]
|-
| 2wire || 2701hg-s || Not Working ||
|-
| 2wire || 2701hg-B || Works || [http://portforward.com/english/routers/port_forwarding/2wire/2701HG-B/default.htm]
|-
| 2wire || 2701hg-D || Works || [http://portforward.com/english/routers/port_forwarding/2wire/2701HG-D/default.htm]
|-
|}

= Notes on Some Routers =

== D-Link ==

D-Link DGL-4500 series of routers have the largest available nat table of any router on the market.  These routers range from 70$-180$ USD depending on where you live and purchase from.

When considering a purchase, consider performance against cost. Upper end ADSL 2+ routers can add several Mbs to your modems sync speed.

'''Wireless Routers - Access Point Only'''

These routers are Access Point devices, and contain no ADSL modem and hence need a separate adsl modem operating in Bridge mode.

* [http://www.dlink.com/products/?pid=64 D-Link DGL-4500]
* [http://www.dlink.com/products/?pid=530 D-Link DIR-655]
* [http://www.dlink.com/products/?pid=DIR-635 D-Link DIR-635]
* [http://www.dlink.com/products/?pid=DIR-601 D-Link DIR-601]
* [http://www.dlink.com/products/?pid=DIR-600 D-Link DIR-600]
* D-Link DI-524

'''Routers With ADSL modem'''
No items to list currently

Note: The DGL-4100 & DGL-4300 have been discontinued, and the replacement model is the DIL-825 and DIL-855 - Loopback status unknown on these later models. The DGL-4300 may be available second hand.

== Netgear ==

* NETGEAR WNR834M : ftp://downloads.netgear.com/files/wnr834m_ref_manual.pdf

* Netgear DG834G v3 with latest firmware & v4 upto firmware version v5.01.09 (according to [http://forum1.netgear.com/showthread.php?t=42641 this link], a later firmware update of v4 removed NAT loopback) NAT Loopback returned as menu option with latest v5.01.16 firmware for the v4 model. The latest model versions, marked v5 on the unit's label, has significantly different internals and is not currently Loopback capable(the v5 has the wireless aerial on the right, not the left, as looking from the front. The DG834G v1, v2, v3 & v4 are end of line in most markets. The v3 & v4 are proven good performers.
* Netgear DGN1000 worked out of the box. Note this working item reports its firmware version as V2.1.00.19_VG which seems much newer than the version offered for download on netgear.com.
* NETGEAR FVS338 : loopback issue with firmware v3.0.3-17 (2008). LAN address is incorrectly presented to simulator instead of WAN address. Fixed in latest update v3.0.6-25 (2010).

== Other routers & Hardware ==

* BT home hub V2
* If you are using a ZyXEL DSL router/modem from Embarq, please read [[OpenSim:Network_settings#A_solution_for_local_connections_when_you_are_using_NAT_and_Port_Forwarding|this configuration guide]]. This will show you how to reconfigure your DSL router/modem to fix this problem.

= KNOWN non-functional for OpenSim: =

* Netgear Pro Safe VPN FVS318 : [http://www.netgear.com/Products/VPNandSSL/WiredVPNFirewallRouters/FVS318.aspx http://www.netgear.com/Products/VPNandSSL/WiredVPNFirewallRouters/FVS318.aspx]
* NetGear WGR614 does not work with ISP required gateway modems
* Belkin F5D7230-4 (the router might work if 3rd party firmware is used, such as DD-WRT : http://www.dd-wrt.com/ )

 

= REFERENCE LINKS: =

More Information Related to Routers and Solutions @: [http://osgrid.org/forums/viewtopic.php?f=8&t=2283 osgrid.org/forums/viewtopic.php]

= Linux specific solutions =
== SETTING UP A LINUX COMPUTER TO ACT AS A ROUTER ==

----

For Linux based Netfilter (iptables) routers, you want to set up the NAT table with some extra entries The following script is something to get you started, you'll need to fix up the variables at the top to match your system and network. <source lang="bash">
#!/bin/bash
#
# vvvvv - Fix these! - vvvvv
IPTABLES=/usr/sbin/iptables
LAN_NETWORK=192.168.0.0/24
SERVER_IP=192.168.0.2
INTERNET_IP=100.100.100.100
REMOTING_PORT=8895
REGION_PORT=9000
# ^^^^^ - Fix these! - ^^^^^

# First, the Destination NAT, anything going to the external address on our ports, we redirect to the server
# Note, if you have a double NAT running and this router doesn't actually have the internet IP address, you'll
# need another set of PREROUTING-DNAT lines with the --destination (-d) set to the internet facing private address
$IPTABLES -t nat -I PREROUTING -d $INTERNET_IP -p tcp --dport $REMOTING_PORT --jump DNAT --to-destination $SERVER_IP
$IPTABLES -t nat -I PREROUTING -d $INTERNET_IP -p udp --dport $REGION_PORT --jump DNAT --to-destination $SERVER_IP
$IPTABLES -t nat -I PREROUTING -d $INTERNET_IP -p tcp --dport $REGION_PORT --jump DNAT --to-destination $SERVER_IP

# Second, the Source NAT, we need this so that returning packets to our LAN clients go back through the router first,
# otherwise, the server will try to talk directly to the client and the client will reject them
$IPTABLES -t nat -I POSTROUTING -s $LAN_NETWORK -d $SERVER_IP -p tcp --dport $REMOTING_PORT --jump SNAT --to-source $INTERNET_IP
$IPTABLES -t nat -I POSTROUTING -s $LAN_NETWORK -d $SERVER_IP -p udp --dport $REGION_PORT --jump SNAT --to-source $INTERNET_IP
$IPTABLES -t nat -I POSTROUTING -s $LAN_NETWORK -d $SERVER_IP -p tcp --dport $REGION_PORT --jump SNAT --to-source $INTERNET_IP
</source>

--[[User:Hell Fire|Hell Fire]]

== DNS solution ==
It's possible to host your own DNS-server, so you can prevent some of the dns-naming problems mentioned before. If http://example.org resolves to the external ip, and that loopback connection is prevented by your router, you could point your resolv.conf to a local nameserver like:
nameserver 192.168.2.2
Now you need bind/named installed in order to handle the dns-requests. You can find a bind example configfile here.

= openWRT Routers: =

If you use openWRT firmware on your router, check here: [[Users:Thomax:nat-loopback|OpenWRT NATLoopback]]

= Windows XP, Win7 Loopback Adapter Install: =

Please see this -> Windows XP: http://www.windowsnetworking.com/articles-tutorials/windows-xp/Install-Microsoft-Loopback-adapter-Windows-XP.html

Windows 7: http://www.windowsreference.com/windows-7/how-to-install-a-loopback-adapter-in-windows-7/

[[Category:Hardware]]

See more potential loopback solutions here: http://opensimulator.org/wiki/Network_Settings#DynDNS_loopback

Wifi

2013-06-07T18:28:16Z

Arielle: /* Setting Configuration Parameters for a Grid */

{{quicklinks}}
{{thirdparty}}
'''Wifi - A Simple Account Management Front-end'''

"Wifi" stands for "Web Interface For... I", and is an '''add-on''' module which is not a standard part of OpenSimulator. It is provided by Diva Canto and can be added to OpenSimulator 0.7 onwards.

== '''PLEASE NOTE''' ==
'''Packaged binary versions of Wifi are available from http://metaverseink.com/Downloads.html in two packages: as part of the standalone Diva distribution (D2) of OpenSimulator, and another package for use with a ROBUST server grid implementation of OpenSimulator. The latter package (Wifi for Robust) is NOT intended to work with standalone implementations of OpenSim.'''

----

== Introduction ==
'''


Wifi provides an embedded Web application for handling user registrations. Wifi is a set of components that can be loaded up by both standalone simulators and [[ROBUST]] servers.

Its features include:

* Account creation, optionally controlled by the administrator
* Configurable default avatars for new accounts
* Account updates by both users and administrator
* Account deletion by administrator
* Password recovery via email
* Simple management of user inventory 
* A welcome page which can be used as login page for the user's viewer.

Wifi has a few interesting properties that make it a good fit for small-to-medium OpenSimulator-based virtual worlds.

# It doesn’t require an additional web server; it’s all done with built-in OpenSimulator features.
# Using OpenSimulator features bring many technical benefits. These benefits aren't visible immediately, but it will show its value in the future. Unlike other Web apps that access the database directly, Wifi works by communicating with OpenSimulator directly. This means that any future changes to the OpenSimulator database structure, will not affect Wifi.
# Technically speaking, Wifi is a set of components that can be used by both standalone sims, as well as [[ROBUST]] (Grid) servers.

== Adding Wifi to your OpenSimulator Setup ==

'''Additions to Standard OpenSimulator Distribution (from 0.7 onwards)'''

=== Binary Approach ===

Obtain the latest Wifi module distribution zip from
http://metaverseink.com/Downloads.html
and place the files as instructed in the equivalent locations in your OpenSimulator directory.

bin directory
* add bin/Diva.Wifi.dll
* add bin/Diva.Wifi.ScriptEngine.dll
* add bin/Diva.OpenSimServices.dll
* add bin/Diva.Utils.dll
* for standalones, also add bin/Diva.Modules.dll (this doesn't exist in the module zip! Get it from the diva-rxxxxx.zip file instead.)

Copy WifiPages directory and its contents to OpenSimulator top level directory.

doc directory
* add in doc/WIFI.txt

Copy over the WIFI related readme, release notes and licence text files.

For grids, edit Robust(.HG).ini in section [Startup] to add 8002/Diva.Wifi.dll:WifiServerConnector to <code>ServiceConnectors</code>.

For standalones, edit StandaloneCommon.ini in section [Modules] to add <code>WifiModule = true</code>.

Add a new section [WifiService] from example at http://github.com/diva/diva-distribution/blob/master/addon-modules/Wifi/Wifi.ini.example to Robust(.HG).ini (for grids) or StandaloneCommon.ini (for standalones).

=== Source Code Approach ===

Get Diva Distribution which contains the Wifi modules from
http://github.com/diva/diva-distribution/

== Setting Configuration Parameters for a Grid ==

The complete example file is here:
http://github.com/diva/diva-distribution/blob/master/addon-modules/Wifi/Wifi.ini.example

'''Additions to Robust.ini or Robust.HG.ini for Grids'''
(reported to not be working on Robust.ini .7.5 as of June 07/2013

<source lang="ini">[Startup]
ServiceConnectors = "8002/Diva.Wifi.dll:WifiServerConnector"
</source>

Note that it will be usual to specify the port number to be accessible outside your firewall (normally port 8002) rather than the default Network Port for internal inter-component OpenSimulator traffic (normally port 8003) which can be set to only be accessible within a firewall.

<source lang="ini">[WifiService]
GridName = "grid name"
LoginURL = "http://<hostname>:8002"
WebAddress = "http://<hostname>:8002"

;; The Wifi Administrator account
AdminFirst = "Wifi"
AdminLast = "Admin"
AdminEmail = "you@example.com"

;; Do you want to be able to control grid registrations?
AccountConfirmationRequired = false

;; Default avatars for new account registration
;; Syntax: AvatarAccount_<AvatarType> = "<FirstName> <LastName>"
;; Appearance and attachments are copied from avatar <FirstName> <LastName>.
AvatarAccount_Female = "Female Avatar"
AvatarAccount_Male = "Male Avatar"
AvatarAccount_Neutral = "Neutral Avatar"

;; Preselection for default avatar in new account registration
AvatarPreselection = "Neutral"

;; Variables for your mail server
;; Users will get email notifications from this account.
SmtpHost = "mail.example.com"
SmtpPort = "587"
SmtpUsername = "your_account_in_this_mail_server"
SmtpPassword = "your_password_in_this_mail_server"
</source>

== Setting Configuration Parameters for a Standalone ==

The complete example file is here:
http://github.com/diva/diva-distribution/blob/master/addon-modules/Wifi/Wifi.ini.example

'''Additions to config-include/StandaloneCommon.ini for Standalones'''

<source lang="ini">[Modules]
WifiModule = true

[WifiService]
GridName = "grid name"
LoginURL = "http://<hostname>:9000"
WebAddress = "http://<hostname>:9000"

;; The Wifi Administrator account
AdminFirst = "Wifi"
AdminLast = "Admin"
AdminEmail = "you@example.com"

;; Do you want to be able to control grid registrations?
AccountConfirmationRequired = false

;; Default avatars for new account registration
;; Syntax: AvatarAccount_<AvatarType> = "<FirstName> <LastName>"
;; Appearance and attachments are copied from avatar <FirstName> <LastName>.
AvatarAccount_Female = "Female Avatar"
AvatarAccount_Male = "Male Avatar"
AvatarAccount_Neutral = "Neutral Avatar"

;; Preselection for default avatar in new account registration
AvatarPreselection = "Neutral"

;; Variables for your mail server
;; Users will get email notifications from this account.
SmtpHost = "mail.example.com"
SmtpPort = "587"
SmtpUsername = "your_account_in_this_mail_server"
SmtpPassword = "your_password_in_this_mail_server"
</source>

== Configurable Default Avatars ==
[[Image:Openvue-avatars-male-female-neutral-2010-08-27.jpg|300px|right|Example Avatars]]
When users sign up, they can choose between default avatars. It's up to you to decide what these default avatars look like. Here is how you can configure them... Once your OpenSimulator is up and running, create accounts (using Wifi) with the names given in your configuration. With the above examples, these would be:
* Male Avatar
* Female Avatar
* Neutral Avatar

Then login to the world under each of those accounts, and set their appearances however you like. You can add prim attachments.

== Problems with HTTP ports ==

The port used for the Wifi HTTP service is configurable. Usually this will be 8002 for a grid and 9000 for a standalone unless you use custom ports.

For a standalone you can do this by adding the "port" line for the port to use for Wifi and other services to the [Network] section of OpenSim.ini

<source lang="ini">[Network]
port = 9000
</source>

Or for a grid specify a specific port (usually 8002) for the WifiServiceConnector in the ServiceConnectors list in the [Startup] section of Robust(.HG).ini

<source lang="ini">[Startup]
ServiceConnectors="............,8002/Diva.Wifi.dll:WifiServerConnector"
</source>

In either case, define the equivalent WebAddress in the [WifiService] section of your StandaloneCommon.ini or Robust(.HG).ini (or addon-modules/Wifi/config/Wifi.ini if used in future).

<source lang="ini">[WifiService]
WebAddress = "http://hostname:8002"
</source>

If you do not use the usual OpenSimulator service ports, please note that some network setups and ISPs will not allow HTTP to be served on port 80. It is usual to use an alternative port such as 8080 or a custom port in that case.

== Wifi URLs When Operational ==

* Sample grid: <nowiki>http://yourgridhostname:8002/wifi</nowiki>
* Sample standalone: <nowiki>http://yourstandalonehostname:9000/wifi</nowiki>
* Local standalone: <nowiki>http://localhost:9000/wifi</nowiki>

'''Examples'''

* Diva Tagus Test World (temporary August 2010): http://tagus.ics.uci.edu:9000/wifi

== Wifi Administrator Functions ==

=== Manage Users ===
[[Image:Openvue-Wifi-Example.jpg|300px|right|Example Wifi Entry Page]]
If authorisation is set to be on, you will receive an e-mail to the nominated admin account e-mail address if a user requests a new account and avatar creation. You can activate or delete new user creation requests. Users are notified of the activation via an e-mail to their nominated address.

You can also search for users and change their details. Give a space as a search term to select all avatars. Available are fields for "Level", "Flags" and "Title".
* Level = 0 is a normal user
* Level = 50 (default) is used to indicate a privileged user (e.g. who can set up new hypergrid linked regions)
* Level = 100 is a Wifi admin account user

You can manually reset a user's password by typiing into the password box and the nhitting the "Reset" button. Note that the user is '''NOT''' infromed of this password reset, so you must manually contact the user to communicate such a password change.

Note that the Wifi admin username/avatar is set in the Wifi configuration, and can be changed there. BUT.. '''once an admin always an admin'''. Well almost. If you change from one admin to another, the previous avatar still has administrator rights. You can remove Wifi administrator rights from an avatar by changing the "Level" of the user from 100 to the normal avatar level of 0 using the Manage Users facility in Wifi.

You can set an intermediate level for a '''privileged''' user which can be used to allow certain types of Wifi menu that a normal user will not see, but that are less than full admin user rights. A configurable parameter sets the '''Level''' above which this functions for a user (default 50).

=== Manage Regions ===

A facility to add '''LINK REGIONS''' is available in Wifi versions for OpenSimulator 0.7.1 onwards.

Administrators and other '''privileged''' users can also view the current set of '''LINKED REGIONS'''

=== Remote Console ===

A feature in Wifi versions for 0.7.1 onwards and available to administrators via the '''CONSOLE''' link if suitably enabled.

The WifiConsole uses OpenSim's REST console and thus the Robust server and any simulators must be started with parameter "-console rest". Furthermore, the configuration options "ConsoleUser" and "ConsolePass" must be set in section [Network] and the values of these options must match across all instances. Finally, for all region simulators (i.e. except for the Robust server), option "ConsoleAllowedOrigin" must be set to the same value as option "WebAddress" in section [WifiService] of the Robust configuration.

Please note that as at February 2011 the console in Wifi is not much more than a proof on concept in its current state. It has been tested on web browsers based on Mozilla (i.e. the Gecko Engine) only. Browsers using the WebKit engine do work somewhat, too, and IE has its own issues. The console also does not yet work with any interactive input, as necessary for creating a new region with "create region", for example.

Right now, there is no way to use this feature in a secure way because the values for "ConsoleUser" and "ConsolePass" are transmitted as clear text over the network. Please keep this in mind when using the console in Wifi.

== Diva Distribution ==

[[Image:Diva-Tagus-Wifi-Example-v2.jpg|300px|right|Example Wifi Entry Page]]

Wifi is included and enabled by default in the [[Diva Distribution]]:

* Documentation: http://wiki.github.com/diva/d2/wifi
* Blog Description: http://www.metaverseink.com/blog/
* Downloads and binary distribution: http://metaverseink.com/Downloads.html
* Source Code: http://github.com/diva/diva-distribution/

Download

2013-03-19T03:13:14Z

Arielle: /* Other Distributions */

{{Quicklinks}}{{ReleaseInfo}}
= Introduction =
'''Note 1:''' If you are reading this on any site but http://www.opensimulator.org, you might not be actually downloading OpenSimulator.org software. Please check your browser URL before proceeding any further.

'''Note 2:''' Depending on what you want to do with OpenSimulator, setting it up and keeping it running will require a fair amount of technical knowledge. After downloading OpenSim, please consult the several instruction manuals on this Wiki and elsewhere. Please be aware that the learning curve for operating OpenSimulator is steep.

'''Note 3:''' Many Linux distros (including Ubuntu) ship with only the "mono-runtime" package installed, however you need to install "mono-complete" for some OpenSimulator features such as LSL script commands. You must also use at least Mono V2.4.3 (Ubuntu 10.04 ships with mono 2.4.4 which works fine).

'''Note 4:''' OpenSimulator is made available under the [[BSD License]]. Downloaders of the code also receive an additional [[IP Rights Grant]] for any intellectual property licensed to OpenSimulator under the terms of the [[Contributions_Policy#OpenSimulator_Licensing_Conditions|Contribution Agreements]].

As OpenSimulator is still at an alpha code maturity stage, there is absolutely no guarantee that functionality works or is stable.

= Binary Packages =

== Current release ==
Binary packages of the latest OpenSimulator release are provided in .zip or .tar.gz form. The two packages are theoretically identical, though the .tar.gz was built using mono while the .zip was built using .NET.

Once you've unzipped/untarred these you'll be able to run OpenSimulator 'out of the box' in standalone mode - no code compilation or other installation required.

The current release is '''{{#var:currentversion}}''' (released on {{#var:releasedate}}) and can be downloaded as

*[{{#var:url_bingz}} opensim-{{#var:currentversion}}.tar.gz] or
*[{{#var:url_binzip}} opensim-{{#var:currentversion}}.zip]

After unpacking please read the [[{{#var:currentversion}} Release]] Notes.
Further instructions on running OpenSimulator may be found in README.txt after you untar/unzip the archives and within this wiki.



= Other Distributions =

OpenSimulator is a BSD licensed codebase, so other projects are welcome to repackage OpenSimulator and add their own modules or configuration. Current known public distributions are

* Diva Distribution, a '''Preconfigured hypergrided standalone,''' binary distribution. Easy to setup and to keep up to date. Windows and Linux/Unix. Download the file diva-rNNNN.zip, unzip it, read README.txt and take it from there.
http://metaverseink.com/Downloads.html

* OSGrid distribution. This is preconfigured for connection of an OpenSimulator instance to http://osgrid.org.
http://www.osgrid.org/index.php/downloads

* NewWorld Studio. Preconfigured standalone for beginners with GUI manager, automatic router configuration. Selection of hypergrid mode at startup. Windows, Linux and Mac versions. Basic download is free and enhanced features have a license fee.
http://newworldstudio.net/

* Sim on a stick (SOAS). A portable, standalone and self-contained deployment of OpenSimulator. Can be run from a USB stick on most Windows PCs.
http://simonastick.com/

= Source code =

== Current release ==
The two packages are identical apart from their compression formats.

*[{{#var:url_srcgz}} opensim-{{#var:currentversion}}-source.tar.gz] or
*[{{#var:url_srczip}} opensim-{{#var:currentversion}}-source.zip]


== Source code repostory ==
You can also download code directly from the [[Developer_Documentation#Source_Code_Repository_Access|OpenSimulator source code repository]]. However, we only suggest doing this if you've very familiar with OpenSimulator. Master development code at any point may be broken or may contain database changes that later need to be reversed.

= Previous releases =
You can find previous releases of OpenSimulator at http://opensimulator.org/dist. Very old releases (pre OpenSimulator 0.6.8) only have source code packages.

Previous [[Release Notes]]

= Developers and Testers =
If you're a developer or a tester and you want to download possibly broken development code then please [[Developer Documentation#Source Code Repository Access|go here]]

= Related Software =
* [[Related Software|Related Software Section]] - Here you can find details on OpenSimulator compatible viewers, external components (e.g. web sign-up systems) and add-on region modules.

''Pages by Category:''[[:Category:Users| User-pages]],[[:Category:Development| Developer-pages]],[[:Category:Scripts| Scripts]] 

[[Category:Users]]
[[Category:Developers]]

Download

2013-03-19T03:07:50Z

Arielle: /* Other Distributions */

{{Quicklinks}}{{ReleaseInfo}}
= Introduction =
'''Note 1:''' If you are reading this on any site but http://www.opensimulator.org, you might not be actually downloading OpenSimulator.org software. Please check your browser URL before proceeding any further.

'''Note 2:''' Depending on what you want to do with OpenSimulator, setting it up and keeping it running will require a fair amount of technical knowledge. After downloading OpenSim, please consult the several instruction manuals on this Wiki and elsewhere. Please be aware that the learning curve for operating OpenSimulator is steep.

'''Note 3:''' Many Linux distros (including Ubuntu) ship with only the "mono-runtime" package installed, however you need to install "mono-complete" for some OpenSimulator features such as LSL script commands. You must also use at least Mono V2.4.3 (Ubuntu 10.04 ships with mono 2.4.4 which works fine).

'''Note 4:''' OpenSimulator is made available under the [[BSD License]]. Downloaders of the code also receive an additional [[IP Rights Grant]] for any intellectual property licensed to OpenSimulator under the terms of the [[Contributions_Policy#OpenSimulator_Licensing_Conditions|Contribution Agreements]].

As OpenSimulator is still at an alpha code maturity stage, there is absolutely no guarantee that functionality works or is stable.

= Binary Packages =

== Current release ==
Binary packages of the latest OpenSimulator release are provided in .zip or .tar.gz form. The two packages are theoretically identical, though the .tar.gz was built using mono while the .zip was built using .NET.

Once you've unzipped/untarred these you'll be able to run OpenSimulator 'out of the box' in standalone mode - no code compilation or other installation required.

The current release is '''{{#var:currentversion}}''' (released on {{#var:releasedate}}) and can be downloaded as

*[{{#var:url_bingz}} opensim-{{#var:currentversion}}.tar.gz] or
*[{{#var:url_binzip}} opensim-{{#var:currentversion}}.zip]

After unpacking please read the [[{{#var:currentversion}} Release]] Notes.
Further instructions on running OpenSimulator may be found in README.txt after you untar/unzip the archives and within this wiki.



= Other Distributions =

OpenSimulator is a BSD licensed codebase, so other projects are welcome to repackage OpenSimulator and add their own modules or configuration. Current known public distributions are

* Diva Distribution, a '''Preconfigured hypergrided standalone,''' binary distribution. Easy to setup and to keep up to date. Windows and Linux/Unix. Download the file diva-rNNNN.zip, unzip it, read README.txt and take it from there.
http://metaverseink.com/Downloads.html

* OSGrid distribution. This is preconfigured for connection of an OpenSimulator instance to http://osgrid.org.
http://www.osgrid.org/index.php/downloads

* NewWorld Studio. Preconfigured standalone for beginners with GUI manager, automatic router configuration. Selection of hypergrid mode at startup. Windows, Linux and Mac vesions. Basic download is free and enhanced features have a license fee.
http://newworldstudio.net/

* Sim on a stick (SOAS). A portable, standalone and self-contained deployment of OpenSimulator. Can be run from a USB stick on most Windows PCs.
http://simonastick.com/

= Source code =

== Current release ==
The two packages are identical apart from their compression formats.

*[{{#var:url_srcgz}} opensim-{{#var:currentversion}}-source.tar.gz] or
*[{{#var:url_srczip}} opensim-{{#var:currentversion}}-source.zip]


== Source code repostory ==
You can also download code directly from the [[Developer_Documentation#Source_Code_Repository_Access|OpenSimulator source code repository]]. However, we only suggest doing this if you've very familiar with OpenSimulator. Master development code at any point may be broken or may contain database changes that later need to be reversed.

= Previous releases =
You can find previous releases of OpenSimulator at http://opensimulator.org/dist. Very old releases (pre OpenSimulator 0.6.8) only have source code packages.

Previous [[Release Notes]]

= Developers and Testers =
If you're a developer or a tester and you want to download possibly broken development code then please [[Developer Documentation#Source Code Repository Access|go here]]

= Related Software =
* [[Related Software|Related Software Section]] - Here you can find details on OpenSimulator compatible viewers, external components (e.g. web sign-up systems) and add-on region modules.

''Pages by Category:''[[:Category:Users| User-pages]],[[:Category:Development| Developer-pages]],[[:Category:Scripts| Scripts]] 

[[Category:Users]]
[[Category:Developers]]

Hypergrid 1.0

2013-03-07T17:11:38Z

Arielle:

This was the original Hypergrid version started as a proof of concept by Diva in 2008. It was included in Opensimulator core at the end of that year and was relevant until HG 1.5 came out with opensimulator 7.0. in 2010. As it was an "exercise in feasibility" its focus was on the ability to jump between different Opensimulator grids and standalones and not on the security aspects.
There are at the time of this writing some grids running this version of HG.

==The Hypergrid Classes ==

Currently, the hypergrid is implemented outside of the OpenSimulator namespace, so that there is complete separation between what already exists and this new behavior. It has its own namespace, HyperGrid. In it, there are 4 sub-namespaces that follow directly the software architecture of OpenSim, namely:
OpenSim.Framework:
ForeignUserProfileData extends UserProfileData by introducing information about the user's "home", namely the home address, port and remoting port. The user's home is not that user's user service; it's the opensim that the user has defined to be her home. This is necessary for supporting the home jump (Ctrl-Shift-H).
HGNetworkServersInfo follows the spirit of NetworkServersInfo, although it neither extends it nor uses it. For now, it's a utility class whose two main functions are to convert domain names of servers to IP addresses, and to uniformly provide the answer to the question bool IsLocalUser(...).
OpenSim.Region.Framework.Scenes.Hypergrid:
HGSceneCommunicationService extends SceneCommunicationService, overriding RequestTeleportToLocation. There are two very small but critical changes to the base method: (a) on the TeleportFinish event, we switch the region handles when the destination region is an hyperlink; (b) the connections at the end are always closed for hyperlink TPs.
HGScene extends Scene, overriding TeleportClientHome(...). The only change to the base method is to stay away from the user server, for now, because the user service is still not completely wrapped up for foreign users. Once the user service is properly wrapped up, this class will become unnecessary.
HGScene.Inventory is a partial class of HGScene, just like what happens in the OpenSimulator framework. This part of HGScene overrides some inventory-scene interaction methods, so that assets are fetched/posted from/to the user's asset server. Once that extra fetching/posting is done, these methods simply pass the ball to the base methods.
HGAssetMapper: this is a new class specific to the hypergrid that manages the fetching and posting of assets between foreign regions where the user is and the user's asset server.
OpenSim.Region.Communications.HyperGrid is a mashup of OpenSim.Region.Communications.*. This is the place where most of the hypergrid extension lies. One of the reasons for this is that the hypergrid communications part is doing one additional thing: it is making standalones network-able.
HGCommunicationsStandalone extends CommuniationsLocal. Just as its base, it is a hub for the several network services available in standalone mode. The main difference is that those services are extensions of what's in OpenSimulator.
HGCommunicationsGridMode extends CommunicationsManager directly. Again, it's a hub for the network services available in grid mode, those services being extensions of OpenSimulator.
The cluster HGGridServices (superclass), HGGridServicesStandalone and HGGridServicesGridMode (subclasses) implements the OpenSimulator interfaces IGridServices and IInterRegionCommunications. The 2 subclasses are wrappers for LocalBackEndServices and OGS1GridServices, respectively. There is one common pattern throughout these classes: check if the region to talk to is an hyperlink; if it's not, simply delegate the work to LocalBackEndServices/OGS1GridServices; if it is, push the work to the base class HGGridServices. HGGridServices, in turn, does the management of hyperlink regions, and defines two additional pieces of inter-region protocol:
region_uuid: for linking regions
expect_hg_user: similar to the existing expect_user interface, but with a lot more information about the user being passed around, namely all the user's servers (inventory, asset, user, home, etc.)
HGInventoryService extends LocalInventoryService and implements ISecureInventoryService. This class is the most obvious mashup of the pack, mixing local service access for standalone users and remote inventory access for when users are out and about. Right now, there is a fair amount of selective copy-and-paste, to stay away from the ugliness coming from OGS1InventoryService and OGS1SecureInventoryService. HGInventoryService is always a ISecureInventoryService. Its methods all follow the same pattern: check if the user is a local standalone user; if it is, pass the work to the base method (in LocalInventoryService); if it's not perform secure remote access.
HGUserServices wraps OSG1UserServices, but it's not functional yet.
OpenSim.Region.CoreModules.HyperGrid is a collection of 3 region modules:
HGWorldMapModule extends WorldMapModule. It reuses almost everything from the base class. The only small change is in RequestMapBlocks, where it tries to send Offline mapblocks to the client.
HGStandaloneInventoryService and HGStandaloneAssetService do what their names say. They are region modules that allow access to inventory and assets for standalones, when the standalone user is out and about. In spirit, there is a lot in common between these modules and the REST inventory/asset plugin. Unfortunately, that plugin could not be used because it defines a completely different interface than that used by existing inventory and asset servers, and the access for the hypergrid must use a consistent interface.

Hypergrid 1.0

2013-03-07T16:57:25Z

Arielle:

==The Hypergrid Classes ==

Currently, the hypergrid is implemented outside of the OpenSimulator namespace, so that there is complete separation between what already exists and this new behavior. It has its own namespace, HyperGrid. In it, there are 4 sub-namespaces that follow directly the software architecture of OpenSim, namely:
OpenSim.Framework:
ForeignUserProfileData extends UserProfileData by introducing information about the user's "home", namely the home address, port and remoting port. The user's home is not that user's user service; it's the opensim that the user has defined to be her home. This is necessary for supporting the home jump (Ctrl-Shift-H).
HGNetworkServersInfo follows the spirit of NetworkServersInfo, although it neither extends it nor uses it. For now, it's a utility class whose two main functions are to convert domain names of servers to IP addresses, and to uniformly provide the answer to the question bool IsLocalUser(...).
OpenSim.Region.Framework.Scenes.Hypergrid:
HGSceneCommunicationService extends SceneCommunicationService, overriding RequestTeleportToLocation. There are two very small but critical changes to the base method: (a) on the TeleportFinish event, we switch the region handles when the destination region is an hyperlink; (b) the connections at the end are always closed for hyperlink TPs.
HGScene extends Scene, overriding TeleportClientHome(...). The only change to the base method is to stay away from the user server, for now, because the user service is still not completely wrapped up for foreign users. Once the user service is properly wrapped up, this class will become unnecessary.
HGScene.Inventory is a partial class of HGScene, just like what happens in the OpenSimulator framework. This part of HGScene overrides some inventory-scene interaction methods, so that assets are fetched/posted from/to the user's asset server. Once that extra fetching/posting is done, these methods simply pass the ball to the base methods.
HGAssetMapper: this is a new class specific to the hypergrid that manages the fetching and posting of assets between foreign regions where the user is and the user's asset server.
OpenSim.Region.Communications.HyperGrid is a mashup of OpenSim.Region.Communications.*. This is the place where most of the hypergrid extension lies. One of the reasons for this is that the hypergrid communications part is doing one additional thing: it is making standalones network-able.
HGCommunicationsStandalone extends CommuniationsLocal. Just as its base, it is a hub for the several network services available in standalone mode. The main difference is that those services are extensions of what's in OpenSimulator.
HGCommunicationsGridMode extends CommunicationsManager directly. Again, it's a hub for the network services available in grid mode, those services being extensions of OpenSimulator.
The cluster HGGridServices (superclass), HGGridServicesStandalone and HGGridServicesGridMode (subclasses) implements the OpenSimulator interfaces IGridServices and IInterRegionCommunications. The 2 subclasses are wrappers for LocalBackEndServices and OGS1GridServices, respectively. There is one common pattern throughout these classes: check if the region to talk to is an hyperlink; if it's not, simply delegate the work to LocalBackEndServices/OGS1GridServices; if it is, push the work to the base class HGGridServices. HGGridServices, in turn, does the management of hyperlink regions, and defines two additional pieces of inter-region protocol:
region_uuid: for linking regions
expect_hg_user: similar to the existing expect_user interface, but with a lot more information about the user being passed around, namely all the user's servers (inventory, asset, user, home, etc.)
HGInventoryService extends LocalInventoryService and implements ISecureInventoryService. This class is the most obvious mashup of the pack, mixing local service access for standalone users and remote inventory access for when users are out and about. Right now, there is a fair amount of selective copy-and-paste, to stay away from the ugliness coming from OGS1InventoryService and OGS1SecureInventoryService. HGInventoryService is always a ISecureInventoryService. Its methods all follow the same pattern: check if the user is a local standalone user; if it is, pass the work to the base method (in LocalInventoryService); if it's not perform secure remote access.
HGUserServices wraps OSG1UserServices, but it's not functional yet.
OpenSim.Region.CoreModules.HyperGrid is a collection of 3 region modules:
HGWorldMapModule extends WorldMapModule. It reuses almost everything from the base class. The only small change is in RequestMapBlocks, where it tries to send Offline mapblocks to the client.
HGStandaloneInventoryService and HGStandaloneAssetService do what their names say. They are region modules that allow access to inventory and assets for standalones, when the standalone user is out and about. In spirit, there is a lot in common between these modules and the REST inventory/asset plugin. Unfortunately, that plugin could not be used because it defines a completely different interface than that used by existing inventory and asset servers, and the access for the hypergrid must use a consistent interface.

Hypergrid 1.5

2013-03-07T16:48:59Z

Arielle: Created page with "Version 1.5 has been replaced with HG 2.0 as of this writing though a number of HG enabled grids are still using it. There were 2 versions, HG 1.5 and HG 1.5 i7 which were not co..."

Version 1.5 has been replaced with HG 2.0 as of this writing though a number of HG enabled grids are still using it. There were 2 versions, HG 1.5 and HG 1.5 i7 which were not compatible with each other and jumps between them will either partially or completely fail.

This version has increased security by limiting the hyperjumper's inventory exposure to other grids/standalones to what is in the My Suitcase folder which sits outside of the My Inventory folder. Inventory items picked up on hypergrid travels go into the My Suitcase folder and once back on the travellers home grid the item(s) are moved/copied from the Suitcase to the appropriate My Inventory folder. In practice the move/copy did not always work well except with web frontends ie Diva's Wifi, that were specifically coded to allow the transfers.

2012-10-26T03:35:01Z

Arielle: /* DynDNS loopback */

{{Quicklinks}}
 

== Introduction ==

These instructions are for enabling access to a grid from behind a firewall. Please note that if you are using consumer network hardware, you will need a router that supports NAT loopback. See [[NAT Loopback Routers]].

'''TODO: Improve instructions for allowing access to a standalone from behind a firewall'''.

== OpenSimulator Grid - Ports for Grid Services - from version 0.7.0 ==

Ports used for Grid services (such as login, user control, grid management, asset services and inventory services, etc) are run within a ''Robust'' shell started by Robust.exe. They can be configured to state which port they run on, and the services can be run across multiple machines as desired to balance load.

But in a simple grid with all the Robust services running in a single Robust.exe shell it is normal to just use two ports for all services:

TCP/8002 - All externally and user accessible OpenSimulator services
TCP/8003 - All internal OpenSimulator services

Hence, 8002 should be accessible through your firewall, but in this simple setup 8003 can be behind a firewall.

== OpenSimulator Grid - Ports for Region Simulators ==
One port must be open on any computer running an OpenSim.exe simulator that attaches to a grid. OpenSim.exe can be run on same computer (or one of computers) on which the Grid Services run, or on a separate computer. One OpenSim.exe can be used to run a number of regions, but each region must have its own unique port on that computer.

TCP+UDP/9000 - Default Port for First Simulator - grid, regions, and clients talk to these
TCP+UDP/9001 - Default Prot for Second Simulator - grid, regions, and clients talk to these
TCP+UDP/900x - Default Port for further Simulators...

In fact you can choose which port you prefer to use for each region on grid using the '''InternalPort''' parameter in the relevant Region description .ini file

XML-RPC communications, if enabled, are on the port specified in the [XMLRPC] section '''XmlRpcPort''' parameter (default port 20800).

TCP+UDP/20800 - Default Port for XML-RPC communications to a specific OpenSim.ini simulator (and all regions on it)

== OpenSimulator StandAlone ==
* UDP+TCP/9000 - Services and the single region simulator are used via this single port

* Check your /bin/Regions/ directory which contain one or more Region description files. Three of the fields will specify the internal IP address or domain name, the external IP address or domain name, and the port to be used for the region (which must be unique for each region) - something like this:
InternalAddress = "0.0.0.0"
InternalPort = 9000
ExternalHostName = 82.73.39.77"

* Retrieve your [http://www.ip-adress.com/ external_host_name]
* Get your internal_ip_address (using ipconfig for windows, or ifconfig for linux)
* Make sure the settings match

If you have a router in front of your internet-modem, check out ''NAT and Port Forwarding''.
Else you're good to go.

== Optional and Add-on Module Specific Ports ==

=== FreeSWITCH Voice ===

TCP+UDP 5060 - SIP Ports (5060 for default call profile)
TCP+UDP 1720 - H.323 ports for call setup

More details on the Freeswitch ports used and firewall configuration details are at:

* [[Freeswitch Module#Firewall Config]]
* http://wiki.freeswitch.org/wiki/Firewall

=== Mumble Voice ===

SIP Ports
ICE Ports

== NAT and Port Forwarding ==

=== Straightforward ===

If your host does not have a public IP address (eg it is hidden behind a home router) you will have issues hosting grid and region servers if you plan on connecting clients to it on both sides of the router, however this can be worked around through the use of port forwarding and ip-redirecting.This will also correct issues where the client hangs at region handshake. 

* Set internal_ip_address to your local LAN-ip(e.g. 192.168.2.1) (region xml-file)
* Set the external_host_name to your external IP-Address (Not a hostname, since DNS-resolving doesn't work properly) (region xml-file)
* Forward the appropriate ports to the OpenSim-server on both UDP and TCP (router-setup)
* Open appropriate ports on the OpenSim-server's firewall on both UDP and TCP 
* Reroute traffic for '''Linux:'''
** iptables -t nat -A OUTPUT --dst '''''EXTERNAL_IP''''' -p tcp --dport 9000:9010 -j DNAT --to-destination '''INTERNAL_IP'''
** iptables -t nat -A OUTPUT --dst '''''EXTERNAL_IP''''' -p udp --dport 9000:9010 -j DNAT --to-destination '''''INTERNAL_IP'''''
** service iptables restart 

Those iptables lines will redirect any traffic going to '''''EXTERNAL_IP''''' on ports 9000 to 9010 to I'''''NTERNAL_IP'''''. The internal ip is the LAN-IP of your server, and External ip is your internet IP. ''Use the above iptables command on all internal machines'' except your gateway/router. This assumes your gateway/router machine does not also host your sim. This also assume you have a default ACCEPT policy on your internal machines. So to connect from within your LAN, use the above iptables commands to reroute the traffic to the server internal ip.

* Reroute traffic for '''Windows:'''
** netsh (this method needs experimentation and elaboration. Please see the [[Talk:Network Settings|Discussion page]] for some guesswork on where to start)
*** note from paulieFlomar: I tried using Windows built-in tools like FireWall, netsh, and IP Security Policy. My experience with these tools was unsuccessful. I then tried to create an outgoing rule with some third-party firewall products. I tried ZoneAlarm and Sunbelt Firewall. Neither of these products would allow me to create outgoing rules. Finally, I tried creating an outgoing rule in my Linux IP Tables firewall. This worked. I created 2 rules which I placed in a firewall script, before my NAT rule. The rules were:

iptables -t nat -A PREROUTING --dst '''''EXTERNAL_IP''''' -p tcp --dport 9000:9010 -j DNAT --to-destination '''''INTERNAL_IP'''''

iptables -t nat -A PREROUTING --dst '''''EXTERNAL_IP''''' -p udp --dport 9000:9010 -j DNAT --to-destination '''''INTERNAL_IP'''''

These rules worked. I can now access my region from my LAN.

Optional:

* Register an external domain-name (for external connections)
* Use Bind for internal domain-name resolving

=== DynDNS loopback ===

This method was used and successfully tested using www.dyndns.com (creates a virtual domain for your pc/ip, like yourcomputer.ath.cx) as loopback for devices on a LAN with three machines (pentium 2.8ghz running windows xp - internet server , amd opteron running ubuntu 7.10 64bit - as opensim server - and MacBook with OSX 10.4.11 - as client), a modem (thomson/alcatel speedtouch 330) and a mini-switch (which brand no one ever heard of). The connection of these machines is made as following: Modem -> Win Pc -> Switch -> Mac and Ubuntu. Dyndns is used to loopback to the Win Pc, and then it forwards the request to the internal LAN opensim server, which grants everything for the client. As for the client, if he is inside the private LAN then he is now actually someone on the internet requesting for access to the opensim server. Thus, if the client is someone on the internet then he will be treated like that. Tricky ? Further details ahead:

Method:

* Set the simulator listening IP address to your dyndns domain - edit ''opensim/bin/Regions/Regions.ini''; and change the external_host_name to ''external_host_name="yourcomputer.ath.cx"''. Leave internal_ip_address "0.0.0.0" and port "9000".
* Set the client (SecondLife Viewer) -loginuri to "yourcomputer.ath.cx:8002" (the port used was 8002, yours can be different if you configured it that way ie: "yourcomputer.ath.cx:9000 on Standalone mode) - i didnt use the -loginserver flag also. This can be set in the Grid Manager of most third party viewers.
* Port Forward the above ports on the internet server (in this case, win xp). You do so by creating exceptions in Windows Firewall for the above mentioned ports, and for both connections: Internet Connection and LAN - this keeps the ports open for the web requests to travel over the private network.
* Edit "hosts" file (on windows, this is C:\Windows\System32\Drivers\etc\hosts and on Unix-type systems, this is /etc/hosts) entry on your internet server (in this case, win xp box) and add the following line: ''xxx.xxx.xxx.xxx<nowiki>    </nowiki> yourcomputer.ath.cx''. Of course, xxx.xxx.xxx.xxx is your opensim server internal LAN IP.

yourcomputer.ath.cx is now available for everyone to connect and you may login with the client!

 

=== DynDNS and the free IPCop Linux Firewall ===

Here an other way with the IPCop Linux Firewall, DynDNS and a OpenSimulator server

* Setup an IPCop firewall with 3 interfaces (red, green, orange) and put the OpenSimulator server on the orange interface (all OpenSimulator server's on one Linux box). Red is the internet, green is your lan.
* Setup the DynDNS service on the IPCop Firewall.
* change the external_host_name in the default.xml to the DynDNS name
* do'nt change the internal_ip_address in the default.XML, it should be 0.0.0.0
* if there, delete all loopbacks in /etc/hosts only 127.0.0.1 should be localhost
* customize the Port Forwarding on the IPCop Firewall (8002 TCP, 9000 UDP/TCP and for every additonal region 900X UDP/TCP). Port forwarding should be set to the (orange) interface adress of the OpenSimulator Box

Then it should be possible to conenct from inside the LAN (green) and it is also possible to conenct from the internet (over the red interface). (well, the inside-lan connections are also made now over the RED interface, but infact, this is in the same ISP network, it should be quit fast ;-)

* Attention : the ports on the IPCop Firewall must also be open if you connect from inside (green) to your OpenSimulator Grid !

If you are using the OS WebGui, do'nt forget to set the "SMTP AUTH" in your email server. Most of the dynamic IPs are blocked at ISP level so the new users do'nt get any confirmation email.

This was tested with the Hippo OpenSimulator Viewer and with the Login URL : http://DynDNSName:8002

 

=== Local connections with ZyXEL DSL modem/router and NAT/Port Forwarding ===

This solution works with the ZyXEL Prestige 660ME-61 DSL Router. It may work with other models made by ZyXEL.

Method:

* Connect by TELNET to your ZyXEL DSL modem. Use the same IP address that you would if you were using the web interface. For example, the default ip on most Embarq ZyXEL DSL modems is 192.168.2.1.

telnet 192.168.2.1

* Enter your password. If you do not know it, try just pressing <ENTER> or ask your ISP for the password. They may or may not give it to you.

* Select menu option "24. System Maintenance" from the menu.

Copyright (c) 1994 - 2004 ZyXEL Communications Corp.
Prestige 660ME-61 Main Menu
Getting Started Advanced Management
1. General Setup 21. Filter Set Configuration
2. WAN Backup Setup 22. SNMP Configuration
3. LAN Setup 23. System Password
4. Internet Access Setup 24. System Maintenance
25. IP Routing Policy Setup
Advanced Applications 26. Schedule Setup
11. Remote Node Setup
12. Static Routing Setup
15. NAT Setup 99. Exit
Enter Menu Selection Number:

 

* Select menu option "8. Command Interpreter Mode" from the menu

Menu 24 - System Maintenance
1. System Status
2. System Information and Console Port Speed
3. Log and Trace
4. Diagnostic
5. Backup Configuration
6. Restore Configuration
7. Upload Firmware
8. Command Interpreter Mode
9. Call Control
10. Time and Date Setting
11. Remote Management
Enter Menu Selection Number:

* At the prompt type "ip nat loopback on".

Copyright (c) 1994 - 2004 ZyXEL Communications Corp.
Sprint > ip nat loopback on

* At the prompt type "exit".

Sprint> exit

* Select menu option "99. Exit"

* Follow all other steps for configuring and starting your server as outlined in [[Main Page#Getting Started with OpenSim|Getting Started]].

 

=== Local connections with the DLink GamerLounge Extreme N router ===

Networking and router configurations have been responsible for 98% of all trouble I have had setting up and operating OpenSimulator region server software. Insuring that you have a capable router properly configured should be the first thing on the list of configuration checkpoints for a smooth and trouble-free path to OpenSimulator software operations in GridMode.

Below is a series of screen snapshots with the key pages of my router configuration interface with proper settings displayed.

The settings below assume that you have an otherwise working connection and do not touch on such subjects as port conflicts or logging your network onto your ISP's provider network.

{| class="FCK__ShowTableBorders"
|-
| [[Image:Router config snapshot1.png|thumb|250px|1.Status]]
| [[Image:Router config snapshot2.png|thumb|250px|2.Advanced > Gaming]]
| [[Image:Router config snapshot3.png|thumb|250px|3.Routing]]
|}

{| class="FCK__ShowTableBorders"
|-
| [[Image:Router config snapshot4.png|thumb|250px|4.firewall]]
| [[Image:Router config snapshot5.png|thumb|250px|5.Advanced network settings]]
|}

* provided that all information supplied in ~opensim/bin/OpenSim.ini and in your ~opensim/Regions/*.xml are properly configured, this should have you up and running.

 

===Local and Internet connections with Linux iptables and NAT/Port Forwarding=== Please don't copy this verbatim - much more should go into a firewall setup, but this will at a bare minimum get NAT working with forwarding to your OpenSimulator server from both inside and outside your LAN.

Example firewall.sh script: <source lang="bash">
echo 1 > /proc/sys/net/ipv4/ip_forward
echo 1 > /proc/sys/net/netfilter/nf_conntrack_tcp_be_liberal
echo 0 > /proc/sys/net/ipv4/conf/all/accept_redirects
echo 0 > /proc/sys/net/ipv4/conf/all/accept_source_route
echo 0 > /proc/sys/net/ipv4/conf/all/send_redirects
echo 1 > /proc/sys/net/ipv4/conf/all/log_martians
echo 1 > /proc/sys/net/ipv4/conf/all/rp_filter
modprobe nf_conntrack_ftp
modprobe nf_nat_ftp

INT = "eth0" # your internal network card on the firewall
EXT = "eth1" # Your external network card on the firewall
IPTABLES = "/sbin/iptables" # Path to your iptables executable

OPENSIMEXT = "66.102.1.103/32" # Example external IP - replace with yours
OPENSIMINT = "192.168.1.240/32" # Internal IP of your OpenSimulator server
INTSUBNET = "192.168.1.0/24" # Your internal subnet range

# Flush rules when we are restarting the script
$IPTABLES -F
$IPTABLES -F -t nat
$IPTABLES -F -t mangle

# Set up sane defaults
$IPTABLES -P INPUT DROP
$IPTABLES -P OUTPUT ACCEPT
$IPTABLES -P FORWARD DROP

# Allow all connections from inside the network to the firewall on all ports
$IPTABLES -A INPUT -i $INT -j ACCEPT
# Allow all outbound connections from the inside. Much better to limit this...
$IPTABLES -A FORWARD -o $EXT -j ACCEPT

# Configure basic NAT
$IPTABLES -A FORWARD -i $EXT -m state --state RELATED,ESTABLISHED -j ACCEPT
$IPTABLES -t nat -A POSTROUTING -o $EXT -j SNAT --to-source $OUTNAT

# Configure forwarding for OpenSimulator (you need to add ports if you are not running in standalone
# or if you are running more than one region)
$IPTABLES -A PREROUTING -p tcp -d $OPENSIMEXT --dport 9000 -j DNAT --to-destination $OPENSIMINT
$IPTABLES -A PREROUTING -p udp -d $OPENSIMEXT --dport 9000 -j DNAT --to-destination $OPENSIMINT

# Now for the magical juice that lets inside users and outside users both access your server
# Configure to allow internal network users to access the OpenSimulator server using the
# external IP address. This fixes failing to connect to regions over UDP due to NAT config
# Make sure you configure the proper external IP for each of your regions
$IPTABLES -t nat -A PREROUTING -i $INT -s $INTSUBNET -d $OPENSIMEXT -j DNAT --to-destination $OPENSIMINT
$IPTABLES -t nat -A POSTROUTING -o $INT -s $INTSUBNET -d $OPENSIMINT -j DNAT --to-source $OPENSIMEXT

</source>

 

NOTE: Contrary to what is displayed above, DHCP services are not required to operate OpenSimulator server software.

 

== NAT LoopBack Routers Listings ==

[[NAT Loopback Routers|opensimulator.org/wiki/NAT_Loopback_Routers]]

== Historical - OpenSimulator Grid - Ports for Grid Services - up to version 0.6.9 ==

Note this is no longer the current version...

* TCP/8000 - Reserved
* TCP/8001 - Grid Server - Regions and other grid services talk to this
* TCP/8002 - User Server and Login Services - Clients, Regions, and other grid services talk to this
* TCP/8003 - Asset Services - Regions and other grid services talk to this
* TCP/8004 - Inventory Services - Regions and other grid services talk to this
* TCP/8005 - Reserved (Dispatch Services)
* TCP/8006 - Messaging Server
* TCP/8895 - Used in early releases for region-to-region communications

== VMware VMXNET3 NIC Issue ==

When running OpenSimulator in a 64-bit CentOS 6 VM under VMware ESXi 5, with the latest VMware Tools installed, and using the VMXNET3 vNIC, I (smxy) found that my viewer would consistently be disconnected from my grid at approximately 12 minutes after connecting (with the child agents dying sooner, as evidenced by regions turning red in the mini-map), with ACK timeouts reported at the region consoles. This behavior was 100% repeatable. I discovered that deleting the VMXNET3 vNIC and replacing it with the E1000 vNIC (and maintaining the same MAC address) eliminated the problem completely.

A few weeks later, I noticed someone (LilinEnyo) reporting ACK timeouts, in IRC. It turns out she was running "ubuntu 64bit" under ESXi 5, with VMware tools installed and using the VMXNET3 vNIC. In her case, the ACK timeouts were disconnecting her viewer at approximately 5 minutes after connecting. I had her switch to the E1000 vNIC and it eliminated the issue for her, too.

[[Category:Users]]

NAT Loopback Routers

2012-10-25T19:31:56Z

Arielle: /* Windows XP Work Around: */

{{Quicklinks}} {{content}}

= INTRODUCTION =

What is NAT Loopback and why is it needed to host a public Opensimulator Region?

Currently (as at August 2010), a hosted region on a home connection with a broadband router needs, what is known as ''NAT Loopback'' functionality.

Many DSL routers/modems prevent loopback connections as a security feature. This means that a machine on your local network (e.g. behind your DSL router/modem) cannot connect to a forward facing IP address (such as 199.149.252.44) of a machine that it also on your local network. Connecting to the local IP address (such as 192.168.2.40) of that same machine works fine.

This is an issue since each region has to be specify an IP address for the client to connect. This is the ExternalHostName parameter in a regions config file (e.g. bin/Regions/Regions.ini). In the absence of NAT loopback, if a forward facing IP address is specified (such as 199.149.252.44) then external clients will be able to connect to the region but clients on your local network will not. If the internal address were put in ExternalHostName instead (e.g. 192.168.2.40) then viewers on the local network will be able to connect but viewers from an external network would not.

This page shows a list of routers supporting NAT Loopback. Please add both known working and non-working routers to the list.

= Working Routers =

== 3Com ==

* 3CRWDR100A-72
* 3CRWDR101A-75

== D-Link ==

D-Link DGL-4500 series of routers have the largest available nat table of any router on the market.  These routers range from 70$-180$ USD depending on where you live and purchase from.

When considering a purchase, consider performance against cost. Upper end ADSL 2+ routers can add several Mbs to your modems sync speed.

'''Wireless Routers - Access Point Only'''

These routers are Access Point devices, and contain no ADSL modem and hence need a separate adsl modem operating in Bridge mode.

* [http://www.dlink.com/products/?pid=64 D-Link DGL-4500]
* [http://www.dlink.com/products/?pid=530 D-Link DIR-655]
* [http://www.dlink.com/products/?pid=DIR-635 D-Link DIR-635]
* [http://www.dlink.com/products/?pid=DIR-601 D-Link DIR-601]
* [http://www.dlink.com/products/?pid=DIR-600 D-Link DIR-600]
* D-Link DI-524

'''Routers With ADSL modem'''
No items to list currently

Note: The DGL-4100 & DGL-4300 have been discontinued, and the replacement model is the DIL-825 and DIL-855 - Loopback status unknown on these later models. The DGL-4300 may be available second hand.

== Draytek ==

* Draytek Vigor 2710n [http://www.draytek.com/user/PdInfoDetail.php?Id=82] does NAT loopback out of the box and seems to be generally an all-round great router.
* Draytek Vigor 120 [http://www.draytek.com/user/PdInfoDetail.php?Id=71] does NAT loopback out of the box and has some nice features. NOTE that if it's using PPPoA (common in UK and New Zealand) there is a bug that stops Opensim (and Secondlife) ping packets from working so you disconnect after 3 minutes. You need to upgrade to firmware 3.2.4.3 (or higher).

== Linksys/Cisco ==

* [http://www.linksysbycisco.com/EU/en/support/WAG200G Linksys WAG200G] with Firmware Version: 1.01.09
* [http://en.wikipedia.org/wiki/Linksys_WRT54G_series Linksys WRT54G]
* [http://homesupport.cisco.com/en-us/wireless/lbc/WAG54G Linksys WAG54G v3]
* [http://homesupport.cisco.com/en-us/wireless/lbc/WAG54G Linksys WAG54G v2 - NZ/Australia version]
* Linksys RT31P2
Note: The WAG54G v2 NZ/Australia version has a faster processor, more memory and larger NAT table, and works with OS out of the box. Other market versions may not.

WAG120N Linksys Wireless-N ADSL2+ Modem Router (Australia)

== Netgear ==

* NETGEAR WNR834M : ftp://downloads.netgear.com/files/wnr834m_ref_manual.pdf
* NETGEAR WNR2000 : With firmware 1.2.3.7 ( http://kb.netgear.com/app/answers/detail/a_id/11895 ) loopback now enabled 'out of the box'
* NETGEAR WGR614 : has been confirmed to work out of the box
* Netgear RP614 v3
* Netgear DG834G v3 with latest firmware & v4 upto firmware version v5.01.09 (according to [http://forum1.netgear.com/showthread.php?t=42641 this link], a later firmware update of v4 removed NAT loopback) NAT Loopback returned as menu option with latest v5.01.16 firmware for the v4 model. The latest model versions, marked v5 on the unit's label, has significantly different internals and is not currently Loopback capable(the v5 has the wireless aerial on the right, not the left, as looking from the front. The DG834G v1, v2, v3 & v4 are end of line in most markets. The v3 & v4 are proven good performers.
* Netgear DGN1000 worked out of the box. Note this working item reports its firmware version as V2.1.00.19_VG which seems much newer than the version offered for download on netgear.com.
* NETGEAR FVS338 : loopback issue with firmware v3.0.3-17 (2008). LAN address is incorrectly presented to simulator instead of WAN address. Fixed in latest update v3.0.6-25 (2010).

== Thomson ==

* Thomson SpeedTouch router-modem TG585, ST-585i (requires Telnet acces to it to Enable Loopback)
* Thomson Speedtouch ST-780, ST-516

== Other routers & Hardware ==

* Arris TM502b : http://portforward.com/english/routers/port_forwarding/Arris/TM502b/
* 2wire 2701hg-s NOT Loopback capable. but the 2wire 2701hg-B & 2701hg-D Series ARE loopback capable.  (These can be purchased for approximately $50 USD)
* AVM FritzBox (most Models are working perfect, '''except 3790 VDSL Router''', Date Sep 2010) : http://www.avm.de
* Ubee Wireless Cable Router DDW2600  [http://www.ubeeinteractive.com/index.php/products/product-overview/wireless_cable_router1/ http://www.ubeeinteractive.com/index.php/products/product-overview/wireless_cable_router1/]
* BT home hub V2
* If you are using a ZyXEL DSL router/modem from Embarq, please read [[OpenSim:Network_settings#A_solution_for_local_connections_when_you_are_using_NAT_and_Port_Forwarding|this configuration guide]]. This will show you how to reconfigure your DSL router/modem to fix this problem.

= KNOWN non-functional for OpenSim: =

* Netgear Pro Safe VPN FVS318 : [http://www.netgear.com/Products/VPNandSSL/WiredVPNFirewallRouters/FVS318.aspx http://www.netgear.com/Products/VPNandSSL/WiredVPNFirewallRouters/FVS318.aspx]
* NetGear WGR614 does not work with ISP required gateway modems
* Belkin F5D7230-4 (the router might work if 3rd party firmware is used, such as DD-WRT : http://www.dd-wrt.com/ )

 

= REFERENCE LINKS: =

More Information Related to Routers and Solutions @: [http://osgrid.org/forums/viewtopic.php?f=8&t=2283 osgrid.org/forums/viewtopic.php]

= Router/Modem Table =
==== Router / Modem Table ====
(this information gathered from the OpenSimulator WIKI and OSGrid forums information collectively and assembled into this sortable formatted table for ease of use and quick access. Links provided are either to the Manufactures pages or Pages which can further assit in configuration and troubleshooting.)

{| cellspacing="0" cellpadding="5" border="1" align="centre" class="sortable"
|-
| '''Make''' || '''Model''' || '''Status''' || '''Notes'''
|-
| Belgacom BBox-2 || [http://support.en.belgacom.be/app/answers/detail/a_id/14453/~/how-to-install-and-manage-my-wireless-modem%3F BBox-2 Docs] || Works || Also known as [http://www.sagemcom.com/index.php?id=1226&L=0 SAGEM 3464]. BBox-1 work, BBox-2 = Method 1: flash the firmare (in this case we lose the guarantee provider) Method 2: Configure Bbox Bridge mode and put a second router for OpenSim-Sim.
|-
| Dlink || [http://www.dlink.com/products/?pid=DGL-4500 DGL-4500] || Works || [http://portforward.com/english/routers/port_forwarding/Dlink/DGL-4500/defaultguide.htm]
|-
| Dlink || [http://www.dlink.com/products/?pid=370 DGL-4300] || Works || [http://portforward.com/english/routers/port_forwarding/Dlink/DGL-4300/defaultguide.htm]
|-
| Dlink || [http://www.dlink.ca/products/?tab=3&pid=DI-524&rev=DI-524 DI-524] || Works || [http://portforward.com/english/routers/port_forwarding/Dlink/DI-524/defaultguide.htm]
|-
| Dlink || [http://www.dlink.com/products/?pid=DIR-600 DIR-600] || Works || [http://portforward.com/english/routers/port_forwarding/Dlink/DIR-600/defaultguide.htm]
|-
| Dlink || [http://www.dlink.com/products/?pid=DIR-601 DIR-601] || Works || [http://portforward.com/english/routers/port_forwarding/Dlink/DIR-601/defaultguide.htm]
|-
| Dlink || [http://www.dlink.com/products/?pid=DIR-635 DIR-635] || Works || [http://portforward.com/english/routers/port_forwarding/Dlink/DIR-635/defaultguide.htm]
|-
| Dlink || [http://www.dlink.com/products/?pid=DIR-655 DIR-655] || Works || [http://portforward.com/english/routers/port_forwarding/Dlink/DIR-655/defaultguide.htm]
|-
| Draytek || [http://www.draytek.com/user/PdInfoDetail.php?Id=71 Vigor120] || Works ||
|-
| Draytek || [http://www.draytek.com/user/PdInfoDetail.php?Id=82 Vigor2710] || Works || [http://portforward.com/english/routers/port_forwarding/DrayTek/Vigor_2710n/defaultguide.htm] firmware 3.2.4.3 (or higher).
|-
| Netgear || WNR834M || Works ||
|-
| Netgear || WNR2000 || Works || With firmware 1.2.3.7 Loop back now enabled 'out of the box'
|-
| Netgear || WGR614 || Works || confirmed to work out of the box
|-
| Netgear || RP614 || Works || Version 3 or better
|-
| Netgear || DG834G || Works || v1, v2, v3 & v4 are end of line in most markets. The v3 & v4 are proven good performers.
|-
| Linksys/Cisco || RT31P2 || Works || [http://portforward.com/english/routers/port_forwarding/Linksys/RT31P2/defaultguide.htm]
|-
| Linksys/Cisco || [http://www.linksysbycisco.com/APAC/en/support/AG241 AG241] || Works || [http://portforward.com/english/routers/port_forwarding/Linksys/AG241/defaultguide.htm]
|-
| Linksys/Cisco || [http://www.linksysbycisco.com/EU/en/support/WAG200G WAG200G] || Works || [http://portforward.com/english/routers/port_forwarding/Linksys/WAG200G/default.htm] Firmware Version: 1.01.09 or better
|-
| Linksys/Cisco || [http://en.wikipedia.org/wiki/Linksys_WRT54G_series WRT54G] || Works || [http://portforward.com/english/routers/port_forwarding/Linksys/WRT54G/default.htm]
|-
| Linksys/Cisco || [http://www.linksysbycisco.com/ANZ/en/products/WAG160N WAG160N] || Works || [http://portforward.com/english/routers/port_forwarding/Linksys/WAG160N/default.htm]
|-
| Linksys/Cisco || [http://homesupport.cisco.com/en-us/wireless/lbc/WAG54G WAG54G v3] || Works ||
|-
| Linksys/Cisco || [http://www.linksysbycisco.com/ANZ/en/products/E3000 E3000] || Works || [http://portforward.com/english/routers/port_forwarding/Cisco/Linksys-E3000/default.htm]
|-
| Linksys/Cisco || [http://homesupport.cisco.com/en-us/wireless/lbc/WAG54G WAG54G v2 - NZ/AU] || Works ||
|-
| 3Com / HP || 3CRWDR100A-72 || Works || [http://portforward.com/english/routers/port_forwarding/3com/3CRWDR100A-72/default.htm]
|-
| 3Com / HP || 3CRWDR101A-75 || Works || [http://portforward.com/english/routers/port_forwarding/3com/3CRWDR101A-75/eMule.htm]
|-
| Arris || TM502b || Works || [http://portforward.com/english/routers/port_forwarding/Arris/TM502b/]
|-
| 2wire || 2701hg-s || Not Working ||
|-
| 2wire || 2701hg-B || Works || [http://portforward.com/english/routers/port_forwarding/2wire/2701HG-B/default.htm]
|-
| 2wire || 2701hg-D || Works || [http://portforward.com/english/routers/port_forwarding/2wire/2701HG-D/default.htm]
|-
| Thomson SpeedTouch || TG585 || Works || [http://portforward.com/english/routers/port_forwarding/Thomson-Alcatel/SpeedTouch585/default.htm] new ver. Only
|-
| Thomson SpeedTouch || ST-585i || Works || [http://portforward.com/english/routers/port_forwarding/Thomson-Alcatel/SpeedTouch585i/default.htm]
|-
| Thomson SpeedTouch || ST-780 || Works || [http://portforward.com/english/routers/port_forwarding/Thomson-Alcatel/ST780/default.htm]
|-
| Thomson SpeedTouch || ST-516 || Works || [http://portforward.com/english/routers/port_forwarding/Thomson-Alcatel/SpeedTouch516/default.htm]
|-
| AVM || FRITZ!Box || Works || [http://www.avm.de/en/Produkte/FRITZBox/index.html] Except 3790 VDSL Router (old stock)
|-
| Ubee || DDW2600 || Works || [http://www.ubeeinteractive.com/index.php/products/product-overview/wireless_cable_router1/] Cable Router
|-
| BT || BT Home Hub V2 || Works || [http://portforward.com/english/routers/port_forwarding/BT/BT_Home_Hub_v2/defaultguide.htm]
|-
| BT || BT2700HGV || Works || [ http://portforward.com/english/routers/port_forwarding/BT/BT2700HGV/defaultguide.htm]
|-
| Netgear || Pro Safe VPN FVS318 || Not Working || [http://www.netgear.com/service-provider/products/security/wired-VPN-firewalls/FVS318.aspx#two]
|-
| Netgear || WGR614 || Not Working || [http://www.netgear.com/home/products/wirelessrouters/simplesharing/WGR614.aspx] does not work with ISP required gateway modems
|-
| Asus || [http://www.asus.com/Networks/Wireless_Routers/WL520gC/ WL-520GC] || Works || [http://portforward.com/english/routers/port_forwarding/Asus/WL-520GC/defaultguide.htm]
|-
| SMC || [http://www.smc.com/index.cfm?event=viewProduct&cid=1&scid=17&localeCode=EN%5FUSA&pid=924 SMC-7004VBR] || Works || [http://portforward.com/english/routers/port_forwarding/SMC/SMC7004ABR/defaultguide.htm]
|-
| Inventel / Livebox || DV42190WA || Works || Sold as Livebox 3420 by Orange/SFR in Europe. Set port forwarding for UDP and TCP separately
|-
| Linksys/Cisco || [http://homesupport.cisco.com/en-us/wireless/lbc/BEFSR41/ BEFSR41] || Works || [http://portforward.com/english/routers/port_forwarding/Linksys/BEFSR41/defaultguide.htm]
|-
| Netgear || [http://support.netgear.com/app/products/family/a_id/8213 WNR3500 ] || Works || [http://portforward.com/english/routers/port_forwarding/Netgear/WNR3500/defaultguide.htm] NB restart after configuration
|-
| Apple || [http://www.apple.com/airportextreme/ AirPort Extreme] || Works ||
|-
| Airlink || Airlink 101 Super G || Works || older model, search for reference
|-
| Airlink || Airlink 101 802.11G wireless || Works || older model, search for reference
|-
| Netgear || RP614v3 and Newer revisions || Works || [http://portforward.com/english/routers/port_forwarding/Netgear/RP614v3/defaultguide.htm]
|-
| Actiontec || [http://www.actiontec.com/products/product.php?pid=189 Verizon FiOS Router Model # 424WR] || Works || [http://www.actiontec.com/support/product_details.php?pid=189#q23] Set TCP and UDP separately
|-
| Netgear || [http://www.netgear.com/home/products/wirelessrouters/high-performance/WNDR3700.aspx WNDR3700] || Works || [http://portforward.com/english/routers/port_forwarding/Netgear/WNDR3700/default.htm]
|-
| Actiontec || [http://www.actiontec.com/support/product_details.php?pid=71 GT701-WG] || Works || [http://portforward.com/english/routers/port_forwarding/Actiontec/GT701WG/default.htm]
|-
| Cisco || [http://www.cisco.com/en/US/products/ps9925/index.html RV042] || Works ||
|-
| Scientific Atlanta || WebSTAR-DPR2320 || Works || [http://portforward.com/english/routers/port_forwarding/Scientific-Atlanta/WebSTAR-DPR2320/default.htm] Google for more info
|-
|}

= Linux specific solutions =
== SETTING UP A LINUX COMPUTER TO ACT AS A ROUTER ==

----

For Linux based Netfilter (iptables) routers, you want to set up the NAT table with some extra entries The following script is something to get you started, you'll need to fix up the variables at the top to match your system and network. <source lang="bash">
#!/bin/bash
#
# vvvvv - Fix these! - vvvvv
IPTABLES=/usr/sbin/iptables
LAN_NETWORK=192.168.0.0/24
SERVER_IP=192.168.0.2
INTERNET_IP=100.100.100.100
REMOTING_PORT=8895
REGION_PORT=9000
# ^^^^^ - Fix these! - ^^^^^

# First, the Destination NAT, anything going to the external address on our ports, we redirect to the server
# Note, if you have a double NAT running and this router doesn't actually have the internet IP address, you'll
# need another set of PREROUTING-DNAT lines with the --destination (-d) set to the internet facing private address
$IPTABLES -t nat -I PREROUTING -d $INTERNET_IP -p tcp --dport $REMOTING_PORT --jump DNAT --to-destination $SERVER_IP
$IPTABLES -t nat -I PREROUTING -d $INTERNET_IP -p udp --dport $REGION_PORT --jump DNAT --to-destination $SERVER_IP
$IPTABLES -t nat -I PREROUTING -d $INTERNET_IP -p tcp --dport $REGION_PORT --jump DNAT --to-destination $SERVER_IP

# Second, the Source NAT, we need this so that returning packets to our LAN clients go back through the router first,
# otherwise, the server will try to talk directly to the client and the client will reject them
$IPTABLES -t nat -I POSTROUTING -s $LAN_NETWORK -d $SERVER_IP -p tcp --dport $REMOTING_PORT --jump SNAT --to-source $INTERNET_IP
$IPTABLES -t nat -I POSTROUTING -s $LAN_NETWORK -d $SERVER_IP -p udp --dport $REGION_PORT --jump SNAT --to-source $INTERNET_IP
$IPTABLES -t nat -I POSTROUTING -s $LAN_NETWORK -d $SERVER_IP -p tcp --dport $REGION_PORT --jump SNAT --to-source $INTERNET_IP
</source>

--[[User:Hell Fire|Hell Fire]]

== DNS solution ==
It's possible to host your own DNS-server, so you can prevent some of the dns-naming problems mentioned before. If http://example.org resolves to the external ip, and that loopback connection is prevented by your router, you could point your resolv.conf to a local nameserver like:
nameserver 192.168.2.2
Now you need bind/named installed in order to handle the dns-requests. You can find a bind example configfile here.

= openWRT Routers: =

If you use openWRT firmware on your router, check here: [[Users:Thomax:nat-loopback|OpenWRT NATLoopback]]

= Windows XP and Windows 7 Work Around: =

Please see this -> Windows XP: http://help.newworldgrid.com/lang/en/loopback-adapter-on-windows-xp

Windows 7: http://help.newworldgrid.com/lang/en/loopback-windows

[[Category:Hardware]]

NAT Loopback Routers

2012-10-25T19:30:15Z

Arielle: Updating links to loopback adapter tutorials

{{Quicklinks}} {{content}}

= INTRODUCTION =

What is NAT Loopback and why is it needed to host a public Opensimulator Region?

Currently (as at August 2010), a hosted region on a home connection with a broadband router needs, what is known as ''NAT Loopback'' functionality.

Many DSL routers/modems prevent loopback connections as a security feature. This means that a machine on your local network (e.g. behind your DSL router/modem) cannot connect to a forward facing IP address (such as 199.149.252.44) of a machine that it also on your local network. Connecting to the local IP address (such as 192.168.2.40) of that same machine works fine.

This is an issue since each region has to be specify an IP address for the client to connect. This is the ExternalHostName parameter in a regions config file (e.g. bin/Regions/Regions.ini). In the absence of NAT loopback, if a forward facing IP address is specified (such as 199.149.252.44) then external clients will be able to connect to the region but clients on your local network will not. If the internal address were put in ExternalHostName instead (e.g. 192.168.2.40) then viewers on the local network will be able to connect but viewers from an external network would not.

This page shows a list of routers supporting NAT Loopback. Please add both known working and non-working routers to the list.

= Working Routers =

== 3Com ==

* 3CRWDR100A-72
* 3CRWDR101A-75

== D-Link ==

D-Link DGL-4500 series of routers have the largest available nat table of any router on the market.  These routers range from 70$-180$ USD depending on where you live and purchase from.

When considering a purchase, consider performance against cost. Upper end ADSL 2+ routers can add several Mbs to your modems sync speed.

'''Wireless Routers - Access Point Only'''

These routers are Access Point devices, and contain no ADSL modem and hence need a separate adsl modem operating in Bridge mode.

* [http://www.dlink.com/products/?pid=64 D-Link DGL-4500]
* [http://www.dlink.com/products/?pid=530 D-Link DIR-655]
* [http://www.dlink.com/products/?pid=DIR-635 D-Link DIR-635]
* [http://www.dlink.com/products/?pid=DIR-601 D-Link DIR-601]
* [http://www.dlink.com/products/?pid=DIR-600 D-Link DIR-600]
* D-Link DI-524

'''Routers With ADSL modem'''
No items to list currently

Note: The DGL-4100 & DGL-4300 have been discontinued, and the replacement model is the DIL-825 and DIL-855 - Loopback status unknown on these later models. The DGL-4300 may be available second hand.

== Draytek ==

* Draytek Vigor 2710n [http://www.draytek.com/user/PdInfoDetail.php?Id=82] does NAT loopback out of the box and seems to be generally an all-round great router.
* Draytek Vigor 120 [http://www.draytek.com/user/PdInfoDetail.php?Id=71] does NAT loopback out of the box and has some nice features. NOTE that if it's using PPPoA (common in UK and New Zealand) there is a bug that stops Opensim (and Secondlife) ping packets from working so you disconnect after 3 minutes. You need to upgrade to firmware 3.2.4.3 (or higher).

== Linksys/Cisco ==

* [http://www.linksysbycisco.com/EU/en/support/WAG200G Linksys WAG200G] with Firmware Version: 1.01.09
* [http://en.wikipedia.org/wiki/Linksys_WRT54G_series Linksys WRT54G]
* [http://homesupport.cisco.com/en-us/wireless/lbc/WAG54G Linksys WAG54G v3]
* [http://homesupport.cisco.com/en-us/wireless/lbc/WAG54G Linksys WAG54G v2 - NZ/Australia version]
* Linksys RT31P2
Note: The WAG54G v2 NZ/Australia version has a faster processor, more memory and larger NAT table, and works with OS out of the box. Other market versions may not.

WAG120N Linksys Wireless-N ADSL2+ Modem Router (Australia)

== Netgear ==

* NETGEAR WNR834M : ftp://downloads.netgear.com/files/wnr834m_ref_manual.pdf
* NETGEAR WNR2000 : With firmware 1.2.3.7 ( http://kb.netgear.com/app/answers/detail/a_id/11895 ) loopback now enabled 'out of the box'
* NETGEAR WGR614 : has been confirmed to work out of the box
* Netgear RP614 v3
* Netgear DG834G v3 with latest firmware & v4 upto firmware version v5.01.09 (according to [http://forum1.netgear.com/showthread.php?t=42641 this link], a later firmware update of v4 removed NAT loopback) NAT Loopback returned as menu option with latest v5.01.16 firmware for the v4 model. The latest model versions, marked v5 on the unit's label, has significantly different internals and is not currently Loopback capable(the v5 has the wireless aerial on the right, not the left, as looking from the front. The DG834G v1, v2, v3 & v4 are end of line in most markets. The v3 & v4 are proven good performers.
* Netgear DGN1000 worked out of the box. Note this working item reports its firmware version as V2.1.00.19_VG which seems much newer than the version offered for download on netgear.com.
* NETGEAR FVS338 : loopback issue with firmware v3.0.3-17 (2008). LAN address is incorrectly presented to simulator instead of WAN address. Fixed in latest update v3.0.6-25 (2010).

== Thomson ==

* Thomson SpeedTouch router-modem TG585, ST-585i (requires Telnet acces to it to Enable Loopback)
* Thomson Speedtouch ST-780, ST-516

== Other routers & Hardware ==

* Arris TM502b : http://portforward.com/english/routers/port_forwarding/Arris/TM502b/
* 2wire 2701hg-s NOT Loopback capable. but the 2wire 2701hg-B & 2701hg-D Series ARE loopback capable.  (These can be purchased for approximately $50 USD)
* AVM FritzBox (most Models are working perfect, '''except 3790 VDSL Router''', Date Sep 2010) : http://www.avm.de
* Ubee Wireless Cable Router DDW2600  [http://www.ubeeinteractive.com/index.php/products/product-overview/wireless_cable_router1/ http://www.ubeeinteractive.com/index.php/products/product-overview/wireless_cable_router1/]
* BT home hub V2
* If you are using a ZyXEL DSL router/modem from Embarq, please read [[OpenSim:Network_settings#A_solution_for_local_connections_when_you_are_using_NAT_and_Port_Forwarding|this configuration guide]]. This will show you how to reconfigure your DSL router/modem to fix this problem.

= KNOWN non-functional for OpenSim: =

* Netgear Pro Safe VPN FVS318 : [http://www.netgear.com/Products/VPNandSSL/WiredVPNFirewallRouters/FVS318.aspx http://www.netgear.com/Products/VPNandSSL/WiredVPNFirewallRouters/FVS318.aspx]
* NetGear WGR614 does not work with ISP required gateway modems
* Belkin F5D7230-4 (the router might work if 3rd party firmware is used, such as DD-WRT : http://www.dd-wrt.com/ )

 

= REFERENCE LINKS: =

More Information Related to Routers and Solutions @: [http://osgrid.org/forums/viewtopic.php?f=8&t=2283 osgrid.org/forums/viewtopic.php]

= Router/Modem Table =
==== Router / Modem Table ====
(this information gathered from the OpenSimulator WIKI and OSGrid forums information collectively and assembled into this sortable formatted table for ease of use and quick access. Links provided are either to the Manufactures pages or Pages which can further assit in configuration and troubleshooting.)

{| cellspacing="0" cellpadding="5" border="1" align="centre" class="sortable"
|-
| '''Make''' || '''Model''' || '''Status''' || '''Notes'''
|-
| Belgacom BBox-2 || [http://support.en.belgacom.be/app/answers/detail/a_id/14453/~/how-to-install-and-manage-my-wireless-modem%3F BBox-2 Docs] || Works || Also known as [http://www.sagemcom.com/index.php?id=1226&L=0 SAGEM 3464]. BBox-1 work, BBox-2 = Method 1: flash the firmare (in this case we lose the guarantee provider) Method 2: Configure Bbox Bridge mode and put a second router for OpenSim-Sim.
|-
| Dlink || [http://www.dlink.com/products/?pid=DGL-4500 DGL-4500] || Works || [http://portforward.com/english/routers/port_forwarding/Dlink/DGL-4500/defaultguide.htm]
|-
| Dlink || [http://www.dlink.com/products/?pid=370 DGL-4300] || Works || [http://portforward.com/english/routers/port_forwarding/Dlink/DGL-4300/defaultguide.htm]
|-
| Dlink || [http://www.dlink.ca/products/?tab=3&pid=DI-524&rev=DI-524 DI-524] || Works || [http://portforward.com/english/routers/port_forwarding/Dlink/DI-524/defaultguide.htm]
|-
| Dlink || [http://www.dlink.com/products/?pid=DIR-600 DIR-600] || Works || [http://portforward.com/english/routers/port_forwarding/Dlink/DIR-600/defaultguide.htm]
|-
| Dlink || [http://www.dlink.com/products/?pid=DIR-601 DIR-601] || Works || [http://portforward.com/english/routers/port_forwarding/Dlink/DIR-601/defaultguide.htm]
|-
| Dlink || [http://www.dlink.com/products/?pid=DIR-635 DIR-635] || Works || [http://portforward.com/english/routers/port_forwarding/Dlink/DIR-635/defaultguide.htm]
|-
| Dlink || [http://www.dlink.com/products/?pid=DIR-655 DIR-655] || Works || [http://portforward.com/english/routers/port_forwarding/Dlink/DIR-655/defaultguide.htm]
|-
| Draytek || [http://www.draytek.com/user/PdInfoDetail.php?Id=71 Vigor120] || Works ||
|-
| Draytek || [http://www.draytek.com/user/PdInfoDetail.php?Id=82 Vigor2710] || Works || [http://portforward.com/english/routers/port_forwarding/DrayTek/Vigor_2710n/defaultguide.htm] firmware 3.2.4.3 (or higher).
|-
| Netgear || WNR834M || Works ||
|-
| Netgear || WNR2000 || Works || With firmware 1.2.3.7 Loop back now enabled 'out of the box'
|-
| Netgear || WGR614 || Works || confirmed to work out of the box
|-
| Netgear || RP614 || Works || Version 3 or better
|-
| Netgear || DG834G || Works || v1, v2, v3 & v4 are end of line in most markets. The v3 & v4 are proven good performers.
|-
| Linksys/Cisco || RT31P2 || Works || [http://portforward.com/english/routers/port_forwarding/Linksys/RT31P2/defaultguide.htm]
|-
| Linksys/Cisco || [http://www.linksysbycisco.com/APAC/en/support/AG241 AG241] || Works || [http://portforward.com/english/routers/port_forwarding/Linksys/AG241/defaultguide.htm]
|-
| Linksys/Cisco || [http://www.linksysbycisco.com/EU/en/support/WAG200G WAG200G] || Works || [http://portforward.com/english/routers/port_forwarding/Linksys/WAG200G/default.htm] Firmware Version: 1.01.09 or better
|-
| Linksys/Cisco || [http://en.wikipedia.org/wiki/Linksys_WRT54G_series WRT54G] || Works || [http://portforward.com/english/routers/port_forwarding/Linksys/WRT54G/default.htm]
|-
| Linksys/Cisco || [http://www.linksysbycisco.com/ANZ/en/products/WAG160N WAG160N] || Works || [http://portforward.com/english/routers/port_forwarding/Linksys/WAG160N/default.htm]
|-
| Linksys/Cisco || [http://homesupport.cisco.com/en-us/wireless/lbc/WAG54G WAG54G v3] || Works ||
|-
| Linksys/Cisco || [http://www.linksysbycisco.com/ANZ/en/products/E3000 E3000] || Works || [http://portforward.com/english/routers/port_forwarding/Cisco/Linksys-E3000/default.htm]
|-
| Linksys/Cisco || [http://homesupport.cisco.com/en-us/wireless/lbc/WAG54G WAG54G v2 - NZ/AU] || Works ||
|-
| 3Com / HP || 3CRWDR100A-72 || Works || [http://portforward.com/english/routers/port_forwarding/3com/3CRWDR100A-72/default.htm]
|-
| 3Com / HP || 3CRWDR101A-75 || Works || [http://portforward.com/english/routers/port_forwarding/3com/3CRWDR101A-75/eMule.htm]
|-
| Arris || TM502b || Works || [http://portforward.com/english/routers/port_forwarding/Arris/TM502b/]
|-
| 2wire || 2701hg-s || Not Working ||
|-
| 2wire || 2701hg-B || Works || [http://portforward.com/english/routers/port_forwarding/2wire/2701HG-B/default.htm]
|-
| 2wire || 2701hg-D || Works || [http://portforward.com/english/routers/port_forwarding/2wire/2701HG-D/default.htm]
|-
| Thomson SpeedTouch || TG585 || Works || [http://portforward.com/english/routers/port_forwarding/Thomson-Alcatel/SpeedTouch585/default.htm] new ver. Only
|-
| Thomson SpeedTouch || ST-585i || Works || [http://portforward.com/english/routers/port_forwarding/Thomson-Alcatel/SpeedTouch585i/default.htm]
|-
| Thomson SpeedTouch || ST-780 || Works || [http://portforward.com/english/routers/port_forwarding/Thomson-Alcatel/ST780/default.htm]
|-
| Thomson SpeedTouch || ST-516 || Works || [http://portforward.com/english/routers/port_forwarding/Thomson-Alcatel/SpeedTouch516/default.htm]
|-
| AVM || FRITZ!Box || Works || [http://www.avm.de/en/Produkte/FRITZBox/index.html] Except 3790 VDSL Router (old stock)
|-
| Ubee || DDW2600 || Works || [http://www.ubeeinteractive.com/index.php/products/product-overview/wireless_cable_router1/] Cable Router
|-
| BT || BT Home Hub V2 || Works || [http://portforward.com/english/routers/port_forwarding/BT/BT_Home_Hub_v2/defaultguide.htm]
|-
| BT || BT2700HGV || Works || [ http://portforward.com/english/routers/port_forwarding/BT/BT2700HGV/defaultguide.htm]
|-
| Netgear || Pro Safe VPN FVS318 || Not Working || [http://www.netgear.com/service-provider/products/security/wired-VPN-firewalls/FVS318.aspx#two]
|-
| Netgear || WGR614 || Not Working || [http://www.netgear.com/home/products/wirelessrouters/simplesharing/WGR614.aspx] does not work with ISP required gateway modems
|-
| Asus || [http://www.asus.com/Networks/Wireless_Routers/WL520gC/ WL-520GC] || Works || [http://portforward.com/english/routers/port_forwarding/Asus/WL-520GC/defaultguide.htm]
|-
| SMC || [http://www.smc.com/index.cfm?event=viewProduct&cid=1&scid=17&localeCode=EN%5FUSA&pid=924 SMC-7004VBR] || Works || [http://portforward.com/english/routers/port_forwarding/SMC/SMC7004ABR/defaultguide.htm]
|-
| Inventel / Livebox || DV42190WA || Works || Sold as Livebox 3420 by Orange/SFR in Europe. Set port forwarding for UDP and TCP separately
|-
| Linksys/Cisco || [http://homesupport.cisco.com/en-us/wireless/lbc/BEFSR41/ BEFSR41] || Works || [http://portforward.com/english/routers/port_forwarding/Linksys/BEFSR41/defaultguide.htm]
|-
| Netgear || [http://support.netgear.com/app/products/family/a_id/8213 WNR3500 ] || Works || [http://portforward.com/english/routers/port_forwarding/Netgear/WNR3500/defaultguide.htm] NB restart after configuration
|-
| Apple || [http://www.apple.com/airportextreme/ AirPort Extreme] || Works ||
|-
| Airlink || Airlink 101 Super G || Works || older model, search for reference
|-
| Airlink || Airlink 101 802.11G wireless || Works || older model, search for reference
|-
| Netgear || RP614v3 and Newer revisions || Works || [http://portforward.com/english/routers/port_forwarding/Netgear/RP614v3/defaultguide.htm]
|-
| Actiontec || [http://www.actiontec.com/products/product.php?pid=189 Verizon FiOS Router Model # 424WR] || Works || [http://www.actiontec.com/support/product_details.php?pid=189#q23] Set TCP and UDP separately
|-
| Netgear || [http://www.netgear.com/home/products/wirelessrouters/high-performance/WNDR3700.aspx WNDR3700] || Works || [http://portforward.com/english/routers/port_forwarding/Netgear/WNDR3700/default.htm]
|-
| Actiontec || [http://www.actiontec.com/support/product_details.php?pid=71 GT701-WG] || Works || [http://portforward.com/english/routers/port_forwarding/Actiontec/GT701WG/default.htm]
|-
| Cisco || [http://www.cisco.com/en/US/products/ps9925/index.html RV042] || Works ||
|-
| Scientific Atlanta || WebSTAR-DPR2320 || Works || [http://portforward.com/english/routers/port_forwarding/Scientific-Atlanta/WebSTAR-DPR2320/default.htm] Google for more info
|-
|}

= Linux specific solutions =
== SETTING UP A LINUX COMPUTER TO ACT AS A ROUTER ==

----

For Linux based Netfilter (iptables) routers, you want to set up the NAT table with some extra entries The following script is something to get you started, you'll need to fix up the variables at the top to match your system and network. <source lang="bash">
#!/bin/bash
#
# vvvvv - Fix these! - vvvvv
IPTABLES=/usr/sbin/iptables
LAN_NETWORK=192.168.0.0/24
SERVER_IP=192.168.0.2
INTERNET_IP=100.100.100.100
REMOTING_PORT=8895
REGION_PORT=9000
# ^^^^^ - Fix these! - ^^^^^

# First, the Destination NAT, anything going to the external address on our ports, we redirect to the server
# Note, if you have a double NAT running and this router doesn't actually have the internet IP address, you'll
# need another set of PREROUTING-DNAT lines with the --destination (-d) set to the internet facing private address
$IPTABLES -t nat -I PREROUTING -d $INTERNET_IP -p tcp --dport $REMOTING_PORT --jump DNAT --to-destination $SERVER_IP
$IPTABLES -t nat -I PREROUTING -d $INTERNET_IP -p udp --dport $REGION_PORT --jump DNAT --to-destination $SERVER_IP
$IPTABLES -t nat -I PREROUTING -d $INTERNET_IP -p tcp --dport $REGION_PORT --jump DNAT --to-destination $SERVER_IP

# Second, the Source NAT, we need this so that returning packets to our LAN clients go back through the router first,
# otherwise, the server will try to talk directly to the client and the client will reject them
$IPTABLES -t nat -I POSTROUTING -s $LAN_NETWORK -d $SERVER_IP -p tcp --dport $REMOTING_PORT --jump SNAT --to-source $INTERNET_IP
$IPTABLES -t nat -I POSTROUTING -s $LAN_NETWORK -d $SERVER_IP -p udp --dport $REGION_PORT --jump SNAT --to-source $INTERNET_IP
$IPTABLES -t nat -I POSTROUTING -s $LAN_NETWORK -d $SERVER_IP -p tcp --dport $REGION_PORT --jump SNAT --to-source $INTERNET_IP
</source>

--[[User:Hell Fire|Hell Fire]]

== DNS solution ==
It's possible to host your own DNS-server, so you can prevent some of the dns-naming problems mentioned before. If http://example.org resolves to the external ip, and that loopback connection is prevented by your router, you could point your resolv.conf to a local nameserver like:
nameserver 192.168.2.2
Now you need bind/named installed in order to handle the dns-requests. You can find a bind example configfile here.

= openWRT Routers: =

If you use openWRT firmware on your router, check here: [[Users:Thomax:nat-loopback|OpenWRT NATLoopback]]

= Windows XP Work Around: =

Please see this -> Windows XP: http://help.newworldgrid.com/lang/en/loopback-adapter-on-windows-xp
Windows 7: http://help.newworldgrid.com/lang/en/loopback-windows

[[Category:Hardware]]