Console


Console
General Properties Tab
Web Properties Tab
Client Properties Tab
Operators Properties Tab
Servers Properties Tab
Security Properties Tab


Console

Console

The console allows you to run ConferenceRoom as a console program either under Windows NT® or under Windows 95®. It also displays server statistics and license information.

Start/Stop
Start or Stop ConferenceRoom if running program as Console.

Hide
Close the Console program.

Configure
Opens up the Properties menu.


General Properties Tab

General Tab

Server Information

Description
(not required) This a short description of your server that will be displayed when a user types the /admin or /info commands.
Example: IRC Server [207.3.177.10]

Contact Info
(not required) contains information so that people using the server know how to contact the administrator (such as e-mail address) of the server. Provides contact information for the /admin command.
Example: Contact: johnd@domain.com (John Doe)

Key
Key required to operate the server. The key installed determines the ConferenceRoom version which is installed. Connections are limited to 10 users for the 30 day evaluation version. We encourage you to register your key for support.

User License is indicated.

Network Information

Port
Designates a port to be allocated for connections to the server. The default port, as is usually the case for IRC, is set for 6667.

Limit connections
It is possible to support up to 10, 000 simultaneous users with the correct machine configuration on ConferenceRoom. There is a limitation on the number of simultaneous connections depending upon the end user license. It is automatically set to 10 for the trial version.

Only this hostname
This option should be left off unless you have a static IP address that does not change each time you connect to your provider.

Runs as a service
Causes ConferenceRoom to be run as a service under Windows NT®. Available only to registered users.

Advanced Options

Advanced Options Tab

Disable DNS Lookups
Client Addresses will appear as IP adresses rather than host domains on the server if this option is enabled. Most people will probably prefer to leave this option unchecked.

Example: 201.3.177.10 instead if hostname.domainname.com

Network Style

ConferenceRoom is currently compatible with the UNIX® IRCD code-base, and can connect to any network based on that. We expect to be able to connect to IRC networks based on the other code basis in the next release of ConferenceRoom.

In addition, ConferenceRoom can also connect to other ConferenceRoom(s) servers using its server-to-server messaging functionality. WebMaster will be initiating two networks based on this technology, one of which will be open to all users, while the other will require high performance and support on the part of its participants. For more information on these networks, please contact WebMaster Incorporated.

ConferenceRoom Native: (default)Running in this mode informs ConferenceRoom that it is either not networked or is networked only to other ConferenceRoom(s). This mode enable several protocol extensions (including AdminOper) that provide additional functionality to the IRC standard operation.

IRCD: Running ConferenceRoom in this mode lets it connect to other servers running IRCD 2.8.2.1 or earlier.

To connect to other servers, see information in the Server Properties Tab


Web Properties Tab

Web Tab

Web Interface

ConferenceRoom now comes with a built in web server which allows you to serve the web interface to the IRC chat rooms using theme oriented templates. In order to serve the Java clients, you merely need to choose one of the themes, the description of which is provided, or create one of your own. In fact, if you submit a theme to us, and we choose to use it, we will provide you with a free WebMaster T-Shirt (everyone wants one), and a free ConferenceRoom license.

Choose a Theme
Simply select a theme such as the DEFAULT theme, which will be the basis for the client web interface to the server. These themes resemble an IRC Client in their functionality. A user logs into the server by typing in the nick, and then decides which of the chat rooms to join.

Network Interface

Port
The port of which the web interface to ConferenceRoom is served. The default port is 8080.

Warning: ConferenceRoom automatically enables its web interface on port 8080. If you have another server (e.g. Your primary web server running on port 8080), you must disable the web server by enabling the "Disable Web Server" option or change the port number above to an unused port (e.g. 8000)

Limit connections
It is possible to support up to 10, 000 simultaneous users with the correct machine configuration on ConferenceRoom. There is a limitation on the number of simultaneous connections depending upon the end user license. It is automatically set to 10 for the trial version.

Only this hostname
This option should be left off unless you have a static IP address that does not change each time you connect to your provider.

Disable web server
In case you wish to use your primary web server to serve the web interface, or do not wish to have a web interface, this option will disable the web server. (More on using the web interface without the web server later)

Note: The information entered in the General Properties tab when configuring ConferenceRoom does roll over into the Web Properties tab, but the user still needs to click/switch on to the Web Properties tab and press OK to activate the information.


Client Properties Tab

Client Tab

Client Configuration

You can add, edit and delete user classes in this menu. The DEFAULT setting allows all users to connect to your server. If you want to limit access to the server you may delete the DEFAULT entry and click on ADD. The following information must then be provided:

Classname: Name of the client class to be listed in the control panel.
Example: Admin Only

Userid: Userid or the login ID of the user permitted to connect. Use * to allow all userids’.
Example: residue or *

Password: Password required to connect to the server. Use * if you do not wish to require one.
Example: adminpass

From host: Host from which clients will be permitted to connect to the server. In most cases, this field should contain a *, which will allow users from any domain to enter your server.
Example:
* This will allow any domain to connect.
*.domainname.com This will only allow clients from domainname.com to connect.

Ping Frequency
Determines how often the server checks to determine if clients are still connected. Timeouts can be caused by various things such as the user losing Internet connectivity, disconnecting or a lot router route. If users are experiencing ping timeouts, this value may need to be raised.

