IRC Operator Manual v1.2
Network: Avade IRC Network
Authors: DreamHealer, PJKevin
Last Revised: February 14 2010 by DreamHealer
This manual will cover:
Chapter 1. Avade Network
1.1 Introduction
1.2 New Oper
1.3 History
2. Modes
UserModes 2.1. How to set usermodes
2.1.1 +i invisible
2.1.2 +w wallops
2.1.3 +s server messages
2.1.4 +r registered nick
2.1.5 +R block non-identified users
2.1.6 +k kill messages
OperModes 2.2
2.2.1 +o IRC operator
2.2.2 +c client connects/quits
2.2.3 +n routing messages
2.2.4 +f floodwarnings
2.2.5 +y see stats requests
2.2.6 +d debug messages
2.2.7 +a services administrator
2.2.8 +A server admin
2.2.9 +b chatops
2.2.10 +g globops
2.2.11 +h helpop
2.2.12 +e dccallow
ChannelModes 2.3. How to set channelmodes
2.3.1 +b channel ban
2.3.2 +i invite only
2.3.3 +k keyword
2.3.4 +l limit
2.3.5 +m moderate
2.3.6 +n no external messages
2.3.7 +o channel op
2.3.8 +p private
2.3.9 +r registered channel
2.3.10 +R block non-identified users
2.3.11 +M moderate non-identified users
2.3.12 +s secret
2.3.13 +t topic changes is op only
2.3.14 +v voice
2.3.15 +c no colors
2.3.16 +O only IRCop's can join
IRC Operator 3. IRC Operator Access Levels
3.1 Local Operator
3.2 Global Operator
3.4 Server Administrator
3.3 Services Operator
3.5 Services Administrator
3.6 Services Root Administrator
Routing 4. Routing
4.1 About Routing
4.2 /squit
4.3 /connect
Server 5. IRC Operator Server Commands
5.1 /oper and operhost
5.2 /who
5.3 /wallops, /chatops, /locops, /globops
5.4 /kill
5.5 /kline and /unkline
5.6 /zline
5.7 /Stats
5.8 /version
5.9 /trace
5.10 /lusers
5.11 /links
5.12 /samode
5.13 /sajoin
5.14 /rehash
5.15 /restart
5.16 /die
5.17 /close
IRC Operator Services Commands
6.1 NickServ
6.1.1 LIST
6.1.2 FLIST
6.1.3 FLUSH
6.1.4 MARK
6.1.5 AUTHINFO
6.1.6 FREEZE
6.1.7 GETEMAIL
6.1.8 GETPASS
6.1.9 HOLD
6.1.10 LISTEMAIL
6.1.11 DELETE
6.1.12 FORBID
6.1.13 SET
6.1.14 LISTCHANS
6.1.15 LISTNICKS
6.2 ChanServ
6.2.1 LIST
6.2.2 FLIST
6.2.3 EXPEL
6.2.4 LEVEL
6.2.5 MARK
6.2.6 TOPIC
6.2.7 CLOSE
6.2.8 FREEZE
6.2.9 GETPASS
6.2.10 HOLD
6.2.11 OFFICIAL
6.2.12 DELETE
6.2.13 SET
6.3 OperServ
6.3.1 CLONES
6.3.2 GLOBAL
6.3.3 IDENTIFY
6.3.4 LISTADM
6.3.5 SETTINGS
6.3.6 STATS
6.3.7 UINFO
6.3.8 UPTIME
6.3.9 VERSION
6.3.10 OPERHELP
6.3.11 CHANGES
6.3.12 AKILL
6.3.13 PASS
6.3.14 SEARCH
6.3.15 TRIGGER
6.3.16 IGNORE
6.3.17 JUPE
6.3.18 SOP
6.3.19 SGLINE
6.3.20 SQLINE
Theory 7. Being an IRC Operator
7.1 Opering in general
7.2 Dealing with problematic users
7.3 KILLS/AKILLS/KLINES
7.4 FORBID/FREEZE/CLOSE
7.5 If a user reports/threatens to report you
7.6 Teamwork
1.1 Introduction
Welcome to the Avade IRC Network, this manual will explain how things work on this
new nice network in a hopefully understandable way. This manual will also be
considered a reference to both IRC operators and official helpers, there are also things
explained that could be nice to know as a user on Avade IRC Network so you know
how stuff works. This manual is constantly being updated so please contact the Support
& Community team for a revised version at least once in 2 months and keep yourself
updated. Happy Opering!
The Avade Network Administration
1.2 New Oper
Congratulation to your new found access to one of the servers currently linked to Avade
Network, to give a few pointers to advance your access I can summon them by saying:
1. regulary check your staff mail and memos
2. be active, and help users
3. if you figure out a way to expand our network, please do so.
You will be facing new challenges to go through. Please remember that you represent
the network and therefore it is your responsibility to upkeep our image.
1.3 History
The Avade IRC Network was founded in the beginning of 2010 as part of other projects
run by DreamHealer and BabyAnGeLL. Services was pretty much already developed
and bugfixed so it just waited for a network to be run on.
The basic idea of the network was to have a nice place to invite friends and to have fun.
Usermodes.
2.1 How to set usermodes
Every mode has a purpose and a function that you as a user can find useful for the
situations you will find yourself in. (Section 2 in this manual will only cover usermodes
and their uses.)
To set a usermode you must type like this:
/mode YourNick +-modes
i.e. /mode DreamHealer +Ri
2.1.1 +i invisible
The +i mode makes a user invisible to other users that doesnt know the users nick or are
on the same channel as the user. The mode doesnt make the user invisible in a channel.
The mode will make the user invisible from /who and /names command
2.1.2 +w wallops
The +w mode makes a user recieve wallops that are sent from IRC operators. wallops
are network wide messages that are used to easily communicate with eachother like a
communication method but also a news method for those users who are interested.
However after the introduction of other methods of communication such as globops and
locops wallops are seldom or never used.
2.1.3 +s server messages
This mode will make you recieve server messages, this mode can sometimes turn into a
flood if theres alot happenning at the time and should be used with care by non-opered
users.
2.1.4 +r registered nick
This mode can only be set by an U:lined server, and it makes the nick you are currently
using identified both to U:lined services and in /whois. When set it will show this in a
/whois:
DreamHealer has identified for this nick
As soon you have successfully used the /nickserv IDENTIFY command, services will
set your nick +r and it will stay +r until you reconnect or use /nick command.
2.1.5 +R block non-identified users
This is a very useful mode if you are flooded with floodbots in private or just want to
avoid unregistered nicks. The mode will stop any message from a non-identified
user(-r user) This includes: /msg, /notice, /ctcp. An IRC Operator that hasnt identified
his nick yet, but are fully opered is able to message any user that are set +R.
2.1.6 +k kill messages
This mode will let any user set +k to recieve kill messages, it can cause a flood and isnt
recommended for non-opered users.
OperModes 2.2
2.2.1 +o IRC operator
This mode can only be set by using the /oper command. by successfully using the /oper,
you are an IRC operator and can access various commands such as /kill, /squit, /connect.
To use /oper command you must have been added with your own O:line on the server
you currently are connected to and then type like this:
/oper nick pass
After that your nick will get another line in the /whois info:
DreamHealer is an IRC Operator
If you are a local operator you will be set with a capital +O after /oper up and the /whois
info will only be available on the server you currently are connected to, due to that you
only are a LOCAL operator. As a local operator you wont be able to access any operserv
command or any oper commands set in chanserv or nickserv, even if you do have
services access.
2.2.2 +c client connects/quits
This mode will make an IRC Operator to recieve info when a user connects or
disconnects from the server the oper is currently connected to. On relatively small
networks this can be useful for server monitoring, but on bigger networks this can cause
a flood and be quite annoying.
2.2.3 +n routing messages
This mode will enable an IRC operator to view server routing notices
2.2.4 +f floodwarnings
This mode will enable an IRC operator to get flood notices generated by the server the
IRCop currently are connected to. A notice will appear whenever someone disconnects
cause of "excess flood" and if a user triggers the builtin channel flood protection.
2.2.5 +y see stats requests
This mode enables IRC Operators to see stats/links/admin requests
2.2.6 +d debug messages
This mode is for viewing debug messages
2.2.7 +a services administrator
This mode will enable the use of /samode which can access any channelmode available
and also /sajoin to join channels. It will also add an additional info to your /whois if you
are set with this usermode:
DreamHealer is an IRC Operator - Services Administrator
Please notice that all access to services is set in services, are set to a certain registered
nickname, so by having access to this usermode will not enable any extra features in
services.
2.2.8 +A server admin
Users set with this usermode will also automaticly get set with usermode +a this mode
will let the user to see +s(secret) and +p(private) channels. Some additional info will
also be shown in your /whois if you use this mode:
DreamHealer is an IRC Operator - Server Administrator
2.2.9 +b chatops
This mode will let the user to see /chatops messages
2.2.10 +g globops
This mode is used to view /globops messages, you must be a global IRC
operator to be able to enable this feature.
2.2.11 +h helpop
This mode will let the IRC operator to show up in a /stats p request as to
be available to help:
DreamHealer (Pintuz@AvadeNET) Idle: 720
2.2.12 +e dccallow
If the server stops any dcc file transferes, a notice will be sent to all IRC operators that
are set with usermode +e
ChannelModes 2.3. How to set channelmodes
To be able to set any channelmode you either must be oped(@) or be an IRC Operator
with access to usermode +a(section: 2.2.7)
To change a channelmode you must type like this:
/mode #chan +-modes 3.1 Local Operator
A local operator is where newbie opers start from but basically this does not apply to all
IRC Networks. A local operator's oper line is different than other levels by the lowercase
'o' in the server's ircd.conf file. Local operators basically only can be noted if you are on
the same server as the oper. Example, if Icelander is a local operator on icer.* and I am
on dream.*, I will not see the extra line on his WHOIS output unless I type /whois icer.*
Icelander
Note that local operators can add local klines, perform local squits and connects, see
invisible '+i' users, and remove users from the server he is opered on. In other words,
local operator's action does not affect the network as a whole.
3.2 Global Operator
Global operators are recognised no matter even if you're on a different server. A global
operator's O:line is configured with a capital 'O' in the ircd.conf file. They're able to
perform global kills (remove users even if they are on a different server), view channel
access lists (AOP/SOP/COUNT).
Generally speaking, their actions can affect the network on the whole.
3.4 Server Administrator
Server Administrators are recognized by the oper mode +A. They are also automatically
set to +a. They are the ones who run and maintain the server making sure it stays in
good condition on Avade. Server Administrators are the only ones able to add and
remove IRC Operators on their server. In addition to the Services Administrator
commands, they are also able to view +s(secret) and +p (private channels).
3.3 Services Operator
Services Operator's has some extra commands in services to help them in their work on
the network. They may place akills and search logs etc.
3.5 Services Administrator
Services Administrators are also known as SA under the oper mode +a. They are able to
view NickServ access lists, mass kick channels, and change channel modes even without
the need of being opped or even in the channel using /samode. They are also able to
force join any channel without being invited using /sajoin.
They are also able to retrieve a nick/channel password (GETPASS) which is a common
reason why users look for them, freeze nicks and channels and close channels. To view
a list of available SAs, you can type /motd services.*.
3.6 Services Root Administrator
On some networks, they are known as Services Root Administrators or SRA for short.
They have the highest access to services. Most problems with services can be easily
solved by a SA but there are times a SRA is required for other tasks. SRAs are the ones
who will select Services Administrators and Services Operators.
There are also other teams on Avade like NO, HR, SC, Webmasters and Abuse. Each
team has its own lead and some teams permit non-opers in their staff. Some teams like
Abuse and NO require a certain level of access to services and some teams like SC don't.
Routing 4. Routing
4.1 About Routing
Routing is the key to maintain a network that consists of more than one server. This
work is on the shoulders of the IRC Operators and can be difficult to get well and
synched.
Routing is a complete science and is hard to completely summon in a few words. The
first maintenance can only be set by a root on each machine that will link together to a
network. Running an ntpd on each machine is requested to be able to link 2 bahamut
servers together, if a server is desynched and/or lagged to the rest of the network it will
act wierd and
some modes will exist on some servers but not on others and so on.
4.2 /squit
The /squit command is used to delink a server that is already linked to the network.
Youre also abled to squit servers even though you may not be on either two. A general
reminder needs to be pointed here that when squitting, you must squit from the far end
of the link. Lets take a look at the following structure of a network:
kernel.* <----> fire.* <----> dreams.*
Given the above example, kernel.* and dreams.* are leaf servers and fire.* is the hub.
If youre on kernel.* and wish to squit dreams.* with the reason rerouting, you will type:
/squit dreams.* rerouting server
If you are on kernel.* want to squit kernel.* from fire.*, you will then type:
/squit fire.* reasonhere
Note that we are delinking kernel.* from fire.* and therefore, fire.* is the far end. The
network starts from the server you are connected to, so if you want to squit the server
you are connected to which is kernel.*, you have to squit the hub it is linked to which is
fire.* in the above example.
Here is an example on how to squit hubs:
kernel.* <----> fire.* <----> dreams.*
|
|
icer.* <----> vikings.* <----> firestone.*
If you're on icer.* and want to split vikings.* from fire.*, you will type the following:
/squit fire.* reason
The result would be:
kernel.* <----> fire.* <----> dreams.*
icer.* <----> vikings.* <----> firestone.*
4.3 /connect
The connect command is used to connect servers that have splitted though it may
autoconnect. It must be reminded that the server youre connecting must have the right
C/H/N lines in order for it to link.
The first variant of this feature is to connect the server you are connected to, to a hub on
your network, say perhaps your leaf splits from the hub and want it to link back, or to
another hub on your network.
Example:
icer.* global.*
So, if youre on icer.*, you will type /connect global.* and will link them together:
icer.* <----> global.*
If theres a split between 2 hubs, and you want to reconnect them, you will be using the
command with a different parameter using /connect DestinationServer.* 7000
OriginServer.*. On Avade, port 7000 is opened on a hub server and closed on a leaf
server. However, the port may not be the same for every hub and you will need to
contact the hub admin to find out. Referring to the example below:
kernel.* <----> fire.* <----> dreams.*
icer.* <----> global.* <----> dragon.*
fire.* and global.* are 2 hubs in a split indicating the netsplit. So if youre on kernel.*
and want to connect the 2 hubs, you would need to do the following command:
/connect global.* 7325 fire.*.
Server 5. IRC Operator Server Commands
This section will explain the usage of various oper server commands. Please note that
these commands must be used with care and shouldnt be abused in any way. You have
to be opered up before you can use any of these commands.
Abusing you oper access will result in disciplinary actions, and in worst case delinking
of your server so please study what you cant do aswell as what you can do.
5.1 /oper and operhost
This command will allow you IRC operator access to the server you are currently
connected to. To be able to successfully issue this command you have to have your own
O:line on the server you are connected to.
Please note that /oper will only give you access to the server and not services.
/oper dreamhealer mypass
To be able to access the operhost that is set on a server, you must have an O:line and a
operhost supported I:line then type like this:
/server servername.avade.net:port portpass:opernick:operpass
5.2 /who
This command is one of my favourites, its most sweet. By using this command you may
look into any channel and see who is inside it or search the whole net for a certain host,
ip, usermode, nick, userid or realnamefield.
The diffrent searchflags you can use is:
+a: user is away
/who +a *.se
/who +ca #chan
+c: user is in channel
/who +c #channel
+g: user has string in their realnamefield
/who +g *string*
/who +cg #chan *string*
+h: user has string in their host
/who +h *string*
/who +ch #chan *string*
+i: user has ip or iprange
/who +i ip.ip.ip.*
/who +ci #chan ip.ip.ip.*
+m: user has usermode set
/who +m UserMode
/who +cm #chan UserMode
+n: user has string in their nick
/who +n *string*
/who +cn #chan *string*
+s: user is connected to server (servers full name must be used)
/who +s server.se.eu.avade.net
/who +cs #chan server.se.eu.avade.net
+u: user has string in their username
/who +u *string*
/who +cu #chan *string*
+C: show first visible channel the user is in
/who +C Nick
+M: search in the channels that you are inside
/who +M *.se
Please practice this command regulary, because its a good and easy way to find bots or
other unallowed activities as akill-evaders or clones.
5.3 /wallops, /chatops, /locops, /globops
This section will explain how opers can communicate networkwide.
A local operator is only allowed to use /locops, this command will send a notice to all
current IRC operators on the server it was issued.
/locops MessageHere
Global operators have access to issue wallops, chatops or globops. A wallop can be
recieved by any user set with usermode +w while chatops will arrive to IRC operators
set with usermode +b, and globops will arrive to all IRC operators set with usermode +g.
To be able to send with these message mediums you have to be set with the usermode
that are required to be able to recieve a message with each medium.
/wallops MessageHere
/chatops MessageHere
/globops MessageHere
A strict rule here that what is said on globops/chatops/wallops should NOT be shared
with non IRC Operators, failure to abide this rule may result your O:line being revoked.
5.4 /kill
A kill will disconnect a certain user from the network, even if the user is an oper or not.
Note that you cannot kill U:lined clients eg. services.
/kill Nick ReasonHere
Before issuing this command please make sure the user really is breaking the network
AUP
5.5 /kline and /unkline
This is a useful command to ban someone from your server. Note that this command
only works as a local command and will not affect any users on different servers even if
you are a global operator.
To issue this command you must type:
/kline Nick :ReasonHere
/kline user@host :ReasonHere
Before issuing this command please make sure the user really is breaking the network
AUP
5.7 /Stats
This command is for retrieving various information about a server and its configuration.
The command can retrieve info from both server:lines and stats from the server. If you
dont provide a servername the command will automatically show information about the
local server that you currently are connected to.
Syntax:
/stats
/stats u irc1.*
Info shown:
Server Up 29 days, 17:47:23
End of /STATS report.
Letters:
a - Shows local akill list
c - Shows C/N lines
b - Shows B lines
d - Shows D lines
e - Shows E lines
f - Shows F lines
h - Shows H/L lines
i - Shows I lines
K - Shows K lines (or matched klines)
k - Shows temporary K lines (or matched temp klines)
L - Shows IP and generic info about [nick]
l - Shows hostname and generic info about [nick]
m - Shows commands and their usage
o - Shows O/o lines
p - Shows opers connected and their idle times
r - Shows resource usage by ircd (only in DEBUGMODE)
t - Shows generic server stats
U - Shows U:lined servers
u - Shows server uptime
v - Shows connected servers and their idle times
y - Shows Y lines
z - Shows memory stats
? - Shows connected servers and sendq info about them
Some of the info are restricted and can only be used if you are opered up.
5.8 /version
This command is for retrieving the version of a server and how its been compiled. The
version reply is showing not only the servername and version- number, but also has a
handful letters that can tell how a server is compiled.
Letters:
A SENDQ_ALWAYS
c CHROOTDIR
C CMDLINE_CONFIG
d DO_ID
D DEBUGMODE
e LOCOP_REHASH
E OPER_REHASH
f FOLLOW_IDENT_RFC
F HIDE_FAKES
g SUN_GSO_BUG
G SHOW_GHOSTS
H HUB
i SHOW_INVISIBLE_LUSERS
I NO_DEFAULT_INVISIBLE
K OPER_KILL
k LOCAL_KILL_ONLY
L LEAST_IDLE
m M4_PREPROC
M IDLE_FROM_MSG
N DELAY_NICKS
p CRYPT_OPER_PASSWORD
P CRYPT_LINK_PASSWORD
N NPATH
r LOCOP_RESTART
R OPER_RESTART
s SECUNREG
S ENABLE_SUMMON
t OPER_REMOTE
T TRACE_STATS
u IRCII_KLUDGE
U ENABLE_USERS
V VALLOC
w NOWRITEALARM
X UNIXPORT
Y USE_SYSLOG
8 V28PlusOnly
5.9 /trace
This command can be used in 2 different ways, the first one is to use trace on a user on
the network:
Syntax:
/trace BabyAnGeLL
Info:
Link bahamut-1.8(06) babyangell phoenix.az.us.avade.net
[phoenix.az.us.avade.net] Operator opers BabyAnGeLL!Baby@AvadeNET 12
[phoenix.az.us.avade.net] babyangell End of TRACE
As you can see above the command shows where the user is connected compared to you
are connected, so basically you will see the route any message will take where through
the network for it to arrive to the nick you traced.
Also it shows some further information about the user:
User users BabyAnGeLL[Baby@AvadeNET] 29
^ ^ ^ ^
^ ^ ^ SendQ
^ ^ Nick[userid@host]
^ Connection Class
What this connection is.
This way you also are able to find lag, due to that during the "route" the servers involved
with the route are sending you info only about the next server they dont send info about
themselves. so if the whole trace would have looked like this instead:
Link bahamut-1.8(06) babyangell phoenix.az.us.avade.net
[phoenix.az.us.avade.net] Operator opers BabyAnGeLL!Baby@AvadeNET 12
[phoenix.az.us.avade.net] babyangell End of TRACE
Then we would know that the leaf Im currently on(dreams.*) sent info about phoenix.*
being the next server in the chain of linked servers, then phoenix.* sent the info about
the nick BabyAnGeLL, and if the process stops in the middle without showing the user
info then we found a link between 2 servers that has lag on it
The other way trace can be used, is on a server:
/trace server.*
This will show all current connections and their connectionclasses and so on. If you
arent opered up you will only see operators that arent set with usermode +i. This will
also show info about how many users and servers the server is holding.
Server NONE 0S 143868176C phoenix.az.us.avade.net *!*@phoenix.az.us.avade.net 92
^ ^ ^ ^ ^ ^ ^
^ ^ ^ ^ ^ ^ SendQ
^ ^ ^ ^ ^ Connected to server in route
^ ^ ^ ^ Full servername
^ ^ ^ Number of clients connected to the server or beyond the server if HUB
^ ^ Number of servers links to the server or beyond the server if HUB
^ Connection Class
Is connected as a server
5.10 /lusers
This is a command for retrieving information about how many users and servers that
currently are connected to the network and the server you currently are connected to.
This tool is also useful if you want to see if there currently is any resynching or perhaps
a split. If there is a split you can see that by checking the current servercount and
usercount, and if a server is synching the usercount is increasing fast, however this
resynching process are impossible to see on small networks due to that it can synch very
fast depending on the servers and the connection between them.
If you monitor a server resynch on a big network, and then you can see its synching
1000 to 2000 users/sec so the chance of being able to monitor a resynch on a small
network is fairly low.
5.11 /links
This is a tool to retrieve information about how the network is currently linked server by
server. To read the links list is very simple, its devided so that all servers connected to a
hub is in the next field to the right and so on. if the servers are linked like this:
fire.hub-se.eu.avade.net
viking.hub-se.eu.avade.net
icer.se.eu.avade.net
irc2.avade.net
If this is the case we easily can see that viking and irc2 is connected to fire and that icer
is connected to viking by the way they are spaced to the right. Like this:
fire.hub-se.eu.avade.net
^ ^
^ ^
^ viking.hub-se.eu.avade.net
^ ^
^ ^
^ icer.se.eu.avade.net
^
irc2.avade.net
Links is very useful during routing and rerouting to see how servers currently are linked.
For more info please consult your network routing team. If you are opered up you will
be able to see U:lined hidden servers such as services and stats.
5.12 /samode
This is a tool to force channel modes without being op(@) or even inside the channel.
The command work like the common /mode command and should mainly be used to
moderate flooded channels.
Syntax: /samode #dreamhealer +m
This command wasnt made for opers to fool around and showing off their access with.
Its only use is to be able to manage flooded and/or frozen channels.
On Avade Network a channel belongs to the founder until the channel brakes any
network rule, if the channel isnt breaking any rules the channel staff is allowed to deny
any oper access to the channel. The channels are run by their staff as they see fit within
network boundaries.
Before issuing this command please make sure the channel really is breaking the
network AUP.
5.13 /sajoin
This tool is used to force opers to join the channel where modes like b/i/k/l restricts them
from entering. Normally this can be used if a channel is being taken over, channel
operators avenging IRCOps from doing their duties (if needed). Like /samode, this mode
is used only by Services Admins and above.
Syntax: /sajoin #dreamhealer
This command wasnt made for opers to fool around and showing off their access,
disturb the privacy of the channel or evade channel bans. On Avade Network a channel
belongs to the founder until the channel breaks any network rule, if the channel isnt
breaking any rules the channel staff is allowed to deny any oper access to the channel.
The channels are run by their staff as they see fit within network boundaries.
Before issuing this command please make sure the channel really is breaking the
network AUP.
5.14 /rehash
Rehash is a command to make the server reload configuration files. This command has
several uses that I will list below:
This will reload the servers ircd.conf file:
/rehash
This will reload the ircd.motd file to get the new message of the day if you changed
it in any way:
/rehash motd
This will remove temporary k:lines:
/rehash tklines
This will remove throttled ips:
/rehash throttles
This will make the server reread the /etc/resolv.conf file:
/rehash dns
This will Perform a garbage collecting of excess memory:
/rehash gc
5.15 /restart
Restart is a command that will do as it is named, if you do have the correct flag in your
O:line and you know the restartpassword which are listed in the x:line you are able to
restart the server by typing this:
/restart RestartPassHere
Normally you wont need to use this command, nor have access to it.
5.16 /die
The die command is used to kill the server, you need the right flag and the die password
provided in the x:line to be able to kill the server:
/die DiePassHere
Normally you wont need to use this command, nor have access to it.
5.17 /close
This command is used to close all connections from clients that have not fully registered
yet.
/close
IRC Operator Services Commands
6.1 NickServ
6.1.1 LIST
This command will list registered nicknames searched by a pattern.
Syntax: /nickserv LIST *
/nickserv LIST *pattern*
WARNING: Misuse of the command can lead to severe punishment including removal
of access and O:line.
6.1.2 FLIST
This command lists all registered nicks which matches the given pattern with the format
of nick!user@host. Private nicks will only be able to be seen by CSOps. Nicks with
NOEXPIRE on will have a ! prepended to the nickname and frozen nicks will be
prepended by a *.
If the options NOEXPIRE, FREEZE or FORBIDDEN are given, then only the
respective nicks will be displayed. This command is available to CSOps and
above only.
Syntax: /nickserv FLIST *
/nickserv FLIST *pattern*
/nickserv FLIST *pattern* [HELD|MARKED|FORBIDDEN|FROZEN]
WARNING: Misuse of the command can lead to severe punishment including removal
of access and O:line.
6.1.3 FLUSH
This command will flush all authinfo from a nickname, the user needs to set a new email
on his nick after a staff has used this command on his nickname.
Syntax: /nickserv FLUSH Nickname
WARNING: Misuse of the command can lead to severe punishment including removal
of access and O:line.
6.1.4 MARK
This command is for marking a nick as under observation. While a nick is marked the
nick will be immune of SENDPASS and GETPASS.
Syntax: /nickserv MARK nickname ReasonHere
/nickserv MARK -nickname
/nickserv MARK *
WARNING: Misuse of the command can lead to severe punishment including removal
of access and O:line.
6.1.5 AUTHINFO
This command is for retrieving all auth information available on a nickname. Do not
give out users auth codes as they servs a purpose to make their nicks securely registered.
Syntax: /nickserv AUTHINFO nickname
WARNING: Misuse of the command can lead to severe punishment including removal
of access and O:line.
6.1.6 FREEZE
FREEZE is a temporary hold of the nick. However, like a nickname that has not been
identified after a certain period, it expires. FREEZE is normally used on abusive users
who have abused services or have broken network policies despite several warnings.
This command is limited to SAs and above and only the SA who set it can remove it.
Syntax: /nickserv FREEZE DreamHealer User was found massmessaging
/nickserv FREEZE -DreamHealer
/nickserv FREEZE *
WARNING: Misuse of the command can lead to severe punishment including removal
of access and O:line.
6.1.7 GETEMAIL
This command will retrieve the email address of a registered nickname.
Syntax: /nickserv GETEMAIL nick
WARNING: Misuse of the command can lead to severe punishment including removal
of access and O:line.
6.1.8 GETPASS
In the event a user has forgotten the user password and is unable to use SENDPASS
because he forgot the user email address, GETPASS is used to recover the password
provided encryption is not enabled. This command is limited to SAs and above.
Syntax: /nickserv GETPASS nickname
WARNING: Misuse of the command can lead to severe punishment including removal
of access and O:line.
6.1.9 HOLD
This command is to force services not to expire the nick in the event it is not identified
in 30 days. This option is normally used for IRC Operators and/ or network staff who
may go on long vacation.
Syntax: /nickserv HOLD DreamHealer Nick isnt allowed to expire
/nickserv HOLD -DreamHealer
/nickserv HOLD *
WARNING: Misuse of the command can lead to severe punishment including removal
of access and O:line.
6.1.10 LISTEMAIL
This command will list all registered nicnames that matches an email pattern.
Syntax: /nickserv LISTEMAIL *pattern*
WARNING: Misuse of the command can lead to severe punishment including removal
of access and O:line.
6.1.11 DELETE
This command used alone deletes a nickname from the database.
Syntax: /nickserv DELETE nickname
WARNING: Misuse of the command can lead to severe punishment including removal
of access and O:line.
6.1.12 FORBID
This command disables the nick from being used or registered. If the nick is registered
the registration will be lost.
Syntax: /nickserv FORBID DreamHealer Nick isnt allowed to be registered
/nickserv FORBID -DreamHealer
/nickserv FORBID *
WARNING: Misuse of the command can lead to severe punishment including removal
of access and O:line.
6.1.13 SET
This will let a staff member force change a nicknames services options like ENFORCE
or NOOP.
Syntax: /nickserv SET Nickname OPTION ON|OFF
WARNING: Misuse of the command can lead to severe punishment including removal
of access and O:line.
6.1.14 LISTCHANS
This command is used for listing all channels a nickname has access to.
Syntax: /nickserv LISTCHANS nickname
WARNING: Misuse of the command can lead to severe punishment including removal
of access and O:line.
6.1.15 LISTNICKS
This command is used to list all nicknames registered under the same email.
Syntax: /nickserv LISTNICKS nickname
WARNING: Misuse of the command can lead to severe punishment including removal
of access and O:line.
6.2 ChanServ
6.2.1 LIST
This command will list registered channels searched by a pattern.
Syntax: /chanserv LIST *
/chanserv LIST *pattern*
WARNING: Misuse of the command can lead to severe punishment including removal
of access and O:line.
6.2.2 FLIST
This command lists all registered nicks which matches the given pattern with the format
of nick!user@host. Private nicks will only be able to be seen by SAs. Nicks with HOLD
flag on will have a ! prepended to the nickname and frozen nicks will be prepended
by a *.
If the options HELD, MARKED, FROZEN or FORBIDDEN are given, then only the
respective nicks will be displayed. This command is available to SAs and above only.
Syntax: /chanserv FLIST *
/chanserv FLIST *pattern*
/chanserv FLIST *pattern* [HELD|MARKED|FORBIDDEN|FROZEN]
WARNING: Misuse of the command can lead to severe punishment including removal
of access and O:line.
6.2.3 EXPEL
This command is used for removing modes or users from a channel.
Syntax: /chanserv EXPEL #Avade BANS
/chanserv EXPEL #Avade MODES
/chanserv EXPEL #Avade OPS
/chanserv EXPEL #Avade VOICES
/chanserv EXPEL #Avade USERS
WARNING: Misuse of the command can lead to severe punishment including removal
of access and O:line.
6.2.4 LEVEL
This command will make a channel restricted to all that havent a certain level of services
access.
Syntax: /chanserv LEVEL #Avade OPER
/chanserv LEVEL #Avade SOP
/chanserv LEVEL #Avade SA
/chanserv LEVEL #Avade SRA
/chanserv LEVEL #Avade MASTER
/chanserv LEVEL #Avade NONE
WARNING: Misuse of the command can lead to severe punishment including removal
of access and O:line.
6.2.5 MARK
This command is for marking a channel as under observation. While a nick is marked
the nick will be immune of SENDPASS and GETPASS.
Syntax: /chanserv MARK #Avade Something fishy going on
/chanserv MARK -#Avade
/chanserv MARK *
WARNING: Misuse of the command can lead to severe punishment including removal
of access and O:line.
6.2.6 TOPIC
This command will force change the topic of a channel and overrides and topiclock
settings currently set in the channel.
Syntax: /chanserv TOPIC #Avade Your topic was breaking the network AUP.
WARNING: Misuse of the command can lead to severe punishment including removal
of access and O:line.
6.2.7 CLOSE
This command will close a channel temporarily or permanently. Closing a channel over
its expiration date will result in the channel getting expired, so to close a channel longer
than that you need to HOLD the channel.
Syntax: /chanserv CLOSE #Avade 5m Channel is closed (close for 5 minutes)
/chanserv CLOSE #Avade 5h Channel is closed (close for 5 hours)
/chanserv CLOSE #Avade 5d Channel is closed (close for 5 days)
/chanserv CLOSE #Avade 0 Channel is closed (close permanently)
/chanserv CLOSE *
WARNING: Misuse of the command can lead to severe punishment including removal
of access and O:line.
6.2.8 FREEZE
FREEZE is a temporary hold of the nick. However, like a nickname that has not been
identified after a certain period, it expires. FREEZE is normally used on abusive
channels who have abused services or have broken network policies despite several
warnings. This command is limited to SAs and above and only the SA who set it can
remove it.
Syntax: /chanserv FREEZE #Avade Channel is Frozen
/chanserv FREEZE -#Avade
/chanserv FREEZE *
WARNING: Misuse of the command can lead to severe punishment including removal
of access and O:line.
6.2.9 GETPASS
In the event a user has forgotten the channel password and is unable to use SENDPASS
because he forgot the user email address, GETPASS is used to recover the password
provided encryption is not enabled. This command is limited to SAs and above.
Syntax: /chanserv GETPASS #Channel
WARNING: Misuse of the command can lead to severe punishment including removal
of access and O:line.
6.2.10 HOLD
This command is to force services not to expire the channel in the event it is not
identified in 30 days.
Syntax: /chanserv HOLD #Avade Channel isnt allowed to expire
/chanserv HOLD -#Avade
/chanserv HOLD *
WARNING: Misuse of the command can lead to severe punishment including removal
of access and O:line.
6.2.11 OFFICIAL
This command is for marking a channel as an official network channel. This should only
be used for official help channels or official network channel.
Syntax: /chanserv OFFICIAL #Avade
/chanserv OFFICIAL -#Avade
WARNING: Misuse of the command can lead to severe punishment including removal
of access and O:line.
6.2.12 DELETE
This command will force drop a channel and delete its registration completly.
Syntax: /chanserv DELETE #Channel
WARNING: Misuse of the command can lead to severe punishment including removal
of access and O:line.
6.2.13 SET
This will let a staff member force change a channels services options like ENFORCE or
NOOP.
Syntax: /nickserv SET #channel OPTION ON|OFF
WARNING: Misuse of the command can lead to severe punishment including removal
of access and O:line.
6.3 OperServ
6.3.1 CLONES
This command is to get a more detailed information about an ip or ipmask that has been
found cloning on the network.
Syntax: /operserv CLONES 12.12.12.12
/operserv CLONES john@13.13.13.13
WARNING: Misuse of the command can lead to severe punishment including removal
of access and O:line.
6.3.2 GLOBAL
This command is used usually to send a global message out to everyone on the
network. To use this command, you have to be global operator and above.
Syntax:
/operserv GLOBAL ALL Hi everyone, We are gonna blablabla..
/operserv GLOBAL *.aol.com Welcome to our network AOL users
WARNING: Misuse of the command can lead to severe punishment including removal
of access and O:line.
6.3.3 IDENTIFY
This command will let an oper identify to services after which the oper is granted access
to the restricted oper commands available under nickserv, chanserv, memoserv, operserv
and rootserv.
Syntax:
/operserv IDENTIFY OperservPassword (Identify using current nick)
/operserv IDENTIFY Nickname OperservPassword (Identify using Nickname)
WARNING: Misuse of the command can lead to severe punishment including removal
of access and O:line.
6.3.4 LISTADM
This command will list all IRC Operators that have been added to services access.
Syntax: /operserv LISTADM
WARNING: Misuse of the command can lead to severe punishment including removal
of access and O:line.
6.3.5 SETTINGS
This command will show current services settings like expiry times and max memo
length and limit etc.
Syntax: /operserv SETTINGS
WARNING: Misuse of the command can lead to severe punishment including removal
of access and O:line.
6.3.6 STATS
This command will show current statistics about the network and services nick/chan
registrations etc.
Syntax: /operserv STATS
/operserv STATS ALL
/operserv STATS AKILL
/operserv STATS RESET
WARNING: Misuse of the command can lead to severe punishment including removal
of access and O:line.
6.3.7 UINFO
This command will show what services knows about a certain online user. It will for
example show which nicks and channels the user is currently identified to.
Syntax: /operserv UINFO nickname
WARNING: Misuse of the command can lead to severe punishment including removal
of access and O:line.
6.3.8 UPTIME
This command will show services uptime
Syntax: /operserv UPTIME
WARNING: Misuse of the command can lead to severe punishment including removal
of access and O:line.
6.3.9 VERSION
This command will show services version and information.
Syntax: /operserv VERSION
WARNING: Misuse of the command can lead to severe punishment including removal
of access and O:line.
6.3.10 OPERHELP
This command is used for the IRC Operator side of the services OPERHELP feature in
memoserv and will let IRC Operators list, read and delete queries made from users
through memoserv.
Syntax: /operserv OPERHELP LIST
/operserv OPERHELP READ ID
/operserv OPERHELP DEL ID
NOTE: Deleting a query doesnt remove it from the services logs.
WARNING: Misuse of the command can lead to severe punishment including removal
of access and O:line.
6.3.11 CHANGES
This command will show the recent changes made to services and when the changes
were made.
Syntax: /operserv CHANGES
WARNING: Misuse of the command can lead to severe punishment including removal
of access and O:line.
6.3.12 AKILL
This command is for listing, modifying and retrieving info about the network wide
autokills.
Syntax:
/operserv AKILL LIST *pattern*
/operserv AKILL INFO user@host.com (display info about an akill)
/operserv AKILL TICKET efiu239fu8heiu (display info about an akill)
/operserv AKILL TIME 30m user@host.com ReasonHere (30min timed akill)
/operserv AKILL TIME 6h user@host.com ReasonHere (6hour timed akill)
/operserv AKILL TIME 2d user@host.com ReasonHere (2days timed akill)
/operserv AKILL ADD user@host.com ReasonHere (permanent akill)
/operserv AKILL DEL user@host.com
WARNING: Misuse of the command can lead to severe punishment including removal
of access and O:line.
6.3.13 PASS
This command is for changing your operserv password.
Syntax: /operserv PASS PasswordHere
WARNING: Misuse of the command can lead to severe punishment including removal
of access and O:line.
6.3.14 SEARCH
This command is for searching the services logs to verify what users stories and events.
Below is shown some smart ways to use this command.
NOTE: use pattern for nick/chan names or user@mask or other keywords.
Patterns cant contain spaces.
Syntax:
/operserv SEARCH TODAY ALL *pattern* (all todays logs with *pattern*)
/operserv SEARCH TODAY REG *pattern* (all reg logs with *pattern*)
/operserv SEARCH TODAY FAIL *pattern* (fail idents with *pattern*)
/operserv SEARCH TODAY DROP *pattern* (drop logs with *pattern*)
/operserv SEARCH TODAY OWN *pattern* (ownership logs with *pattern*)
/operserv SEARCH TODAY OS *pattern* (operserv logs with *pattern*)
/operserv SEARCH TODAY RS *pattern* (rootserv logs with *pattern*)
NOTE: To search in logs that was logged before TODAY just change the syntax from
TODAY to HISTORY
Syntax: /operserv SEARCH HISTORY REG *pattern*
(show historical registration logs with *pattern*)
NOTE: If the search gets more than 50 hits you can start reading at log 51 by adding an
index to your search
Syntax: /operserv SEARCH HISTORY REG *pattern* index=50
WARNING: Misuse of the command can lead to severe punishment including removal
of access and O:line.
6.3.15 TRIGGER
This command is for triggering an ip or usermask with a higher or lower allowed clones
value.
Syntax:
/operserv TRIGGER 12.12.12.12 10 ReasonHere
/operserv TRIGGER user@host 10 ReasonHere
/operserv TRIGGER user@ip 10 ReasonHere
/operserv TRIGGER LIST
WARNING: Misuse of the command can lead to severe punishment including removal
of access and O:line.
6.3.16 IGNORE
This command is for listing, modifying and retrieving info about the services ignore list.
Syntax: /operserv IGNORE LIST *pattern*
/operserv IGNORE INFO user@host.com
/operserv IGNORE TICKET efiu239fu8heiu
/operserv IGNORE TIME 30m user@host.com ReasonHere
/operserv IGNORE TIME 6h user@host.com ReasonHere
/operserv IGNORE TIME 2d user@host.com ReasonHere
/operserv IGNORE ADD user@host.com ReasonHere
/operserv IGNORE DEL user@host.com
WARNING: Misuse of the command can lead to severe punishment including removal
of access and O:line.
6.3.17 JUPE
This command is used for adding psuedo servers on the network. A real server will not
be able to link the network if theres currently a juped psuedo server attached to the
network.
Syntax: /operserv JUPE ADD servername.se.eu.avade.net reason
/operserv JUPE DEL servername.se.eu.avade.net
/operserv JUPE LIST
WARNING: Misuse of the command can lead to severe punishment including removal
of access and O:line.
6.3.18 SOP
This command will list or modify the Services Operator list.
Syntax: /operserv SOP ADD nick
/operserv SOP DEL nick
/operserv LIST
WARNING: Misuse of the command can lead to severe punishment including removal
of access and O:line.
6.3.19 SGLINE
This command will list or modify the Services GCOS ban list. This feature is very nice
when dealing with bots that might come from diffrent hosts but has the same
realname/gcos field
NOTE: note the syntax!
Syntax: /operserv SGLINE ADD *gcos*:reason
/operserv SGLINE DEL *gcos*
/operserv SGLINE LIST
WARNING: Misuse of the command can lead to severe punishment including removal
of access and O:line.
6.3.20 SQLINE
This command will list or modify the Services Q:Line list. Nicks or channels matching a
SQLine will not be usable by ordinary users.
NOTE: Its possible to use wildcards such as * or ? where ? will wildcard 1 character.
Syntax: /operserv SQLINE ADD nick reason
/operserv SQLINE ADD nick* reason
/operserv SQLINE ADD #chan reason
/operserv SQLINE ADD #chan* reason
/operserv SQLINE DEL nick
WARNING: Misuse of the command can lead to severe punishment including removal
of access and O:line.
Theory 7. Being an IRC Operator
7.1 Opering in general
IRC Operator or opers are normal users who are given the privileges and certain tasks to
help run and maintain the server/ network they oper on. Being an IRC Operator is not
just about using the /kill command as tempting as it may be It is about not using the /kill.
If you think of it that way, then being an IRC Operator is not for you.
Users will look up to you as a leader or their source of information or help. Never look
down on them. Remember that you were one time at their level. As an IRC Operator, it
is your duty to keep yourself updated with the current issues on the network especially
with services and the ircd functions. Wouldn't it be embarrassing if someone asks you
something and you're not able to answer?
Since you are to enforce Avade's policies, you will have to follow them too. This is
where "Leadership by Example" plays an important role. This means you yourself can't
mass invite, flood attempt hacking or indulge in any illegal activities. Failure to follow
Avade's policies is one of the quickest ways of having your O:line revoked.
IRC Operators have 3 main duties and as follows in the descending order of importance:
1. Maintain the server.
2. Maintain the network the server is linked to.
3. Help users as much as possible.
The third duty is done during the oper's free time. If you're not available or unable to
help someone who needs help, be polite about it and tell them you can't and direct them
to the next source of help. Avoid using phrases like "I am surprised you don't even know
the answer to this simple thing" or "Go read the manual". Not everyone can understand
by just reading documents or helpscreens.
Besides just opering on Avade, there are teams that may require assistance like the
Support & Community, Human Resources and the WebTeam. Currently, Avade has 2
official help channels and they are #Help and #OperHelp. Try as much as possible to
participate in any of these teams. Helpees can also send queries through services
OPERHELP features implemented in memoserv and operserv.
As a staff of the Avade Network, you will be told confidential information and may have
privilege to such info. These should not be told or shared even among friends. They
include anything said on globops/locops oper mailing lists and forums and other means
of communication like MSN or ICQ.
Users trust us to keep the network running smoothly so we should upkeep this trust. Do
not use SAMODE, GETPASS, FREEZE, CLOSE or other demeaning commands unless
you're sure of what you are doing. Remember that services logs such and you will be
held responsible for your actions. Abusing your oper privileges can cause serious
problems for you include removal of your privileges.
7.2 Dealing with problematic users
As mentioned before, opering is not just the /kill command alone. There is more than 1
way to resolve such issues. Always try diplomatic ways like discuss with the user.
Things you should avoid is "I will kill you because I can". First thing you should do is
o study the situation and see what caused it. Review the logs and talk with the user. If
you're sure that the user was being abusive, you should try and warn the user and tell the
consequences.
YES: Flooding services is an abuse. If you flood services again, you will be removed.
NO: I kill people who flood services.
Being rude is not going to get you anywhere. Be firm but polite to get the message
across to them. You will be surprised at how diplomacy works and users will respect
you. Always use/kill as the last resort.
7.3 KILLS/AKILLS/KLINES
One of the tools given to IRC Operators in order to run the network is being able to
remove problematic users. Generally, there are 4 ways of dealing with abusive users.
They are warn, warning kill, autokill and last kline.
As discussed in the previous section, there is more than 1 way of resolving issues.
However, there are times diplomacy fails to work. If repeated warnings do not help, a
KILL would come necessary to show that you mean what you say. Don't warn someone
that you will do something and later you wouldn't. There are users who will test your
patience. Doing this will only make users think you're only making empty threats.
Should the KILL fail to work, then it's time to move on to something advanced. Setting
an AKILL can only be done by SOPs and above. If you're not, you'll have to contact one
with the logs and relevant information. It is not wise to set a wide AKILL which can
affect innocent users.
Gradually, if nothing seems to work, comes the hardest part which is KLINE. Before
you set a KLINE, you might want to talk with your admin/ Net Admin. Another
alternative would be to contact the offender's ISP (Internet Service Provider).
KLINEs are set as a last resort.
NOTE: It is of most importance that your kills, akills and klines are added with an
understandable and to point reason of why the user was thrown out of the network
with the contact info to kline team.
7.4 FORBID/FREEZE/CLOSE
A part from KILL/AKILL/KLINE, services have 3 additional features to deal with
problematic users which affects more of the user's ability to use services. Listed below
are the offences under this category:
1. Mass inviting users to another network/channel/server
2. Nicks/Chans that impersonate IRC Operators/Services/Official Network Chans
3. Botnet/Drone channels
4. Services Abuse
First is always the same which is warning the user. If it is a channel that is being
reported, a masskick serves as a warning not only to the founder/AOP/SOP but also to
the rest of the users as to what can happen if they do not follow the policies.
7.5 If a user reports/threatens to report you
Being an IRC Operator sometimes can be testing your patience as well as limits. This is
why maintaining your cool is important. If a user reports you to your admin/ Net
Administrator, the first thing is not to panic. If you have not done wrong you will have
nothing to fear as your admin/ Net Administrator will contact you regarding the matter.
It is best to save the logs (dated and time stamped) as evidence of the incident which
will help determine the cause and the solution. It is reminded to be rational and avoid
fighting and arguing with the complainant. A meeting will be called and both sides will
be able to speak. Admins and opers will then discuss and choose the right course of
action or if the action taken by that oper was appropriate.
If a user threatens to report you, do not show nervousness or plead with him not to.
Doing so will only mean you are guilty. If a user asks who your admin is, do not hide
this information from him as this can be used against you.
7.6 Teamwork
Teamwork is essential for the benefit of you and the network. There is no "I" in
"TEAM". Work with other server/network staff and/or team members of the team you're
on.
T = Together
E = Each
A = Accomplishes
M = More
Do not share your passwords with anyone!
