Connecting

From OpenSimulator

(Difference between revisions)
Jump to: navigation, search
(Alternative Connection Approaches)
m (Obtaining OpenSimulator Available Viewers: Capitalisation and spacing only)
 
(32 intermediate revisions by 10 users not shown)
Line 1: Line 1:
 
__NOTOC__
 
__NOTOC__
{{Template:Quicklinks}}
 
<br />
 
==Compatible Viewers==
 
Before you can connect to OpenSim, you'll need to have downloaded one of the following clients that can connect to OpenSim.
 
  
* [http://get.secondlife.com Linden Client] (Release version 2 is '''not''' fully supported by OpenSim.)
+
{{Quicklinks|Connecting}}
* [http://mjm-labs.com/viewer/ Hippo Viewer] - a fork of version 1.23 of the Linden Client with OpenSim specific enhancements
+
* [[RealXtend]] - a fork of the 1.23 Linden Client that has specialized features (not fully supported.)
+
* [http://sldev.free.fr/ Cool VL Viewer] - one of the oldest Third Party Viewers around (former name: Cool SL Viewer), fully OpenSim compatible.
+
* [http://www.phoenixviewer.com/ Phoenix Viewer] Based on the now discontinued Emerald Viewer (which was based on the 1.23 LL viewer), one of the most popular viewers. Combines many improvements and  features from different viewers. (Not fully supported)
+
* [http://imprudenceviewer.org/ Imprudence] Innovative viewer with a high focus on OpenSimulator (good [[OSSL]] support). Highly popular amongst users on [[Grid_List/OSGrid|OSGrid]].
+
  
 +
== Obtaining OpenSimulator Available Viewers ==
  
===Other compatible viewers===
+
'''OpenSimulator does not come with a viewer in its distribution.'''
The viewers below are open source, and not based on the Snowglobe, nor on the Snowstorm viewers.
+
  
* [http://forge.opensimulator.org/gf/project/idealistviewer/ Idealist viewer], Not actively developed.
+
You'll need to download an OpenSimulator compatible client/viewer before connecting to OpenSimulator grids or regions.
* [http://lookingglassviewer.org/wiki/Main_Page/ Looking Glass viewer], Status active.
+
* [http://3di-rei.org/ 3Di viewer], Status unknown.
+
  
==Connecting with the Linden Viewer==
+
Please see [[Compatible Viewers]]
  
<span style="color:#ff0000;">'''***NOTE***''': These instructions apply to the Linden Labs viewer ONLY. Most other viewers have a more elegant method to choose a grid. See the documentation for those viewers for more information.</span>
+
* Note that some grids may prefer that you use a particular viewer (even a particular version) so follow that grid instructions.<br><br>
  
Every OpenSim grid or instance will specify a '''loginuri''', which is a uri of the form '''http://someserver:9000''' (standalone mode) or '''http://someserver:8002''' (grid mode).  For instance, for osgrid, this is http://login.osgrid.org.  The following sections assume that you have that uri.  We'll use http://login.osgrid.org as our example url.
+
== Connecting to the Grid with A Grid Selector (Recommended) ==
  
A list of major public grids can be found at [[Grid_List]]. OSGrid is just one of many available.
+
Most viewers have a grid selector which in many cases is already visible, and located at the bottom of the login screen. If it is not visible, try pressing Ctrl-Shift-G to (un)hide the grid selector.
  
=== Linux ===
+
=== If the grid is present in the list ===
* change directory to you viewer (SecondLife_XYZ)
+
If you see the grid you want to connect to in the grid selector, then simply choose it from the drop down menu, enter the username and password that you chose when you created your account on that grid, and click the "Log in" button.
* run <code>./secondlife -loginuri http://login.osgrid.org</code>
+
  
=== Windows ===
+
=== If the grid is missing from the list ===
* make a copy of the SecondLife icon on your desktop
+
If your preferred grid is not present in the drop down menu, then you will have to add it manually. You will have to do this only once.
* rename it to the grid you want to connect to
+
First, find the grid manager. Usually, this can be found in the preferences of your viewer, in a tab called "Grids". In general, the only fields that you will have to fill in are:
* edit the properties on the icon and set the command line to <code>...\SecondLife.exe" -loginuri http://login.osgrid.org</code>
+
  
=== Mac ===
+
* '''Grid Name''' (or alike) - A name you can easily identify the grid by. OpenSimulator grids don't use this information, so you can name it anything you like.
* Make a 'somefilename.sh' file, and put this in it:
+
* '''Login URI''' - The most important information. It should be like "<nowiki>http://someserver:9000" or "http://someserver". For instance, for OSGrid, this is "http://login.osgrid.org/".</nowiki>
* /Applications/Second\ Life.app/Contents/MacOS/Second\ Life -loginuri http://login.osgrid.org
+
* set it to executable
+
* run it
+
+
If you have multiple viewers and multiple grids to connect to, you can try the following AppleScript (one could do something similar with a shell script). Feel free to copy and modify for your own use.
+
--
+
--  This script selects a viewer and a grid for virtual worlds.
+
--
+
--
+
-- Variables for the two supported viewers.  More may be added here.
+
--
+
set lindenViewer to "\"/Applications/SecondLife/Second Life.app/Contents/MacOS/Second Life\""
+
+
set emeraldViewer to "\"/Applications/SecondLife/GreenLife Emerald Viewer.app/Contents/MacOS/GreenLife Emerald Viewer\""
+
--
+
-- Variables for options to select the specified grid.  Since the viewers
+
-- are based on the 2nd life viewer, the options are the same for each
+
-- viewer. Also, connecting to the Second Life grid is the default option
+
-- if no other options are provided.
+
--
+
-- Currently, four grids are supported.  More may be easily added.
+
--
+
set lindenOptions to ""
+
+
set localStandalone to " -loginuri http://vw.server.lan:9000 -loginpage http://vw.server.lan/opensim/index.html"
+
+
set localGrid to " -loginuri http://vw.server.lan:8000 -loginpage http://vw.server.lan/opensim/index.html"
+
+
set osGridOptions to " -loginuri http://osgrid.org:8002 -loginpage http://osgrid.org/loginscreen.php -helperuri http://osgrid.org/"
+
--
+
-- Display dialog and select the viewer.
+
--
+
set dialogResult to display dialog "Choose viewer:
+
1) 2nd Life viewer
+
2) Emerald viewer:" default answer "1" with title "Select Viewer" with icon 1
+
+
set option to text returned of dialogResult
+
+
if option = "2" then
+
set viewer to emeraldViewer
+
else
+
set viewer to lindenViewer
+
end if
+
--
+
-- Display dialog and select the grid.
+
--
+
set dialogResult to display dialog "Choose server:
+
1) 2nd Life grid
+
2) local standalone
+
3) local grid
+
4) OS Grid" default answer "2" with title "Select Grid" with icon 1
+
+
set grid to text returned of dialogResult
+
+
if grid = "1" then
+
set options to lindenOptions
+
else if grid = "2" then
+
set options to localStandalone
+
else if grid = "3" then
+
set options to localGrid
+
else if grid = "4" then
+
set options to osGridOptions
+
else
+
set options to localStandalone
+
end if
+
--
+
-- Combine the grid and viewer and execute the result.
+
--
+
set command to viewer & options
+
do shell script command
+
  
===Linden Viewer options===
+
Near these fields, you will also find a button named "Get Grid Info" or similar. If you click it, it may fill out several blank fields with URIs.  
The Linden viewer has a number of other options. Some are useful, some are not. The viewer has a help option which produces the following results:
+
In some cases, clicking the button will cause an error message to pop up, or in rare cases, freeze the viewer. If clicking the button causes problems of any kind, you can leave the remaining fields empty, or find the missing info and add it manually. Leaving the fields empty will normally not cause problems, and you will still be able to log in to that grid, although on some grids, some features may be unavailable until the missing info is added.
  --autologin          log in as last saved user
+
  --channel arg        n/a
+
  --console arg        n/a
+
  --cooperative arg    Yield some idle time to local host.
+
  --crashonstartup      Crashes on startup. For QA use.
+
  --debugviews          n/a
+
  --drop arg            n/a
+
  --god                Log in a god if you have god access.
+
  --grid arg            Specify the name of the grid, local, or an IP address
+
                        to connect to.
+
  -h [ --help ]        display this help message
+
  --helperuri arg      helper web CGI prefix to use
+
  --ignorepixeldepth    Ignore pixel depth settings.
+
  --inbw arg            n/a
+
  --logfile arg        n/a
+
  --login args          3 tokens: first, last and password
+
  --loginpage arg      Login authentication page to use.
+
  --loginuri arg        login server and CGI script to use
+
  --multiple            Allow multple viewers.
+
  --no-verify-ssl-cert  n/a
+
  --noaudio            n/a
+
  --noinvlib            Do not request the inventory library.
+
  --nopreload          n/a
+
  --noprobe            n/a
+
  --noquicktime        n/a
+
  --nosound            n/a
+
  --novoice            Disable voice.
+
  --outbw arg          n/a
+
  --port arg            n/a
+
  --purge              Delete files in the cache.
+
  --qa                  Activated debugging menu in Advanced Settings.
+
  --quitafter arg      n/a
+
  --rotate              n/a
+
  --safe                Reset preferences, run in safe mode.
+
  --set args            specify the value of a particular
+
                                      configuration variable that
+
                                      overrides all other settings
+
                             
+
  --setdefault args      specify the value of a particular
+
                                      configuration variable which can be
+
                                      overridden by settings.xml
+
                             
+
  --settings arg        Specify the filename of a configuration file.
+
  --skin arg            ui/branding skin folder to use
+
  --slurl arg          Startup SLurl
+
  --url arg            Startup location
+
  --psn arg            MacOSX process serial number
+
  
===== Note =====
+
Click the "Apply" or "OK" button to store your new grid in the menu, and you will be ready to log in as explainted under [[Connecting#If the grid is present in the list|If_the_grid_is_present_in_the_list]]
  
The above described methods work for the SecondLife viewer, other viewers that support the GridInfo protocol won't need this.
+
For instructions that are specific for your favorite viewer, see your viewer's website.
  
== Alternative Connection Approaches ==
+
== Connecting to the Grid with Viewer Parameters ==
  
=== Via a Web Browser ===
+
If your viewer doesn't have a grid selector, or if you are having problems adding the grid to your viewer's grid list, then an alternative method is to use viewer parameters.
  
You can also set up a [[Browser Protocol Handler]] which will make opensim:// links in your browser do the expected thing, and launch the right OpenSim viewer.
+
Basically, all you will really need is to pass the ''--loginuri'' command line parameter to the viewer and launch with it, although you will want to use all of the viewer parameters that are suggested for your preferred grid.
  
* [[Xenki]] - Xenki is an XBAP 3D application intended to be a browser add-on for OpenSim.  
+
For example, you use a viewer on Windows, and you want to connect to OSGrid. A quick-and-easy way would be as follows:
** '''Project site'''
+
 
** http://forge.opensimulator.org/gf/project/xenki/
+
* Press Windows Key + R, this will open the Run dialog.
** '''What is Xenki?'''  
+
* In the Run dialog, enter the following:
** http://www.adamfrisby.com/blog/2008/08/what-is-xenki/
+
viewer-name.exe --loginuri <nowiki>http://login.osgrid.org/ --loginpage http://www.osgrid.org/splash/</nowiki>
** '''Sources:'''  
+
* Press "Enter", or click "OK" and your viewer should start. After clicking the login button, you will enter OSGrid.
** http://www.adamfrisby.com/blog/2008/08/xenki-010-alpha-sources-posted/
+
 
 +
On OSX, you could also use AppleScript, which enables you to select multiple grids to connect to. See the [[OSX Grid Selector Script]] article for a pre-made script.
 +
 
 +
== Connecting to your locally hosted server from behind a DSL router using NAT ==
 +
 
 +
'''Loopback'''
 +
Most DSL routers/modems prevent loopback connections as a security feature. This means that a NATed IP address ( such as 192.168.2.40 ) can not connect to your forward facing IP address ( such as 199.149.252.44 ) from behind your DSL router/modem. In a case like this, external IP addresses may connect to your server/region but you can not ( this applies to both standalone and grid modes ).  
 +
 
 +
List of routers featuring NAT Loopback : [[NAT Loopback Routers]]
 +
 
 +
'''Router solution'''
 +
If you are using a ZyXEL DSL router/modem from Embarq, please read [[Network Settings#Local connections with ZyXEL DSL modem/router and NAT/Port Forwarding|this guide]]. This will show you how to reconfigure your DSL router/modem to fix this problem. Similar solutions may exist for other DSL router/modems. A Google search for the make and model of your DSL router/modem may provide you with a manual to assist you in this.
 +
 
 +
A word of caution : be VERY careful what you change and take good notes along the way so you can undo any changes you make in error.
 +
 
 +
'''DNS solution(Linux)'''
 +
It's possible to host your own DNS-server, so you can prevent some of the dns-naming problems mentioned before. If <nowiki>http://example.org</nowiki> 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.
 +
 
 +
[[Category:Help]]

Latest revision as of 04:31, 6 December 2021


[edit] Obtaining OpenSimulator Available Viewers

OpenSimulator does not come with a viewer in its distribution.

You'll need to download an OpenSimulator compatible client/viewer before connecting to OpenSimulator grids or regions.

Please see Compatible Viewers

  • Note that some grids may prefer that you use a particular viewer (even a particular version) so follow that grid instructions.

[edit] Connecting to the Grid with A Grid Selector (Recommended)

Most viewers have a grid selector which in many cases is already visible, and located at the bottom of the login screen. If it is not visible, try pressing Ctrl-Shift-G to (un)hide the grid selector.

[edit] If the grid is present in the list

If you see the grid you want to connect to in the grid selector, then simply choose it from the drop down menu, enter the username and password that you chose when you created your account on that grid, and click the "Log in" button.

[edit] If the grid is missing from the list

If your preferred grid is not present in the drop down menu, then you will have to add it manually. You will have to do this only once. First, find the grid manager. Usually, this can be found in the preferences of your viewer, in a tab called "Grids". In general, the only fields that you will have to fill in are:

  • Grid Name (or alike) - A name you can easily identify the grid by. OpenSimulator grids don't use this information, so you can name it anything you like.
  • Login URI - The most important information. It should be like "http://someserver:9000" or "http://someserver". For instance, for OSGrid, this is "http://login.osgrid.org/".

Near these fields, you will also find a button named "Get Grid Info" or similar. If you click it, it may fill out several blank fields with URIs. In some cases, clicking the button will cause an error message to pop up, or in rare cases, freeze the viewer. If clicking the button causes problems of any kind, you can leave the remaining fields empty, or find the missing info and add it manually. Leaving the fields empty will normally not cause problems, and you will still be able to log in to that grid, although on some grids, some features may be unavailable until the missing info is added.

Click the "Apply" or "OK" button to store your new grid in the menu, and you will be ready to log in as explainted under If_the_grid_is_present_in_the_list

For instructions that are specific for your favorite viewer, see your viewer's website.

[edit] Connecting to the Grid with Viewer Parameters

If your viewer doesn't have a grid selector, or if you are having problems adding the grid to your viewer's grid list, then an alternative method is to use viewer parameters.

Basically, all you will really need is to pass the --loginuri command line parameter to the viewer and launch with it, although you will want to use all of the viewer parameters that are suggested for your preferred grid.

For example, you use a viewer on Windows, and you want to connect to OSGrid. A quick-and-easy way would be as follows:

  • Press Windows Key + R, this will open the Run dialog.
  • In the Run dialog, enter the following:
viewer-name.exe --loginuri http://login.osgrid.org/ --loginpage http://www.osgrid.org/splash/
  • Press "Enter", or click "OK" and your viewer should start. After clicking the login button, you will enter OSGrid.

On OSX, you could also use AppleScript, which enables you to select multiple grids to connect to. See the OSX Grid Selector Script article for a pre-made script.

[edit] Connecting to your locally hosted server from behind a DSL router using NAT

Loopback Most DSL routers/modems prevent loopback connections as a security feature. This means that a NATed IP address ( such as 192.168.2.40 ) can not connect to your forward facing IP address ( such as 199.149.252.44 ) from behind your DSL router/modem. In a case like this, external IP addresses may connect to your server/region but you can not ( this applies to both standalone and grid modes ).

List of routers featuring NAT Loopback : NAT Loopback Routers

Router solution If you are using a ZyXEL DSL router/modem from Embarq, please read this guide. This will show you how to reconfigure your DSL router/modem to fix this problem. Similar solutions may exist for other DSL router/modems. A Google search for the make and model of your DSL router/modem may provide you with a manual to assist you in this.

A word of caution : be VERY careful what you change and take good notes along the way so you can undo any changes you make in error.

DNS solution(Linux) 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.

Personal tools
General
About This Wiki