Multiple clients per host
Allows multiple connections from a specific address. Leaving this option unchecked will prevent users from running clones on the server. If you know you have a computer from which several users may try to connect to ConferenceRoom at the same time, you may wish to define a separate Client Class entry for this machine and select the Multiple Clients per Host option.

There may be as many client definitions as you wish. The first (topmost) entry that matches a user’s userid and hostname will be used. If the (optional) password on this entry does not match the password provided by the user, authentication will fail and the user will not be able to access the server. Currently the only way to control the order of the client configurations is by altering the client classname – the entries are sorted by this value.

Message of the Day

Appears to all users when connecting to the server and on prompting from the /motd command.

Example:

Welcome to residue’s personal IRC server.

Discussion of the latest releases and online help available on #nyc

For help type; /msg residue Can you help me?


Operators Properties Tab

Operators Tab

This is a list of IRC operators for the server. IRC Operators help control the server in order to achieve optimum operation and enforce policy. This control is exerted by the use of special commands which kill (break connections with) users who are violating policy or are attempting to disrupt service, kline (ban from signing on) users who continue to cause problems make, and make and break connections between servers (in a network of servers).

You can add, edit, and delete information relating to the operators of the channels on IRC. Following is the information you must submit:

Operator definition: Name that will appear in the operator list of the control panel. To specify oneself as an operator from a traditional IRC client, type:
/admin operatordefinition password

To specify oneself as an Administrative Operator, from your traditional IRC client, type:
/adminoper operatordefinition password

Userid: Userid of the client. Only change this from the defaukt * if you want this to match the clients. The userid is specific to a users' client software. If your /whois information shows:
Residue@~xxxxx flakey.donut.residue.com
then xxxxx is the userid (do not include the ~).

Password: Case sensitive password that must be entered to gain access privileges.
Example: FlakeyOne

From: Host from which an IRC op must connect.
Example: *.residue.com

Administrator: This feature only works in ConferenceRoom Native Mode. This gives you the added functionality to set channel modes, set the event mode and set special user modes. A detailed description of these can be found later in the manual.

To obtain a list of hosts with o-lines for the server once you are connected, type /stats o. To make yourself an IRC operator, type:
/oper operatordefinition password in the command line of any IRC client. This will only work if you have been assigned operator status in this panel.

Global Operator:This ConferenceRoom feature is equivalent to the -g IRC option. It allows an operator to be an operator across a network of servers.


Servers Properties Tab


Servers Tab

ConferenceRoom servers can be networked together to form a single network with a single "Chat Space". This network takes the form of a spanning tree, where each node in the network is either a leaf (having only one link – to its uplink), or a node (having a single link to its uplink and multiple downlinks to leaves or downstream nodes).

The Servers Properties tab contains two lists: Uplinks and Downlinks:

Uplink

The Uplink list consists of a primary uplink and 0 or more backup uplinks. Only one is active at a time.

Server Name: Name of the server
Password we send: Password we will send out. The other server ‘expects this password
Password we expect: Password we ‘expect’ from the other server

Downlink

The Downlink list details all the "downstream" servers to which this server connects. ConferenceRoom attempts to maintain contact with all of the servers in this list.

Server Name: Name of the server
Password we send: Password we will send out. The other server ‘expects this password
Password we expect: Password we ‘expect’ from the other server


Security Properties Tab

Security

Flood Detection

In certain cases, some IRC users may try and hamper the functioning of your server by attempting to flood the server with computer generated messages. This can be avoided by turning the flood detection option on. When on, the following Flooding Thresholds information must be entered:

Note: It is also highly recommended that Windows95 users run ConferenceRoom with flood protection on.

Disconnect when flooding detected
Users will be disconnected if they exceed the maximum penalties during a specified period.

Minimum seconds between messages
Minimum Time between inbound messages (in seconds). Violation results in penalty: Every time a user enters two messages within the specified time interval, a penalty is registered. The default is 2 seconds.

Maximum penalties before disconnect
Number of penalties permitted before a user is removed from the server for flooding. The default is 10.

Maximum channels per user
Limits the number of channels to which a user may be joined at one time.

Automatic kills

The server administrator may not want certain users, or any users from a certain domain, from logging onto the server. Such an action may become necessary if certain users persist in hampering the function of the server. This can be done by adding the relevant information here. The information that must be entered is: A list of users or hosts that are banned from the server. To add an automatic kill, click on ADD. To edit an automatic kill entry, select it and click on EDIT. The following information should be provided:

Userid: Userid of the user to be banned. Use * to ban all userids from a host.
Example: *

Domain: Domain of a user to be banned from the server.
Example: *.digex.net

Reason: Explanation for the ban
Example: Running clones on the server

To obtain a list of automatic kills on the server, type /stats k

To do a one-time kill of a user, type /kill nickname from an IRC client

To add an automatic kill entry from an IRC client, type /kline *userid@host reason. This will add an entry into the list of automatic kills managed by the configuration utility.


<< Previous Page Table of Contents Next Page >>

Copyright © 1996, WebMaster, Inc.
May not be reproduced in whole or in part without express consent of WebMaster, Inc.