Connecting

From OpenSimulator

(Difference between revisions)
Jump to: navigation, search
(Connecting with the Linden Viewer)
m (Obtaining OpenSimulator Available Viewers: Capitalisation and spacing only)
 
(71 intermediate revisions by 24 users not shown)
Line 1: Line 1:
==Compatible Viewers==
+
__NOTOC__
* [[RealXtend]]
+
* [[Linden_Client|Linden Client]]
+
* [http://openviewer.org/index.php OpenViewer]
+
  
==Bug Reports==
+
{{Quicklinks|Connecting}}
Though any Second Life compatible client should be supported, bug reports even in IRC should only be made if you are using 1.18.5.3.
+
* SecondLife 1.19.1(4) (official) on Linux, Mac OS X, and Windows
+
* SecondLife 1.18.6 Windlight (works)
+
  
==Browser Protocol Handlers==
+
== Obtaining OpenSimulator Available Viewers ==
A browser-protocol handler is a quick way to connect to a grid, by just clicking on a hyperlink that has an "opensim://" prefix, The only thing you have to do, is instruct your browser how to handle the sl-viewer. Currently there are protocol-handlers for Linux and Windows. I'm pretty sure it's just as easy on the Mac, but since I don't own one, you have to find out for yourself(for now).
+
  
===Linux===
+
'''OpenSimulator does not come with a viewer in its distribution.'''
====Firefox====
+
You can setup firefox to open opensim://serveraddress links, so you don't have to specify the login-parameters every time you're connecting.
+
Follow these steps in order to use this functionality:
+
* create a file named osurl.sh in your secondlife directory, and fill with:
+
#!/bin/sh
+
exec= kdesu -c "/your/path/to/secondlife/secondlife -loginuri ${1:10} -loginpage ${1:10}/?method=login"
+
Notice that kdesu is optional. Somehow secondlife crashes when i run it as a normal user, so I run it as root.
+
* Make the file executable
+
chmod +x ./osurl.sh
+
  
Next you have to add a protocol handler to firefox, so firefox knows that it should run this shellscript.
+
You'll need to download an OpenSimulator compatible client/viewer before connecting to OpenSimulator grids or regions.
  
* Enter about:config in your browser
+
Please see [[Compatible Viewers]]
* Add a new string, name it "network.protocol-handler.app.opensim"
+
* Enter /path/to/your/secondlife/dir/osurl.sh as value
+
* Add a new boolean, name it "network.protocol-handler.external.opensim", and set it to "true"
+
  
Now you can try to connect with the OS-Grid by opening "opensim://osgrid.org:8002"" in your browser.
+
* Note that some grids may prefer that you use a particular viewer (even a particular version) so follow that grid instructions.<br><br>
Please notice that using protocol handlers may cause a potential security hazard(http://www.heise-security.co.uk/news/96163). I am not sure whether this script is vulnerable to the -autologin vulnerability, so be warned(ps. I don't take any responsibility for using this script).
+
  
===Windows===
+
== Connecting to the Grid with A Grid Selector (Recommended) ==
====Internet Explorer====
+
You can do the same for windows, but it takes a little more work. Follow these steps to get the functionality:
+
* create a file named osurl.bat in your secondlife directory, and fill with:
+
@echo off > osurl.bat
+
SET rawUrl=%1
+
SET cleanUrl=%rawUrl:~10%
+
START "OpenSim" /HIGH /B "%~d0%~p0SecondLifeWindLight.exe" -loginpage %cleanUrl%?method=login -loginuri %cleanUrl%
+
EXIT
+
  
* We need to create a file named opensim.reg, fill with(modify paths to SL if needed) the text beneath, and save:
+
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.
Windows Registry Editor Version 5.00
+
[HKEY_LOCAL_MACHINE\SOFTWARE\Classes\opensim]
+
"(default)"="URL:opensim"
+
"URL Protocol"=""
+
[HKEY_LOCAL_MACHINE\SOFTWARE\Classes\opensim\DefaultIcon]
+
@="\"C:\\Program Files\\SecondLifeWindLight\\osurl.bat\""
+
[HKEY_LOCAL_MACHINE\SOFTWARE\Classes\opensim\shell]
+
[HKEY_LOCAL_MACHINE\SOFTWARE\Classes\opensim\shell\open]
+
[HKEY_LOCAL_MACHINE\SOFTWARE\Classes\opensim\shell\open\command]
+
[HKEY_LOCAL_MACHINE\SOFTWARE\Classes\opensim\shell\open\command]
+
@="\"C:\\Program Files\\SecondLifeWindLight\\osurl.bat\" %1"
+
  
* Right-click the file, and import it to the registry
+
=== 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.
  
====Firefox====
+
=== If the grid is missing from the list ===
* Follow the previous steps for Internet explorer
+
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.
* add a protocol handler to firefox, so firefox knows that it should run this shellscript.
+
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:
  
* Enter about:config in your browser
+
* '''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.
* Add a new string, name it "network.protocol-handler.app.opensim"
+
* '''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>
* Enter c:/Program Files/YourSecondLifedir/osurl.bat as value (use your own sl-path here)
+
* Add a new boolean, name it "network.protocol-handler.external.opensim", and set it to "true"
+
  
Now try to connect with the OS-Grid by clicking this link in your browser: opensim://osgrid.org:8002""
+
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.
  
===Mac OSX===
+
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]]
Not yet implemented
+
  
