Connecting

From OpenSimulator

(Difference between revisions)
Jump to: navigation, search
m (Reverted edits by KatherineDaniels (Talk) to last version by MakoBot)
m (Obtaining OpenSimulator Available Viewers: Capitalisation and spacing only)
 
(23 intermediate revisions by 8 users not shown)
Line 1: Line 1:
 
__NOTOC__
 
__NOTOC__
{{Quicklinks}}
 
<br />
 
  
==Obtaining OpenSim Available Viewers==
+
{{Quicklinks|Connecting}}
'''OpenSimulator doesn't have the client program in its distribution.''' You'll need to download an OpenSim compatible client before connecting to OpenSim grids.
+
{{:Compatible Viewers}}
+
  
Some other viewers that can connect to Second Life can also connect to OpenSim. You can find them in [http://wiki.secondlife.com/wiki/Downloads Downloads#Second Life Wiki].
+
== Obtaining OpenSimulator Available Viewers ==
  
==Connecting to the Grid with Grid Selector (Recommended) ==
+
'''OpenSimulator does not come with a viewer in its distribution.'''
  
If you can find the grid you want to connect in the grid selector (The dropdown menu at the bottom of the screen to the right of the login button. If you can't find it, try Ctrl-Shift-G), then simply choose it and enter username/password provided by the grid administrators when you created your account on the grid.
+
You'll need to download an OpenSimulator compatible client/viewer before connecting to OpenSimulator grids or regions.
  
'''Basically, you can't login to OpenSim grids with other grid's accounts, including Second Life. You need to create separate accounts for each grids you want to login.''' When you choose the grid, some viewers shows the link to signup page, so create your account as per its instructions.
+
Please see [[Compatible Viewers]]
  
If you can't, then lookout for the Grid Manager interface. If there is, you can find it near the grid selector or in preference window. Usually, the only fields you have to fill in are:
+
* Note that some grids may prefer that you use a particular viewer (even a particular version) so follow that grid instructions.<br><br>
  
* '''Grid Name''' (or alike) - The name you can easily identify. OpenSim grids doesn't use this information, so you can name it freely.
+
== Connecting to the Grid with A Grid Selector (Recommended) ==
* '''Login URI''' - The most important information.<nowiki> It should be like "http://someserver:9000" or "http://someserver:8002". For instance, for osgrid, this is "http://login.osgrid.org/".</nowiki>
+
  
You will find the button "Get Grid Info" or alike. If you click it, it might fill other blank fields with some URIs, or show error dialog, or freeze. If you have problem with this button, don't click it and leave other fields empty. This problem is not so much an issue. It works anyway without them.
+
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.
  
If it succeed, you will find the new entry in the grid selector.  
+
=== 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.
  
For detailed instructions, see the documentation for each viewer.
+
=== 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:
  
==Connecting to the Grid with Viewer Parameter==
+
* '''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 "<nowiki>http://someserver:9000" or "http://someserver". For instance, for OSGrid, this is "http://login.osgrid.org/".</nowiki>
  
If you can't find grid selector, or you can find it but can't find the grid you want to login in the list and can't find grid manager, there are some other methods.
+
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.
  
In any case, all you have to do is to pass this '''loginuri''' command line parameters to the viewer and launch with it. If you are using Second Life Viewer or Snowglobe-based viewers, see [http://wiki.secondlife.com/wiki/Viewer_parameters#Using_Viewer_parameters this wiki page (Viewer parameters#Using Viewer Parameters)] how to do that. The Linden viewer has a number of other options.  Some are useful, some are not. See [http://wiki.secondlife.com/wiki/Viewer_parameters#Parameter_reference Parameter Reference from Second Life Wiki] for detail.
+
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]]
  
For example, Second Life Viewer on Windows, and want to connect to OSGrid, quick-and-easy way would be like that:
+
For instructions that are specific for your favorite viewer, see your viewer's website.
<pre>
+
SecondLife.exe -loginuri <nowiki>http://login.osgrid.org/ -loginpage http://www.osgrid.org/splash/</nowiki>
+
</pre>
+
+
On OSX, you can even use ActionScript, which enables you to select multiple grid to connect to. [[OSX_Grid_Selector_Script]]
+
  
==Connecting to your locally hosted server from behind a DSL router using NAT==
+
== Connecting to the Grid with Viewer Parameters ==
  
<b>Loopback</b><br>
+
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 <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.
 +
 
 +
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 ).  
 
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]]
+
List of routers featuring NAT Loopback : [[NAT Loopback Routers]]
  
<b>Router solution</b><br>
+
'''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.  
+
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.
 
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.
  
<b>DNS solution(Linux)</b><br>
+
'''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:
 
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
 
  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.
 
Now you need bind/named installed in order to handle the dns-requests. You can find a bind example configfile here.
  
== Alternative Connection Approaches ==
+
[[Category:Help]]
 
+
=== Via a Web Browser ===
+
 
+
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.
+

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