The Dextroverse
 


Article Tools
Wiki Links
Wiki (List)

Post Need-To-Know IRC Oper Commands
Hey IRC staff. Many of you have already been sent a sort of preliminary copy of this, but I spoke with youph and he suggested I create an article for this. This is simply a compilation of common IRCop commands that I collected from various resources such as the forums and information other opers have shared with me. Now I'm sharing it with you all, because I find it massively helpful, especially when I don't have to use a command for a while and a situation suddenly occurs while I'm the only active IRCop, which, contingent upon the time you connect to the server, could very easily be the case. This way, you have some tools to rely on, just in case there is some type of abuse on the server. Enjoy!

~Nismo

Helpful website: http://www.vulnscan.org/UnrealIRCd/u...eropercommands

REMEMBER: When akilling, long-term shunning, etc. a user, be sure to put their nick and the reason at the end. For example, for an akill:
/msg operserv akill add +30d *@ip56-109-121-92.ks.ks.cox.net Nismo Harrassment
Also add any bans to the ban log in the IRCops forum.
Here is a link to that thread: http://dextroverse.org/forums/showthread.php?t=21636
Lastly, I know I put some goofy examples for reasons in some of these, but always use your discretion and best judgment when executing a command.
Thanks!

SETTING ADDITIONAL SERVER NOTICES:
If you enable extra server notice modes, this will allow you to see more activity on the server. This can be useful because it allows you to see things like /nick changes anywhere on this server (this includes the absence of a channel at all), and more diagnostic information about whats going on with the IRCd to be displayed in general:

Oper first and type:
/mode +s +cefGknNosSv

Snomasks are server notice masks. These are a special type of usermode that controls which server notices you will receive and is mostly used by opers:

It can be set by: /mode yournick +s SNOMASK,
I.E. /mode Nismo +s +cF
To remove certain snomasks, use something like: /mode Nismo +s -c
Or you can remove all snomasks by simply doing: /mode Nismo -s

The current available snomasks are:
c - local connects
F - far connects (except from U-lined servers)
f - flood notices
k - kill notices (*)
e - 'eyes' notices
j - 'junk' notices
v - vhost notices
G - gline/shun notices
n - local nick change notices
N - remote nick change notices
q - deny nick (Q:line) rejection notices
s - receives server notices (*)
S - receives spamfilter notices
o - receives oper-up notices
[*: this snomask is also allowed to non-ircops]

I find these to be incredibly helpful because I like being able to see the server action.

WHOIS
In order to get information for many of the following commands, you will need to use the /whois command. It will give you a great deal of information and anything you'll need for a command.
I.E. /whois Nismo
This is what appears if you /whois me:
Nismo is [email protected] navy.mil ENTANGLEMENT ([email protected] hidden with /sethost command)

Nismo is using modes +owghrsxWt +kcfveGnNqso (these are the server notice modes referred to above)

