Banning Foreign Users in Hypergrid - Revision history

Manni: /* On the Network Level */

2023-01-07T10:13:19Z

‎On the Network Level

2014-05-07T19:03:49Z

2014-05-07T19:02:31Z

‎Banning Foreign Users

2014-05-07T19:00:09Z

‎Via the Database

2014-05-06T21:12:00Z

‎Banning Foreign Users

2013-02-24T17:54:07Z

2011-06-10T13:55:04Z

Removed 'Template:' prefix from template includings and/or changed external-link into internal-link

2011-06-07T20:48:06Z

2009-05-21T10:48:55Z

2009-02-13T22:26:25Z

@@ Line 73: / Line 73: @@
 '''Note: This is a ban by MAC address on the firewall level.  It is possible for advanced users to change their MAC address.'''
-The following guide is an excerpt from the [http://was.fm/opensim:banning_agents full article at Wizardry and Steamworks]. The principle is that all viewers are meant to send a MAC address that is hashed using a hex digest algorithm. Since under linux iptables understands only MAC addresses, we can use ipt_string to match the MAC address.
+The following guide is an excerpt from the [https://grimore.org/opensim/banning_agents full article at Wizardry and Steamworks]. The principle is that all viewers are meant to send a MAC address that is hashed using a hex digest algorithm. Since under linux iptables understands only MAC addresses, we can use ipt_string to match the MAC address.
 For example, when a user connects to a grid, whether it is a direct login or a hypergrid teleport,  a string like the following is displayed:

@@ Line 1: / Line 1: @@
 __NOTOC__
 {{Quicklinks}}
 = Banning Foreign Users =

@@ Line 4: / Line 4: @@
 = Banning Foreign Users =
 Even though the current viewers are incapable of dealing with foreign users in the estate dialogs that they present to the user, it is possible to ban specific foreign users from your estates. For now, you have to do it on the backend, i.e. directly editing the database and reviewing the log. Not easy for the faint of heart, but any sys admin should be able to do this with their eyes shut. What follows are instructions for adding a foreign user to the estate's ban list.
 == Via the Database ==
 The first thing you need to do is to find out the UUID and IP address of the user you want to ban. For that you need to look at OpenSim.log. Search for log messages like this:
@@ Line 65: / Line 68: @@
 == On the Network Level ==
 The following guide is an excerpt from the [http://was.fm/opensim:banning_agents full article at Wizardry and Steamworks]. The principle is that all viewers are meant to send a MAC address that is hashed using a hex digest algorithm. Since under linux iptables understands only MAC addresses, we can use ipt_string to match the MAC address.

@@ Line 17: / Line 17: @@
 In this case, the information you need is: UUID = c3c9ecbf-bfb3-43eb-8dce-140afad7995f and IPAddress = problematic.domain.org
-Next, let's add this foreign user to the ban list. Note that the estate information and ban lists are kept at the region server, not in the UGAIM. If you are using local storage for your regions, this information is stored in bin/OpenSim.db. So, open that DB with whatever tool you use to access your DBs. The instructions here assume a local sqlite database; if you're using MySql or other DB technologies for the regions' storage, the instructions are almost identical, but may need adjustments.
+Next, let's add this foreign user to the ban list. Note that the estate information and ban lists are kept at the region server, not in the Robust services. If you are using local storage for your regions, this information is stored in bin/OpenSim.db. So, open that DB with whatever tool you use to access your DBs. The instructions here assume a local sqlite database; if you're using MySql or other DB technologies for the regions' storage, the instructions are almost identical, but may need adjustments.
 SqlLite usually comes with a common Linux installation. In Linux, just type:

@@ Line 4: / Line 4: @@
 = Banning Foreign Users =
-Even though the current viewers are incapable of dealing with foreign users, it is possible to ban specific foreign users from your estates. For now, you have to do it on the backend, i.e. directly editing the database and reviewing the log. Not easy for the faint of heart, but any sys admin should be able to do this with their eyes shut. What follows are instructions for adding a foreign user to the estate's ban list.
+Even though the current viewers are incapable of dealing with foreign users in the estate dialogs that they present to the user, it is possible to ban specific foreign users from your estates. For now, you have to do it on the backend, i.e. directly editing the database and reviewing the log. Not easy for the faint of heart, but any sys admin should be able to do this with their eyes shut. What follows are instructions for adding a foreign user to the estate's ban list.
 == Via the Database ==

@@ Line 2: / Line 2: @@
 {{Quicklinks}}
-=== Banning Foreign Users ===
+= Banning Foreign Users =
 Even though the current viewers are incapable of dealing with foreign users, it is possible to ban specific foreign users from your estates. For now, you have to do it on the backend, i.e. directly editing the database and reviewing the log. Not easy for the faint of heart, but any sys admin should be able to do this with their eyes shut. What follows are instructions for adding a foreign user to the estate's ban list.
 The first thing you need to do is to find out the UUID and IP address of the user you want to ban. For that you need to look at OpenSim.log. Search for log messages like this:
@@ Line 61: / Line 63: @@
 Once this data is entered you need to restart OpenSim, so that it gets loaded.
 [[Category:Hypergrid]]

@@ Line 51: / Line 51: @@
   sqlite> insert into estateban values (103, 'c3c9ecbf-bfb3-43eb-8dce-140afad7995f', 'problematic.domain.org', ' ', ' ');
   sqlite> select * from estateban;
-|c3c9ecbf-bfb3-43eb-8dce-140afad7995f|mecatreco.game-host.org||
+|c3c9ecbf-bfb3-43eb-8dce-140afad7995f|problematic.domain.org||
-|c3c9ecbf-bfb3-43eb-8dce-140afad7995f|mecatreco.game-host.org||
+|c3c9ecbf-bfb3-43eb-8dce-140afad7995f|problematic.domain.org||
-|c3c9ecbf-bfb3-43eb-8dce-140afad7995f|mecatreco.game-host.org||
+|c3c9ecbf-bfb3-43eb-8dce-140afad7995f|problematic.domain.org||
-|c3c9ecbf-bfb3-43eb-8dce-140afad7995f|mecatreco.game-host.org||
+|c3c9ecbf-bfb3-43eb-8dce-140afad7995f|problematic.domain.org||
   sqlite> .quit