==Connecting with the Linden Viewer==
+
For instructions that are specific for your favorite viewer, see your viewer's website.
  
Use the -loginuri yourserver.org:8000 switch and the -loginpage yourserver.org:8000/?method=login switch. You may want to use the -settings switch to use a different configuration set as well (the default is settings.xml). Some examples:
+
== Connecting to the Grid with Viewer Parameters ==
SecondLife.exe -loginuri <nowiki>http://localhost:9000/</nowiki> -loginpage <nowiki>http://localhost:9000/?method=login</nowiki>
+
  
SecondLife.exe -loginuri <nowiki>http://osgrid.org:8002/</nowiki> -settings settings_osgrid.xml -loginpage <nowiki>http://osgrid.org:8002/?method=login</nowiki>
+
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.
  
Setup the protocol handler for convenient connecting, or use the same syntax for other Grids. After the protocol handler is setup, you can try to connect to some grids, by clicking on of the examples below:
+
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.
  
opensim://user.deepgrid.com:8002/
+
For example, you use a viewer on Windows, and you want to connect to OSGrid. A quick-and-easy way would be as follows:
  
opensim://osgrid.org:8002/
+
* Press Windows Key + R, this will open the Run dialog.
 +
* In the Run dialog, enter the following:
 +
viewer-name.exe --loginuri <nowiki>http://login.osgrid.org/ --loginpage http://www.osgrid.org/splash/</nowiki>
 +
* Press "Enter", or click "OK" and your viewer should start. After clicking the login button, you will enter OSGrid.
  
opensim://logingrid.net:8002/
+
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.
  
opensim://maingrid.centralgrid.com:8002/
+
== Connecting to your locally hosted server from behind a DSL router using NAT ==
  
opensim://eu-grid.eu:8002/
+
'''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 ).
  
Another option is to try the 'Launcher' for Windows (.net required). http://www.openlifegrid.com/downloads/gridlauncher.zip<br>
+
List of routers featuring NAT Loopback : [[NAT Loopback Routers]]
To login to the Public GRID examples registration is required first see [[OpenSim: Grids]] for Public Grids.
+
  
 +
'''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.
  
'''''Warning!'''''
+
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.
  
One source of problem - like uploaded pictures not showing or not being able to move directly after loging in into a public grid - is having the "Maximum Bandwith" setting in the Preferences of the SecondLife viewer on the "Network" tab set too high. So set it to about 250 kbps, when you encounter such issues.
+
'''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.
  
==Technical issues==
+
[[Category:Help]]
 
+
===Platform Specific===
+
==== Setup launcher for Mac ====
+
 
+
/Applications/Second\ Life.app/Contents/MacOS/Second\ Life -loginuri <nowiki>http://localhost:9000/</nowiki> -loginpage <nowiki>http://localhost:9000/?method=login</nowiki>
+
/Applications/Second\ Life.app/Contents/MacOS/Second\ Life -loginuri <nowiki>http://user.deepgrid.com:8002/</nowiki> -loginpage <nowiki>http://user.deepgrid.com:8002/?method=login</nowiki>
+
/Applications/Second\ Life.app/Contents/MacOS/Second\ Life -loginuri <nowiki>http://osgrid.org:8002/</nowiki> -loginpage <nowiki>http://osgrid.org:8002/?method=login</nowiki>
+
/Applications/Second\ Life.app/Contents/MacOS/Second\ Life -loginuri <nowiki>http://logingrid.net:8002/</nowiki> -loginpage <nowiki>http://logingrid.net:8002/?method=login</nowiki>
+
/Applications/Second\ Life.app/Contents/MacOS/Second\ Life -loginuri <nowiki>http://osgrid.org:8002/</nowiki> -loginpage <nowiki>http://osgrid.org:8002/?method=login</nowiki> -settings settings_osgrid.xml
+
 
+
alternatively you can add arguments to '''arguments.txt''' on a mac  by:
+
# right-click secondlife choose "'''show package contents'''"
+
# navigate to '''contents -> resources -> arguments.txt'''
+
# add this on one line: '''-loginuri <nowiki>http://localhost:9000/</nowiki> -loginpage <nowiki>http://localhost:9000/?method=login</nowiki>'''
+
# save and run the application normally
+
#* note: you will not be able to connect to Second Life again until you remove this line from arguements.txt
+

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