The .include directive is available so you can store additional configuration lines in separate files:
This should contain the name(s) and email(s) of the services administrator(s) - just to tell users who to contact w/ questions:
The first field is the name you want the services server to be. It should match the C/N lines of the hub server. The second field is the text info for the services (it corresponds to the third field in a server's M line):
This line should contain three fields. In order, the password for the connection, the hostname (or IP address) of the hub server to connect to, and the port to connect at. If no port is specified, DefaultHubPort
, specified in settings.conf, is used. You may put as many S: lines as you wish. If services cannot connect to the first server, or gets disconnected, it will move onto the next one# and so on.(The password must match the C/N lines of the hub server).
V: lines specify a virtual hostname to bind to when connecting to a remote site. IP Addresses can be used as well. If multiple V: lines are given, only the first is used
O: lines specify users who will have access to Hybserv. The first field should contain the user's username@host. The second should be a password that the user will be required to register with in order to use services. The third field is the nickname of the user (ie: the nickname that will appear in the partyline). Finally, the fourth field is a list of flags the user will have, entitling them to different privileges. All four fields must be given, or Hybserv will not consider the line valid.
NOTE: All passwords should be encrypted if CRYPT_OPER_PASSWORDS is defined in config.h (which is the default) - use mkpasswd tool to generate the password.
Available flags are:
- a - Administrator - combination of "f", "o", and "d" flags. Many more commands are available (.help)
- d - Allows user to use DCC CHAT service. If OpersOnlyDcc is enabled, and the user doesn't have an "o" flag, they won't be allowed to use DCC CHAT.
- e - Exception flag - Any user with this flag will not be KILLed or GLINEd by Hybserv if someone attempts to do so.
- f - Friend - when an administrator SECUREs a channel, "f" users will be opped if they are registered at the time.
- g - Gives user gline privileges, allowing them the use of the GLINE and UNGLINE commands.
- j - Allows user to JUPE and UNJUPE servers.
- o - Normal Operator - automatic "f" flag. Many more commands are available (.help).
- s - Services Administrator - most powerful flag. This flag is a combination of every other flag (except +j and +g), and it also gives you access to the most powerful OperServ commands - use sparingly.
Note: Anyone with a O: line may use the IDENTIFY and HELP commands no matter what flags they have.
C: lines specify channels that OperServ
will monitor. The first field is the name of the channel:
I: lines specify restricted hostmasks. The fields, in order: the hostmask, the number of connections allowed from the hostmask, whether to (1) gline the entire host instead of user@host when advanced flood is detected or not (0).
The last field has no effect if ADVFLOOD_GLINE was not enabled at compiletime, hence its specification is optional.
Allows only 3 connections from cloneguy@*.clones.org, gline just the offending user if they start advanced floods, not the entire host:
Allows a total of 6 users from the .blah.com domain, gline the entire host if they're flooding, not just the offending user:
B: lines are to specify TCM bots to link to. The fields are, in order, the hostname of the box the TCM is running on, the nickname of the TCM, the password to use for linking to the TCM, and the port the TCM is listening on. If you don't specify a port, the default of 6800 is used. Make sure that the TCM bots you list here have an N: and C: line in their userlist.cf, matching the password, nick (OperServ
), and hostname that Hybserv is running on.
L: lines give remote TCM bots access to link to Hybserv. The fields are the hostmask of the remote TCM's box, the nickname of the TCM, and the password for connecting. Please see the file TCM-LINKING if you have no clue what a TCM is, or are not sure how to get a TCM to link to Hybserv.
P: lines specify ports to listen on for tcm or user connections. The fields are the hostmask to accept (optional), the port number to listen on, and the type of connection to allow (ie: tcm or users). The hostmask field is only used if the
connection is for users, since the tcm hostmask is given in the first field of the L: line:
Listens for tcm bot connections on port 6900:
Allows users matching *.com to connect on port 5555:
Allows anyone to connect on port 5656:
J: lines specify server jupes (servers that match a jupe line will not be allowed to connect to the network). The first field should contain the name of the server. The second is the reason that the server is juped. The third field is the nick of the oper who set the jupe, and possibly the date:
J:bad.server.com:you were bad:SideWnder 1998/09/20
J:slow.server.com:too much lag =P:AnOper 1990/02/02
G: lines specify users who are banned from the network (glined). The first parameter is the hostname. It may also include a user@host. The second parameter is the reason the user is glined. Finally, the third field is the user who set the gline, and possibly the date:
G:*.badguy.com:You are a bad guy:SideWnder 1998/09/20
M: lines are auto-connecting lines for Hybserv - it will try to connect those leaves in field 4 to server in field 2 after split time in field 5.