#zt Advanced Class March 23 2000

Session Start: Fri Mar 24 10:36:20 2000
*** Now talking in #class
*** [#class] Topic is 'Intermediate Class March 23 7:30PM EST (00-03-28 00:30 GMT) (http://www.user-com.undernet.org/class/)'
*** [#class] Topic by X on Fri Mar 24 13:39:11 2000
*** Joins: Cyndi (Smiles@ras1-27.icom.ca)

Good Evening.  This instructional script is brought to you by the Undernet User Committee.  Please send comments, suggestions or ideas to class@undernet.org. Our Webpage is http://www.user-com.undernet.org/class/ - We'd like to welcome you all to the Undernet Advanced User's School. (INT1)

This class covers the more advanced topics of IRC. It is recommended that you first attend the Undernet New User School before attending this class. The New User's School is held here every other Tuesday at 8:30PM Eastern (01:30AM GMT), alternating every week with this class. (INT2)

If after the class you find you need additional help with IRC, feel free to ask in one of the help channels we mention at the end of class. (INT3)

Now for the rules of the class. These are to your benefit to prevent disruption. For most of you who have attended the New User's School, this should only be a review. (R1)

The teaching staff is divided up alphabetically.  Each tutor will answer questions for the nickname group they are assigned to: For example, A-GTutor handles nicks starting with A through G, and so on.  If your nickname starts with anything else, don't sweat it. Just use the tutor with "A" included in their nickname group. (R2)

Please ask any questions you have about IRC or this class to your tutor via /msg.  Please do not /notice or /DCC me, your tutor, or the channel.  (R3)

The channel is also set to +m.  This means only the teacher and tutors will be able to talk. This is set to prevent disruption in the class. (R4)

To get rid of interruptions of people joining the channel, we also set the channel to +i.  This means you need to be invited by your tutor to join back if you leave. (R5)

If you leave or disconnect, you can /msg your tutor to request an invite to get back in the channel.  Please do not leave or ask for invites if it is not necessary.  Make a note of your tutor's nickname now. (R6)

Nickname changes are prohibited during class. While class is in session, you will not be permitted to change your nickname - That's why we put a ban on *!*@*. (R7)

I'd ask that you please do not message me.  I have the job of keeping the lesson flowing.  Ask all questions to your tutor. (R8)

If you plan to stay for the class, you may wish to log the session.. please turn on your logging now. If you need help with this, please ask your tutor. (R9)

To get rid of disruptions of people leaving or quitting, you may wish to put these messages in your status window instead of the channel window. In mIRC, go to options, and uncheck "Joins/Parts in channel", and also uncheck "Quits in channel". (R10)

The numbers and letters you see at the end of these lines are reference marks.  They help me and the tutors to find where they are during the class.  You do not need to pay attention to these. (R11)

During the course of a class, a certain committee or channel may be mentioned that you want to go to. At the end of class there will be a section for URL's and channels where you can go for programs/channels/people or for more information. (R12)



SESSION A - FLOOD PROTECTION: This session explains the different types of floods and how to combat them. (A1)

Floods are found everywhere you go on IRC. Even though they can disconnect and annoy you, there are very simple ways to combat them. (A2)

There are many different kinds of floods on IRC. Here are some of the more common types. Included after each one is how to combat or prevent that kind. (A3)

CHANNEL TEXT FLOODS - Multiple lines of text sent to a channel - usually in random letters. (A4)

CTCP FLOODS - The flooder sends a ctcp command to you many times, causing your client to respond just as many times, and ending up in a disconnection. (A5)

To combat CTCP and channel text floods, set up an alias key to /silence *!*@*, which will ignore everyone until you take off the command. To take off the command, type /silence -*!*@* (note the -). For information on setting up aliases, consult your clients documentation. (A6)

FLASH FLOODS - This is a more rare type of flood. This flood happens only to UNIX users. The flooder sends a command to the server causing all other UNIX users to have their screen codes reset so the screen becomes unreadable.  (A7)

For all UNIX users, simply type "mesg n" (no quotations) at the shell prompt BEFORE using IRC. This command will get rid of the problem. (A8)

DCC FLOODS - A user attempts to hold multiple DCC sessions with you and sends random text to the chat window. (A9)

The best thing to do to combat this type of flood is to not accept any DCC chats from people that you don't know. Otherwise if the DCC is a DCC send, the best thing to do is to close your client, open it again, and set it to auto-ignore DCC Sends until you're sure the flooder stopped. (A10)

ICMP FLOODS - This happens when a user sends multiple packets of information over and over again to your internet dialer, causing the dialing program to become busy. The dialer doesn't have time to respond to the IRC server you're on, so the server thinks you've left. This ends up in a disconnection. (A11)

There is no fix for ICMPs in Windows 95, so the best thing to use is a port sniffer. This program will detect when you're getting ICMPed, and will automatically log the IP of the flooder. Also ask your ISP about firewalls. When you're behind a firewall, you cannot be ICMPed. There is however a patch for all other platforms. (A12)

Parts: xcvxcv (~vcxvxv@ts1-46.f1105.quebectel.com)
[11:24] <Cyndi> LOCAL PORT FLOODS - mIRC has a bug in it that lets flooders attack your printer and modem ports. There is an easy fix for this. (A13)

There is a simple fix for mIRC users. Just type /ignore -p <option>. Where option is, type these commands in separately: com1*!*@*, com2*!*@*, com3*!*@*, com4*!*@*, prn!*@*, and lpt!*@*. Be sure to type them SEPARATELY. E.G. /ignore -p com1*!*@*, then /ignore -p com2*!*@*, and so on for all of them. (A14)

FORMAT FLOODS - Because of the recent new color feature in mIRC and other clients, format floods are becoming more common. Format floods are "pictures" drawn on a client using colors. As cute as it sounds, they can flood users off - both accidentally and intentionally. (A15)

Those are all the types, fixes and commands you need to combat floods. Remember to NEVER retaliate against a flooder, it only makes the situation worse. If a flooder persists to flood you, try contacting an IRCop with the nickname and/or the user@host of the flooder by typing /who 0 o or /who -oper for UNIX. (A16)

For a more in depth document about flooding and how combat it, check NudeDude's NoFlood document available at the documents website at http://www.undernet.org/documents/ (A17)

We'll pause briefly in case you have any questions that you need to ask your tutor. You'll have a chance to ask your tutor questions at the end of each session. (AP)



SESSION B - DoS attacks - Explanation and information on protection against Denial of Service attacks. (B1)

Denial of Service, or Nuke is an attack against computers connected over the internet, especially on IRC. These attacks are illegal in the U.S and many other countries. (B2)

There are many DoS attacks other than Nukes - ssping, winnuke, land, click, smurf, teardrop, and ICMP are some of them. Please note that "nuke" is usually used to refer to any kind of DoS attack, but there is an attack called winnuke. (B3)

Ssping causes your computer to lock up, usually requiring a reboot. After rebooting, the computer should run as normal. There is currently a patch for Windows 95 and NT, and a few other platforms. (B4)

WinNuke only affects Windows systems, and causes a device driver error, resulting in a loss of connection to the internet. This may also require a reboot. There is a patch for this bug. (B5)

Land affects several operating systems including Windows, and causes a freeze and then a crash of the computer. Luckily, there is a patch. (B6)

Click affects just about everybody, and all it causes is a disconnection from IRC. The quit messages are usually "Connection reset by peer," "Connection refused," "Operation timed out," and "Host unreachable." There are no patches to this bug. (B7)

Smurf affects a whole internet provider or IRC server, and everybody connected gets kicked off the server or provider. The attack can last hours, even days. There is no fix to defend yourself. (B8)

Teardrop affects Windows and Linux users, and causes an immediate crash or reboot. There are fixes for most operating systems. (B9)

ICMP is Internet Control Message Protocol, and is very common. ICMP attacks affect anyone with a modem connection, and causes all internet applications to run very slow, and eventually it will disconnect you from your ISP. There are no current patches, except to get a Firewall from your ISP to block ICMP attacks. (B10)

Bonk.c causes attack causes a crash of your dialing program, and the BSoD (Blue Screen of Death) which i'm sure we've all come across. After the screen your net connection will still be active, but most of your programs will be frozen. You must reboot your computer before you can go on. Related to bonk is another new attack called Newtear, with the same results as bonk. There is a fix for all users. (B11)

SMB (Server Message Block) is a more recent type of attack, and it affects only Windows NT4 users. It can either cause the system to hang or to restart. There is currently a patch for users. (B12)

DoS attacks are very serious. In some cases, a fix is available, and it is strongly reccommended you get the patch. At the end of class URL's will be given for the patches. As with floods, the last thing to do is retaliate. Remember, when you're getting attacked, the first thing you want to know is the IP address so you can report the abuser. (B13)

There is currently a sort of virus going around IRC, called the script.ini backdoor. A user with an infected mIRC script.ini file unknowingly sends a backdoored copy of script.ini to all users entering a channel. People who accept the DCC have their good script.ini replaced with the infected one, causing many things to go wrong. (B14)

The next time they launch mIRC, the infected file is set up. The file will send all commands you type to a secret channel where infectors are. Infectors look for any passwords that are sent to X/W so they can take over those channels using user's passwords. The file is also sent to everyone who enters any channels you are on, causing the infected file to spread like a virus. (B15)

The most important thing to remember is to NEVER accept a DCC from someone you don't know, especially if they're trying to send script.ini. And remember most people who send infected script.ini's do it unknowingly. Also remember to never have auto-accept DCC's on. (B16)

For current DoS patch files, check out http://mirc.stealth.net/nuke/. For more information, take a look at http://www.irchelp.org/irchelp/nuke. For complete protection try the Conseal Firewall available at http://www.signal9.com/firewall. (B17)

We'll pause briefly in case you have any questions that you need to ask your tutor. (BP)

1.Barbie's measurements (if she were life-size): 39-23-33 

2.Coca-cola was originally green and much more addictive.

3.Every day more money is printed for Monopoly than for the US Treasury 

5.The Hawaiian alphabet has 12 letters 




SESSION C - ABUSE AND TAKEOVERS: How to prevent and report abuse and channel takeovers. (C1)

If you install all of the patches and take all of the precautions in section A and B, you are still likely to be a victim of a flood or a DoS attack. Knowing where to report them is the next step. (C2)

The most important thing you can have is a log. Try and have the log timestamped, so we know the exact time. Also try to cut out all irrelevant lines in the log. Besides the log, it is requested that you have the attacker's nickname and user@host. (C3)

Takeovers happen just as much as abuse. Takeovers are when a person comes into a channel and tries to gain ops. Often the abuser will deop and kick/ban the other ops. (C4)

Takeovers can occur by use of a netsplit, when an abuser goes to a split server, gains ops, and then deops the ops on the other end of the split. Floodbots can also cause a takeover, when multiple bots are set up to flood everyone in a channel. Finally, the Script.ini backdoor, where X/W passwords are obtained and used to gain ops. (C5)

If your channel has been taken over, you can go to #zt. Calmly report the incident to the helpers there. (C6)

Many users start a channel one day, and come back the next day to see that other people are ops in it. This is certainly not considered abuse because the channel is not registered, and does not belong to any one person. (C7)

Users gaining ops by changing their user@hosts and pretending to be an op is NOT considered a takeover, but bad channel management. Many IRCops will not aid channels when this occurs. (C8)

Remember that the most important thing to prevent DoS attacks is to have all of the patches, rather than to rely on #zt. (C9)

We'll pause briefly in case you have ay questions that you need to ask your tutor. (CP)

10.Men get hiccups more often than women 

11.Men can read smaller print than women: women can hear better 

14.City with the most Rolls Royces per capita: Hong Kong 

47.Only bird that can fly backwards: Hummingbird 





SESSION D - SCRIPTS AND BOTS - Explanation of scripts and online "robots" (D1)

ots are clients with automated responses to certain commands. These responses can be coded into the client and run on IRC to serve some sort of purpose. (D2)

There are many different kinds of bots - Bar bots, fileserving (f-serve) bots, even casino bots. Each bot is coded to have a specific purpose on IRC. Note - For channel management, maintainance of an oplist and banlist, and to utilize other features that bots can offer, it's best to use CService's X and W. For more info, join #cservice. (D3)

Warbots are bots that are programmed to take over channels by use of flooding and trying to create a netsplit. Warbots are illegal on the Undernet and will get your site k-lined, if not g-lined, so it's best NOT to run this type of bot. (D4)

Unlike scripts, bots are run on a separate client then you're using. For example, you would have a second copy of mIRC on your computer. (D5)

A bot works by using a script, comprised of many "on" commands. For example, "on join * /whois $1" would tell you who a person is when they join a channel. (D6)

An alternative way for running a bot is to obtain an already programmed bot. All you need to do is download the scripts and load it into your client. These bots can be obtained from many popular web sites, and on most bot related channels. (D7)

The best way for a beginner to write a bot is to use the scripting language of their client, such as mIRC, pIRCH, ircle, or ircII. More advanced scripters usually use Perl, C, Tcl, etc. To learn how to script in your own client, ask in a bot channel, look on a bot website, or consult your clients documentation. (D8)

A good resource for bots is the Undernet Documents Committee's BotDoc. This document has an FAQ and has many resources for creating your own bot, or getting one off of the web. This document can be found at the Documents website located at http://www.user-com.undernet.org/documents/ (D9)

Scripts are also clients with automated responses to certain commands, in most cases scripts usually run on the same client as you use. (D10)

Scripts are sometimes used to run bots. In bots, scripts are the files that actually have the "on" commands. Scripts tell the client what to do when certain cases come about. (D11)

Other times scripts are used for fun. Fun scripts include automatic greetings when a client joins a channel, different responses to different actions, or to run f-serves or other services. (D12)

For example, you can go to your Remotes in mIRC and type an "on join" line so that your client automatically sends a greeting to every other client joining the channel(s) you're on. (D13)

For more information on creating scripts specifically designed for your client, refer to your client's help files, try #bot or #bots, or join a channel specifically for your client (#mIRC, #pirch, etc.). (D14)

Some useful websites for bots are http://www.bots.org, http://www.mircx.com or http://www.mircusa.com/ and the Undernet BotDoc mentioned above. (D15)

We'll pause briefly in case you have any questions that you need to ask your tutor. (DP)

48.Only continent without reptiles or snakes: Antarctica 

49.Only animal besides human that can get sunburn: Pig 

51.An eagle can kill a young deer and fly away with it 

52.In the Caribbean there are oysters that can climb trees 

53.Polar bears are left-handed 




SESSION E - ADVANCED COMMANDS: A listing of commands to know. (E1)

LUSERS - Options: none. Syntax: /lusers. Use this command to get network information and status. (E2)

WALLCHOPS - Options: none. Syntax: /wallchops <#channel> <message>. If you are an op and would like to send a private message ONLY to the other ops on the channel, use this command. (E3)

WHOWAS - Options: none. Syntax: /whowas <nickname>. Use this command to see if someone was on IRC recently. Useful if you're being flooded and don't know the address of the attacker. (E4)

CTCP - Options: Clientinfo, ping, time, userinfo, version. Syntax: /ctcp <nick> <option>. CTCP (Client To Client Protocol) is used in many different ways, to check lag, to see a persons client version, etc. To see all available ctcp commands use the clientinfo option. (E5)

USERHOST - Options: none. Syntax: /userhost <nickname>. Finds the user@host for the specified nickname. (E6)

USERIP - Options: none. Syntax: /userip <nickname>. Similar to Userhost, but this command finds the IP address for the specified nickname. (E7)

SILENCE - Options: none.  Syntax: /silence <nickname or user@host>. This command works like ignore, except that it's used to stop CTCP floods. (E8)

USERMODES - Options: i, s, w, d. Syntax: /mode <your nickname> <+ or - (option)>. Use this command to set modes on yourself. Option i makes you invisible, s makes you receive server notices, w makes you receive wallops, and d makes you deaf to all channel conversation. Example - /mode +i. Note - You can use either + or - before the option to choose setting. (E9)

MAP - Options: none. Syntax: /map. Use Map to get information on the current network structure, or routing. (E10)

LINKS - Options: none. Syntax: /links. This is the same command as map, except links displays the structure in a different format. On some networks other than the Undernet, the map command doesn't work. Use this command instead. (E11)

STATS - Options: c, g, H, i, k, l, m, o, u, y. Syntax: /stats <option> (server). Stats lists various information about the server, from ban lists to who is allowed on the server, and various other technical lists. (E12)

Option c returns a list of servers which your server may connect to, g shows the network-wide banlist, H shows servers that are allowed to act as hubs, i lists the hosts that are allowed to connect as clients, k shows the server banlist, and l shows port connections. (E13)

Option m gives commands supported by the server, o shows server operators, u is servers allowed to act as services, ie. X or W, and finally y shows lines from the server configuration file. (E14)

TRACE - Options: none. Syntax: /trace <nickname>. Use Trace to look at the path, in servers, between you and another nickname. (E15)

DNS - Options: none. Syntax: /dns <nickname> or <address>. The DNS command is used to find someone's resolved address, or unresolved DNS number. Useful for finding people with unresolved hostnames. (E16)

For all of these commands, when using them, omit the parentheses. For more advanced commands consult your client's help files. Since each client is different, giving more advanced commands would be confusing. (E17)

For more help with any IRC command, try reading the IRC Command Cosmos at http://www.irchelp.org/irchelp/misc/ccosmos.html. (E18)

We'll pause briefly in case you have any questions that you need to ask your tutor. (EP)

54.Intelligent people have more zinc and copper in their hair 

56.The world's youngest parents were 8 and 9 and lived 

57.The youngest pope was 11 years old 

61.Your nose and ears never stop growing 




SESSION F - TROJANS: An explanation on trojans and their fixes. (F1)

Recently there has been an outbreak of Trojan's being sent to unsuspecting users. (F2)  

These Trojan's are passed around in disguise as games, enhancements to an IRC client, warez  with any extensions such as .exe, .jpg, .gif, .ini etc. (F3)

The result of accepting a file send from anyone could be the compromise of your computer to the writer/owner of the Trojans. (F4) 

What does this compromise mean? Well it ranges from allowing access to your computer when you are online, permitting the Trojan writer/owner to get your ISP, e-mail address, passwords, any financial account information that might be on your machine. (F5)

This allows the Trojan writer/owner to use YOUR machine for Denial Of Service attacks, which for example in the United State of America is a felony. (F6)

The only way this problem can be minimized is by YOU the user, NOT accepting ANY file from anyone, for any reason. (F7)

YOU are protecting yourself when you decline a file send from someone, should they ask why, tell them why!!!!  You shouldn't be ashamed to tell someone that you don't accept file sends. (F8)  

Virus scanners may or may not detect a Trojan in a received file.  There are at least two channels dedicated to the eradication of particular Trojans, #backorifice and #dmsetup. (F9)

Users may also try to say they are sending you a 'fix' for these Trojans, they may also be the Trojans itself so do not accept these either. (F10)

To download a cleaner that will check for and clean 150 Trojans go to http://www.dynamsol.com/puppet/ and to download a BO eliminator go to http://www.bardon.com which will fix active BO and help stop from being infected again. (F11)

It is recommended that you visit #backorifice first to get the proper information. (F12)

To detect if you may be infected: (F13) 

#1 Go to your start button then to run box and type command.com and hit enter (F14)

#2 that will bring up a dos window at which point you type: netstat -a -n (F15)

#3 If you see anything that looks like this: UDP 0.0.0.0:xxxxx ( the x's can be any digits, it's the 0's that are important ) you COULD be infected, but don't panic. (F16)

#4 Close down all your internet programs, icq, web browsers, email programs, real audio, etc, then do netstat -a -n again. (F17)

#5 If the UDP 0.0.0.0:xxxxx connection is gone, you do NOT have Back Orifice.  If it's still there you may be infected, and need to join #BackOrifice and ask them to check you out. (F18)

We'll pause briefly in case you have any questions that you need to ask your tutor. (FP)

Research indicates that mosquitoes are attracted to people who have recently eaten bananas

The first known contraceptive was crocodile dung, used by Egyptians in 2000 B.C

Donald Duck comics were banned from Finland because he doesn't wear pants. 

Your right lung takes in more air than your left one does




SESSION G - SNOMASKS: An explanation of what Server Notice Masks are, and how to use them. (G1)
Server Notice Masks, or snomasks, is a feature not widely known by IRC users. This feature enables you to listen to notices, messages, and actions that the server you're on performs. (G2)
In other words, you can set a snomask that will let you know when an IRC operator sets a gline, when there is a netsplit, a nick collision, or even a kill by an IRCop. (G3)

The syntax for the command is /mode <your nickname> +s <value>. Where value is, you enter a number for the type of message you want to recieve. To stop recieving these messages, simply type /mode <your nickname> -s. Note the +s has changed to -s. (G4)

Here is the listings of the different values (numbers), and what they stand for. A copy of the listings is available in the snomask document at the Document Committee's website, located at http://www.undernet.org/documents/. (G5)

1  -  Displays unsorted old messages. 2  -  Server kills (nick collisions). 4  -  IRCop kills. 8  -  Desyncs. 16  -  Temporary desnycs. 32  -  Unauthorized connections. 64  -  TCP or socket errors. 128  -  Too many connections. (G6)

256  -  Uworld actions on channels. 512  -  IRCop Glines. 1024  -  Net join/break, etc. 2048  -  IP mismatches. 4096  -  Host throttle add/remove notices. 8192  -  Old oper-only messages. 16348  -  Client connect/exit notices (not recommended). (G7)

We'll pause briefly in case you have any questions that you need to ask your tutor. (GP)

Bubble gum contains rubber.

Only 55% of all Americans know that the sun is a star. 

The world population of chickens is about equal to the number of people. 

Some toothpastes contain antifreeze. 



SESSION H - UNDERNET ADMINISTRATION: How the Undernet network works. (H1)

The Undernet may seem very simple to the common user, but behind the scenes there are many people hard at work for the users. Many people devote their time to performing many necessary tasks for maintaining the Undernet. (H2)

The Undernet is comprised of many different committees and subcommittees. Each committee tries to work with one another to create a better network and to maintain network stability. (H3)

There are a total of five committees, and five subcommittees. (G4)

Channel Service Committee - Provides an easy method for registering channels in order to maintain channel stability, to prevent takeovers, and to manage a banlist and userlist. CService has two subcommittees, OpSchool and OpMasters. (H5)

The CService home page is located at http://cservice.undernet.org. CService's main e-mail address is cservice@undernet.org (H5a)

Coder Committee - Concentrates on the continued development of the IRC protocol with the goal of making the Undernet a more efficient chat network. (H6)

The Coder Committee home page is at http://coder-com.undernet.org/. Their e-mail address is coder-com@undernet.org. (H6a)

Undernet User Committee - Provides Undernet Users a place to give their thoughts. This committee has six subcommittees - #UserGuide, Webmasters, Documents, Promotions, Newsletter, and Class. (H7)

The User-Com home page is located at http://www.user-com.undernet.org. The committee's main e-mail address is user-com@undernet.org. (H7a)

North American Routing Committee - Views current IRC Servers and evaluates new applications for servers. The goal of the committee is only to link the most qualified servers. (H8)

European Routing Committee - Acts the same way as the NA Routing Committee, except for focusing only on European Servers. Having separate committees insures the utmost attention is given to this task. (H9)

Both Routing Committee's home pages are at http://www.routing-com.undernet.org. Their e-mail address is routing-com-announce@undernet.org. (G10)

The Undernet also consists of volunteers known as IRCops. These people, picked by server administrators have the job of maintaining the network. To find an IRCop for assistance, type /who 0 o or /who -oper for UNIX. Remember these are busy people, don't get mad if they don't respond at first. (H11)

The Undernet FTP site is a great place to find out more information about the Undernet. Included in this site are history, IRC documents, servers, scripts, clients, pictures, mailing list archives, and misc. utilities. (H12)

We'll now pause briefly in case you have any questions that you need to ask your tutor. (HP)



SESSION I - UNDERNET DOCUMENTATION: How to retrieve important and useful documents. (I1)

As an Undernet user, you have access to a number of documents that help you have an excellent experience online. There are two main sources of documents, HelpBot on IRC, and the Documents Committee. (I2)

When you are in your web browser, you can go to the Documents Committee Web page. This page is very useful in finding what you need, whether it be the Undernet FAQ, or the History of the Undernet. (I3)

The Undernet Documents Committee can be e-mailed also. E-Mail them if you have any ideas for documents or if you have any comments or suggestions for them. Their address is documents@undernet.org. (I4)

Their web page is located at http://www.undernet.org/documents/. At this address, you can find various documents including beginner, advanced, technical, and historical documents.(I5)

If you don't want to go to the WWW, there is a bot online on the Undernet, called HelpBot. For help with using this bot, type /msg HelpBot help. (I6)

HelpBot has many uses. It holds many files available for your download, it has online help with bots, channel listings, and various services. (I7)

There is also another bot on the Undernet run by CService. This bot contains many documents and forms. It's nickname is UnderBot. (I8)

To use both bots, just type /msg <botname> help. This will give you a list of commands to choose from. (I9)

A reminder that because the Undernet is run strictly by volunteers working on their spare time, please read all of the appropriate documentation before asking for help from any of the committees. (I10)

We'll pause briefly in case you have any questions that you need to ask your tutor. (IP)



SESSION J - OTHER REFERENCES: There are many help and assistance channels on the Undernet.  There are also many knowledgeable people to help you out with problems you may have.  Here are some places on The Undernet you can go for help: (J1)

#userguide - Undernet User-Com's help channel, for all general help. (J2)

#winnuke - Technical help and information on nuke attacks. (J3)

#zt - Technical help channel, usually for technical help and channel difficulty. (J4)

#cservice - Undernet Channel Service.  Help with X and W bots and information on how to use them. (J5)

#newbies - Another new users channel to ask questions.  Generally larger than #new2irc. (J6)

#help - Help available for more experienced users, along with newbies. (J7)

#opschool - A CService Class similar to this.  Type /MSG UnderBot motd for the next scheduled OpSchool. (J8)

The Undernet also provides e-mail addresses where you can get help.  Here are a few which you should know. (J9)

cservice@undernet.org - Channel Service mailing list. (J10)

opschool@undernet.org - OpSchool mailing list. (J11)

abuse@undernet.org - Abuse or misuse of powers, e.g. IRC operators, NOT channel affairs. (J12)

help@undernet.org - For more experienced users along with newbie help. (J13)

user-com@undernet.org - User Committee mailing list. (J14)

Like explained before, if absolutely necessary, you can get an IRC Op to assist you. Also, Undernet has a homepage with useful resources at http://www.undernet.org. (J15)

We'll pause briefly in case you have any questions that you need to ask your tutor. (JP)




SESSION K - HELP AND PLACES MENTIONED: Where to find the places mentioned in this class. (K1)

Besides using HelpBot and the Documents Committee, there are many other places to go for help that were mentioned earlier. Many resources are available such as IRC channels, Web sites, and e-mail addresses. (K2)



SECTION A - Floods - NudeDude's NoFlood Document - Available at Document committee web site - www.user-com.undernet.org/documents. (K3)



SECTION B - DoS Attacks - For patches - http://mirc.stealth.net/nuke/ - For Information -  http://www.irchelp.org/irchelp/nuke/. Puppets Page http://www.dynamsol.com (K4)

#ICMPinfo - ICMP information - http://icmpinfo.dynmc.net - Conseal Firewall - Protects against DoS attacks - http://www.signal9.com/firewall/ - Skream's Port Listener - Tracing Nukes - http://skream.simplenet.com/plisten. (K5)



SECTION D - Scripts and Bots - Channels - #bots, #bot. URLs - www.bots.org, www.mircx.com, www.sodre.net/eggdrop, www.user-com.undernet.org/documents. - BotDoc - http://www.user-com.undernet.org/documents/botdocs.html. (K6) 




SECTION E - Advanced Commands - IRC Command Cosmos - http://www.irchelp.org/irchelp/misc/ccosmos.html. (K7)




SECTION G - Undernet Administration - CService - Channel Service Committee - CService@undernet.org - http://cservice.undernet.org - Coder-Com - Coding Committee - coder-com@undernet.org - http://www.xs4all.nl/~carlo17/ircd-dev/. (K8)

User-Com - User Committee - user-com@undernet.org - http://www.user-com.undernet.org - NA and EU Routing-Com - Routing Committees - routing-com@undernet.org - http://www.routing-com.undernet.org. (K9)



SECTION H - Documentation - Documents Committee - http://www.user-com.undernet.org/documents - HelpBot - /msg HelpBot Help - UnderBot - /msg UnderBot Help - Misc Help Channels - #UserGuide, #help, #mIRC, #pIRCH, #CService, #newbies - For various documents and help, check out Undernet's FTP site at ftp://ftp.undernet.org. Also for general IRC help, take a look at www.irchelp.org. (K10)

We'll pause briefly in case you have any questions that you need to ask your tutor. (KP)

last section here

SESSION L - CLOSING: This class is held every fourth Thursday at 7:30PM Eastern. (00:30AM GMT), alternating with the New User Class, Advanced Class and HTML Class. (L1)

It has been a pleasure to teach the class today, and we all hope you learned something new. (L2)

Cyndi> IRC is a fun and exciting way to communicate with others.  We hope you enjoy your experience online, and hope that you come back to the Undernet often. (L3)

We'd like to thank the following people who made this script possible: cpw, bethie, Ferrago, Gamma, NudeDude, Cynthia and WAVVY. (L4)

We'd like to thank these people for helping out by tutoring in classes: joey, Biologie, Linda_UK, Gengis, c64, Ralf :)). (L5)

Additionally we'd like to thank everyone who helps in all of the help channels for their time and effort in making IRC a better place. (L6)

Don't forget to check out our web page at http://www.user-com.undernet.org/class/ (L7)

For a log of this Advanced or the New User Class, check out our web page or e-mail us at class@undernet.org. (L8)

Thank you all for attending, and have a great evening! (L9)

Additionally, please note our scheduling change. The New Users Class will be held here next week, then the advanced class will be held the following week and so on. (L10)

I would like to thank all the tutors and helpers for dedicating their time to help you :) I would especially like to thank you, the users, for caring enough to learn how to use IRC and the Undernet :) be good everyone :) 

*** X changes topic to 'Intermediate Class March 23 7:30PM EST (00-03-28 00:30 GMT) (http://www.user-com.undernet.org/class/)'