I just put up an Worldgroup 3.2 board and need to know what to do to run my TWGS.


Thanks,
Ace-T

quote:
I just put up an Worldgroup 3.2 board and need to know what to do to run my TWGS.


The following information is taken from the Help file included with the TWGS 3.11.55 distro files. I've only edited them in order for their formatting to appear correctly in HTML.

Running from a Worldgroup BBS

By calling TWGS from Worldgroup with the RLogin connection protocol, you can limit your game server users to a single login per Worldgroup account. If you maintain control over player accounts on your BBS, you will have no problems with duping on the server.

Step 1: Configure TWGS for Worldgroup connections.

1) Disable the server and enter the Configuration area.
2) Select the Server tab
3) Select port 513 (required for Worldgroup RLogin connections)

Set the port protocol to RLogin to allow passing of BBS user name from the BBS to TWGS. This must be set for the Worldgroup connection to work. Since only port 513 connections are allowed, you cannot use RLogin for both the game and the admin connections. Set the admin port to telnet.

The "User RLogin name" setting may need to be changed from the default "Passed 2nd" setting. This setting determines which RLogin login string TWGS treats as the user login name. If TWGS isn't reading the correct login name, you should switch to "Passed 1st".


Step 3: Specify a limited IP connection list

Under the IP Lists tab of the Configuration area, you should add the IP address of your BBS machine to the Game Connection and Admin Connection IP lists. This will limit TWGS connections to only those originating from the machine that is running your BBS.

If you are running TWGS from the same machine as the BBS, you should use the local loopback address for the IP (127.0.0.1). If you are running TWGS from a separate machine from the BBS, put the IP address of the BBS machine into these lists.

WARNING: If you do not specify an IP address in the Admin Connection list, others can remote connect to your administration port. This will provide them access to TEDIT on all of your games. You should specify TEDIT passwords, but it is still most safe to allow connections only from a specific list of IPs.

Step 4: Create a Worldgroup TWGS menu option.

1) Enter the menu tree editor
2) Add a page for the TWGS
3) Set the page to "Module page" and select your TCP/IP (RLogin) module

Type in the command-line to connect to TWGS. This will vary depending on the TCP/IP module you are using. I will provide two examples, one for VircomTCP/IP and one for the standard WG3 RLogin Module.

I will build the command for a sample loopback (local) connection.

VircomTCP/IP:

Specify RLogin connection protocol

Command: "L ..."

1) Specify the IP address of the Game Server.

If you have TWGS set to run on the same machine as your BBS, this should be the local loopback IP address, 127.0.0.1. This is most efficient because TCP/IP skips many unnecessary levels of processing when the data is passed to the same machine. You must set this local loopback address as the TWGS IP address in the TWGS Configuration area, Server tab, or click the Local check box.

If you have TWGS set to run from a different machine, this should be the IP addressed associated with that machine. The machine can be connected via a LAN or the Internet. The simplest way to configure TWGS in this case is to use auto IP address detection. TWGS will determine the IP address of the machine whenever is it started.

Command: "L 127.0.0.1 ..."


Specify the RLogin connection strings.

RLogin passes two user login strings and a terminal type. WG allows you to pass user names using the %u macro. To pass two user names and a terminal type, enter a line like this:

Command: "L 127.0.0.1 %u %u ansi"


WG3 RLogin Module:

Specify the IP address of the Game Server.

If you have TWGS set to run on the same machine as your BBS, this should be the local loopback IP address, 127.0.0.1. This is most efficient because TCP/IP skips many unnecessary levels of processing when the data is passed to the same machine. You must set this local loopback address as the TWGS IP address in the TWGS Configuration area, Server tab, or click the Local check box.

If you have TWGS set to run from a different machine, this should be the IP addressed associated with that machine. The machine can be connected via a LAN or the Internet. The simplest way to configure TWGS in this case is to use auto IP address detection. TWGS will determine the IP address of the machine whenever is it started.

Command: "127.0.0.1"

Save your menu settings.

Step 6: Test the connection

Start TWGS and enable the server

Connect to your BBS and go to the TWGS connection menu item. Select the item to start a TWGS session. You should be immediately presented with the TWGS intro menu. Use the # key to see who is online. The name specified in this list should be your BBS name. You cannot alter this name from TWGS, and it is used for all TW game sessions. This guarantees that only one Trade Wars game account can exist in any game for each BBS user name

Lisa M. Cutler
aka Rave
EIS Product Support

When trying to log in it says cannot rlogin from system if you are on the internet???
What did I do wrong or not do?
works great from local connct but not from net.

Ace-T

Rave,
Thanks for all your help I got it. I had to set a key for it it is now up and running.

Thanks Again
Ace-T

I am still having some fun tailoring my WG 3.2 BBS to allow only 1 user per IP to enter the TWGS. Following the instructions, if I turn on the Restrict option, only 1 person at a time can enter. I do have the require logons turned on, but TWGS is only seeing the IP of the BBS, not the individual.

The only thing I have found is to use Rifster's Monitor, a free utility, to record the IPs live. Of course, the logging will do this for me automatically, but I don't want to have to log on a sysop level account to read this. As we are now a league server, I would love to get this ironed out and more automated.

Thanks bunches... love the game, love the server.



Pagan
Death Dealers/FarNorth Raiders
Can you come out and play?
Stardock Omega
hubtoo.com or 198.31.27.43

quote:
I am still having some fun tailoring my WG 3.2 BBS to allow only 1 user per IP to enter the TWGS. Following the instructions, if I turn on the Restrict option, only 1 person at a time can enter. I do have the require logons turned on, but TWGS is only seeing the IP of the BBS, not the individual.

The only thing I have found is to use Rifster's Monitor, a free utility, to record the IPs live. Of course, the logging will do this for me automatically, but I don't want to have to log on a sysop level account to read this. As we are now a league server, I would love to get this ironed out and more automated.


you'll need to disable the limit one connection per ip address option in twgs if you want to allow more than one person to connect to the server through the bbs.

one problem with putting twgs behind a bbs is going to be watching for dupes as the ip addresses of players that appear in twgs will always be the ip address of the machine running the bbs software and worldgroups has limited security against dupes unless you purchase some additional packages like control or validator.

good luck with your system!