Nismo is connecting from *@ip56-109-121-92.ks.ks.cox.net 56.109.121.92 (here is my host, which ends with cox.net and my IP is the number following afterward -- this could appear differently in other users' /whois information)

Nismo is a registered nick (this just states that my nick is registered with NickServ)

Nismo on &#dextroverse &#opers (these are the channels I am currently on and what my status is on each of them)

Nismo using irc.dextroverse.org Dextroverse IRC Server (I am connected to the DV server)

Nismo is an IRC Operator (this is to indicate to users that I have an o:line)

Nismo is available for help. (this appears when I am not away so users know they can ask me questions or express concerns -- if I am away, it will provide a reason for why I am gone)

Nismo is an IRKEN INVADER (this is just champion silliness)

Nismo idle 4, signed on Tue Apr 27 19:47:23 2010 (this tells you when I signed on and how long I've been idle [in seconds], which is helpful in case I have forgotten to de-op myself before going away from my keyboard. Users with questions now know if I've been gone for a while, and other opers with questions can identify the same thing and de-op me to avoid confusion)

WHEN YOU THINK AN IP IS SOMEONE EVADING A BAN/USING A PROXY, ETC.:
/msg nickserv info nick
I.E. /msg nickserv info Nismo
You can also use /whowas if the user is no longer on the server (same syntax as /whois)

KICK FROM CHANNEL
/kick #channel nick reason
Works similarly to a /kill, only the user doesn’t have to reconnect to the server, just rejoin the channel.
I.E. /kick #dextroverse Nismo you’re acting a fool

KILL FROM SERVER
/kill nick reason
This sounds worse than it is; it basically just forcibly removes someone from the server. They can reconnect at any time, though.
I.E. /kill Nismo You’re still acting a fool

SHUN
/quote shun nick +X reason
(X being a positive integer of time, which includes seconds [s], minutes [m], hours [h], days [d], or a combination of one or all -- these integers of time apply to all commands that require you to input time constraints).
I.E. /quote shun Nismo +5d2m Nismo Overly offensive language
You have just shunned me for 5 days and 2 minutes. While it is possible to set a shun to +0d, which is a Permanent shun, this is never recommended.

AKILL (use for banning HOSTS)
I.E. /msg operserv akill add +60d *@ip56-109-121-92.ks.ks.cox.net Nismo Posting NWS in main
You have just akilled me for 60 days. The maximum number of days you can set an akill for is 400.

SZLINE (use to ban IP only)
I.E. /msg operserv szline add +30d 56.109.121.92 Nismo Evading prior ban
You have just szlined me for 30 days. There is no limit on how many days an szline ban can be made for.

HOSTMASK is the information you can find in the /whois on the user you're banning. In this case its *@ip56-109-121-92.ks.ks.cox.net.
If you ever want to remove my akill, it's simple. Just use this command:
/msg operserv akill del

In this case:
/msg operserv akill del *@ip56-109-121-92.ks.ks.cox.net
and it's removed.

The same concept is applied to the szline command. To remove an szline, type:
/msg operserv szline del 56.109.121.92

BAN AN ENTIRE IP RANGE (very helpful in the case of abuse from proxies the use the same basic IP)
You can also ban an entire IP range if you discover you have someone evading, and all their proxies have the same basic IP, except the last octet will bbe different, and can be anywhere from 1 to 255 in most cases.
/msg operserv szline add +180d 56.109.121.* Nismo stop evading and get a life
Basically, you're adding the wildcard (the asterix *) to the end of the IP address, after the last decimal point, in place of the last octet, disabling the user from utilising any of the IP addresses in that range.

SET CHANNEL MODES
/mode #channel +mode (nick, hostmask, etc)
I.E. /mode #dextroverse +q nismo (+q only Q:ilined servers can kick you)

COMMUNICATIONS
/msg operserv global
Talks to all users, through Operserv, but not in the main channel.
I.E. /msg operserv global Hi, everyone, I'm an oper and I think I'm special.
/notice nick
Acts similar to OS global, only this is between only you and the person you /notice and is not seen by anyone in the channels you're in.
I.E. /notice Nismo You think you're special because you're an operator.
/msg nick
Sends a message to the specified user in a Private Message.
/msg Nismo You're a really shitty operator; you'd make an even worse admin.

DOS/FLOOD ATTACK:
If #dextroverse is under attack, the first thing an operator should do is:

/mode #dextroverse +i

What that does is prevent anyone from joining the channel without being invited (/invite nick).

Next, locate the user(s) flooding the channel and quickly kick them. At this point, #dextroverse should be safe and you may begin to /whois the nicks or otherwise determine their *real* IP addresses and quickly akill them followed by a /kill for each user.

If the attack is a connect flood, meaning there are tons of connects from dummy (meaning silly nicks like GDSJSKASK, probably proxies) determine their IP/hosts and akill/kill them.

Remember to notify all operators/admins as soon as you figure out what's going on. If need be, call the operators/admins on the phone and tell them to get online ASAP for assistance.

Remember: TEAMWORK. Don't try and be superoper and do it all alone as you may become overwhelmed.

*DOCUMENTATION FOR UNREAL: http://www.vulnscan.org/UnrealIRCd/unreal32docs.html
*SPECIFICALLY: http://www.vulnscan.org/UnrealIrcd/u...ture_antiflood

*FOR EXAMPLES OF OTHER ATTACKS [ie botnet]:
http://www.dextroverse.org/forums/in...&f=57&t=21033&

FOR A LIST OF OPER COMMANDS, TYPE
/msg operserv help commands and you will get this list:

[14:51] -> *operserv* help commands
[14:51] -OperServ- OperServ commands:
[14:51] -OperServ- GLOBAL Send a message to all users
[14:51] -OperServ- STATS Show status of Services and network
[14:51] -OperServ- SERVERMAP Show map of servers on network
[14:51] -OperServ- OPER LIST List all Services operators
[14:51] -OperServ- ADMIN LIST List all Services admins
[14:51] -OperServ- Commands available to Services operators and admins only:
[14:51] -OperServ- MODE Change a channel's modes
[14:51] -OperServ- KICK Kick a user from a channel
[14:51] -OperServ- CLEARMODES Removes certain modes from a channel
[14:51] -OperServ- CLEARCHAN Removes all users from a channel (masskick)
[14:51] -OperServ- KILLCLONES Kill all users that have a certain host
[14:51] -OperServ- AKILL Manipulate the autokill list
[14:51] -OperServ- AKILLCHAN Autokill all users in a channel
[14:51] -OperServ- SGLINE Manipulate the SGLINE list
[14:51] -OperServ- SQLINE Manipulate the SQLINE list
[14:51] -OperServ- SZLINE Manipulate the SZLINE list
[14:51] -OperServ- SESSION View the list of host sessions
[14:51] -OperServ- EXCEPTION Modify the session-limit exception list
[14:51] -OperServ- LOGONNEWS Define messages to be shown to users at logon
[14:51] -OperServ- OPERNEWS Define messages to be shown to users who oper
[14:51] -OperServ- Commands available to Services admins only:
[14:51] -OperServ- OPER Modify the Services operator list
[14:51] -OperServ- JUPE "Jupiter" a server
[14:51] -OperServ- SET Set various global Services options
[14:51] -OperServ- UPDATE Force the Services databases to be
[14:51] -OperServ- updated on disk immediately
[14:51] -OperServ- SHUTDOWN Save databases and stop Services
[14:51] -OperServ- QUIT Terminate Services without saving databases
[14:51] -OperServ- RESTART Save databases and restart Services
[14:51] -OperServ- REHASH Re-read configuration files
[14:51] -OperServ- SU Obtain Services super-user privileges
[14:51] -OperServ- Commands available to the Services super-user only:
[14:51] -OperServ- ADMIN Modify the Services admin list
[14:51] -OperServ- RAW Send a raw string to the IRC server

FOR A LIST OF CHANSERV COMMANDS, TYPE
/msg chanserv help commands and you will get this list:

[05:58] -ChanServ- The following commands can be used with ChanServ:
[05:58] -ChanServ-
[05:58] -ChanServ- REGISTER Register a channel
[05:58] -ChanServ- IDENTIFY Identify yourself with your password
[05:58] -ChanServ- DROP Cancel the registration of a channel
[05:58] -ChanServ- SET Set channel options and information
[05:58] -ChanServ- UNSET Clear channel information
[05:58] -ChanServ- INFO Show channel options and information
[05:58] -ChanServ- ACCESS Maintain the overall channel access list
[05:58] -ChanServ- LEVELS Fine-tune channel privilege levels
[05:58] -ChanServ- OP Give a user chanop status (+o)
[05:58] -ChanServ- DEOP Remove chanop status (+o)
[05:58] -ChanServ- VOICE Give a user voice status (+v)
[05:58] -ChanServ- DEVOICE Remove voice status (+v)
[05:58] -ChanServ- HALFOP Give a user halfop status (+h)
[05:58] -ChanServ- DEHALFOP Remove halfop status (+h)
[05:58] -ChanServ- PROTECT Give a user protected status (+a)
[05:58] -ChanServ- DEPROTECT Remove protected status (+a)
[05:58] -ChanServ- INVITE Invite yourself to a channel
[05:58] -ChanServ- UNBAN Unban yourself from a channel
[05:58] -ChanServ- KICK Kick a user from a channel
[05:58] -ChanServ- TOPIC Change a channel's topic
[05:58] -ChanServ- CLEAR Clear channel modes or mass-kick users
[05:58] -ChanServ- STATUS Return a user's access level on a channel
[05:58] -ChanServ- LIST List registered channels
[05:58] -ChanServ- AKICK Maintain the AutoKick list
[05:58] -ChanServ-
[05:58] -ChanServ- The following commands are available to Services admins:
[05:58] -ChanServ-
[05:58] -ChanServ- DROPCHAN Drop any channel
[05:58] -ChanServ- FORBID Prevent a channel from being registered/used
[05:58] -ChanServ- SUSPEND Prevent a registered channel from being used
[05:58] -ChanServ- UNSUSPEND Cancel a channel suspension
[05:58] -ChanServ-
[05:58] -ChanServ- Services admins can also view the access, autokick, and
[05:58] -ChanServ- level setting lists or use the STATUS command for any
[05:58] -ChanServ- channel.

SIMILARLY, FOR A LIST OF NICKSERV COMMANDS, TYPE
/msg chanserv help commands and you will get this list:

[06:05] -NickServ- The following commands can be used with NickServ:
[06:05] -NickServ-
[06:05] -NickServ- REGISTER Register a nickname
[06:05] -NickServ- IDENTIFY Identify yourself with your password
[06:05] -NickServ- DROP Cancel the registration of a nickname
[06:05] -NickServ- LINK Link another nickname to your own
[06:05] -NickServ- UNLINK Cancel a linked nickname
[06:05] -NickServ- LISTLINKS List all nicknames you have linked
[06:05] -NickServ- ACCESS Modify the list of authorized addresses
[06:05] -NickServ- AJOIN Modify your autojoin list
[06:05] -NickServ- SET Set options, including kill protection
[06:05] -NickServ- UNSET Clear nickname information
[06:05] -NickServ- RECOVER Kill another user who has taken your nickname
[06:05] -NickServ- RELEASE Regain custody of your nickname after RECOVER
[06:05] -NickServ- GHOST Disconnect a "ghost" session
[06:05] -NickServ- INFO Display information on a nickname
[06:05] -NickServ- LISTCHANS List all channels you own
[06:05] -NickServ- STATUS Check whether a given nickname is identified
[06:05] -NickServ-
[06:05] -NickServ- The following commands are available to Services admins:
[06:05] -NickServ-
[06:05] -NickServ- DROPNICK Drop any nickname
[06:05] -NickServ- FORBID Prevent a nickname from being used/registered
[06:05] -NickServ- SUSPEND Prevent a nickname from being identified for
[06:05] -NickServ- UNSUSPEND Cancel a nickname suspension
[06:05] -NickServ- LIST List all nicknames matching a given mask
[06:05] -NickServ- LISTEMAIL List nicknames by E-mail address
[06:05] -NickServ-
[06:05] -NickServ- Services admins can also use the following commands on any
[06:05] -NickServ- nickname without needing to identify for it:
[06:05] -NickServ-
[06:05] -NickServ- SET, ACCESS LIST, INFO ALL
[06:05] -NickServ-
[06:05] -NickServ- See the help for each command for specific details.


Remember that if you have any questions, feel free to ask anytime. This is intended to help everyone become more familiar with some of the commands an IRCop uses regularly. Build up your confidence. Even if you make a mistake, don't worry. Let somebody know (if someone is not already there) and it can be fixed. Everyone is encouraged to learn these commands and develop a skill-set because you never know when you'll be the only IRCop online. Also, suggestions are welcome. Please let me know if there is a mistake I have not caught or if you have a suggestion for something to add so I can decide whether to edit the Wiki. Good luck!!!

<#

PS: Thanks to the staff for letting me use the resources you have not only posted here but have shared with me individually. This is obviously as much yours as it is mine.


Created by House, 04-28-2010 at 02:21 AM
Last edited by House, 05-13-2010 at 10:11 AM
Last comment by House on 04-28-2010 at 07:25 AM
1 Comments, 902 Views
(protected)

Posting Rules
You may not create new articles
You may not edit articles
You may not protect articles

You may not post comments
You may not post attachments
You may not edit your comments

BB code is On
Smilies are On
[IMG] code is On
HTML code is On


Powered by vBulletin® Version 3.8.4
Copyright ©2000 - 2012, Jelsoft Enterprises Ltd.
vBulletin Skin developed by: vBStyles.com

"Wiki" powered by VaultWiki v2.5.0.
Copyright © 2008 - 2012, Cracked Egg Studios.