This command sets whether your server should automatically try to connect to the other server if they get split. When set on, if your server "splits" or disconnects from another server then a timer goes into effect and after a certain number of seconds, the server will make a connection attempt.
Example:
/as server ChatNow set auto on
Autoconnects encourage the network to fix itself even if network operators do nothing. The delay is there so that if human judgement decides the autoconnect is a bad idea, then an operator can attempt a different connection before the autoconnect kicks in. You will probably want to set autoconnects on for the best links to your server and set it off for servers it does not normally connect to. Configuring a profile for a server that does not connect well can still be useful as a backup in case the normal connections have problems at some time. While the network is split apart is not the ideal time to start adding server profiles.
Binds the outbound connection to the specified IP address.
Example:
/as server ChatNow set bindip 127.0.0.1
When you're running on a multihomed machine this will set which IP address is used to make an outbound connection. When connecting to another server that has STRICT host checking enabled you must specificy the outbound IP or risk not being able to connect.
Makes the server profile inactive while saving the information.
Example:
/as server ChatNow set disable
If the profile is disabled then the two servers cannot connect. But you can hold that profile until such a time as you want to enable it.
When you first configure your server it is disabled -- it is not active. This way you can fully set up the profile before you allow it to connect.
Example:
/as server ChatNow set enable
It is important to enable every profile that you might want your operators to use. Check over all of your server profiles to make sure they are enabled, unless you specifically want them disabled.
This will set the actual address of the server you want to connect to. You do not need to set this if the server is going to be connecting to you.
Example:
/as server ChatNow set 127.0.0.1
It is usually easiest to make all server profiles reciprocal, so that you can connect from either side. However, if one server has a static address and the other has a dynamic address then you can always connect from the one with the dynamic address and still have the profiles work.
You must set a server as a hub if that server is going to connect to multiple servers at the same time. Hubs will allow connections from all servers defined whereas leafs will not allow more than one server connection at a time.
Example:
/as server ChatNow set hub
Hubs require more bandwidth than leafs, and losing a hub causes more problems than losing a leaf, so the hubs should be the stablest servers on the network. Often hubs allow fewer clients on, to allow them to focus their resources on holding the network together.
This is set by default and will only allow the server to be connected to one other server at a time. If you want your server to connect to multiple other servers, you must set it as a hub, see SERVER SET HUB.
Example:
/as server ChatNow set leaf
Leafs are usually the primary client servers for the network. Several leafs can hold the users, while a few hubs primarily hold the servers together.
This sets the name of the server that you are connecting to and must match the GENERAL SET NAME <name> of the other server you wish to connect to.
Example:
/as server ChatNow set name irc.webchat.org
This tells the server who it is connecting to and the other server confirms it by having the correct name.
This will set the hostmask that operators on remote servers will have.
Example:
/as server ChatNow set operhost conferenceroom.com
This sets the ping time from your server to the server you are configuring. If the server doesn't respond to a ping, it will be disconnected. Values of 90 (default) to 300 are recommended.
Example:
/as server ChatNow set ping 300
As with client pings, the more frequent the pings, the more likely a server will be incorrectly disconnected when it is merely lagged. The less frequent the pings the more likely a server will stay connected as a "ghost" server. A medium ping frequency is designed to tell as accurately as possible when the connection still exists without overwhelming the servers with pings.
This is the default port your server will use when it tries to connect to another server. The port you choose must be one that is defined on the other server.
Example:
/as server ChatNow set port 7300
You will usually want to use a port that you are not using for anything else. But so long as the two servers are configured to connect using the same port, it should work.
This designates that the server is to make an SSL connection to the port that is defined. This does not mean the server can only connect via SSL unles secureonly is also on.
Example:
/as server ChatNow set secure on
Make sure that the connect out port is set to an SSL port on the other server.
Mandates that the connect be made via SSL. A regular connection will not be permitted
Example:
/as server ChatNow set secure on
Make sure that you also have SECURE set to on.
The serial number of the remote server is used to authenticate the server to server link.
Example:
/as server ChatNow set serial 104-0003-953
Note: The serial number command has replaced the inpass and outpass commands of previous versions.
This setting allows ConferenceRoom to verify that the incoming IP address from a connecting server matches the host IP's address as the same settings you have set in the configuration on your server.
Example:
/as server ChatNow set strict on
This is useful for servers that have static IP addresses. If strict is off then it will not check to see if the IP address matches what it expects.