From: Greg Sikorski Date: Tue, 11 Apr 2000 05:51:25 +0000 (+0000) Subject: Author: Gte- X-Git-Url: http://git.pk910.de/?a=commitdiff_plain;h=3fcdeb593e083a65b8d3d1a34edf65afd03d433b;p=ircu2.10.12-pk.git Author: Gte- Log message: * ircd/s_err.c: Added missing quotes to ERR_DONTCHEAT numeric. * doc/p10.html: Work on chapter 4. git-svn-id: file:///home/klmitch/undernet-ircu/undernet-ircu-svn/ircu2/trunk@148 c9e4aea6-c8fd-4c43-8297-357d70d61c8c --- diff --git a/ChangeLog b/ChangeLog index ead07fb..4ea700c 100644 --- a/ChangeLog +++ b/ChangeLog @@ -1,3 +1,8 @@ +2000-04-11 Greg Sikorski + + * ircd/s_err.c: Added missing quotes to ERR_DONTCHEAT numeric. + * doc/p10.html: Work on chapter 4. + 2000-04-10 Kevin L. Mitchell * ircd/channel.c (mode_parse_client): fix coredump on /mode @@ -351,7 +356,7 @@ # # ChangeLog for ircu2.10.11 # -# $Id: ChangeLog,v 1.69 2000-04-10 15:29:09 kev Exp $ +# $Id: ChangeLog,v 1.70 2000-04-11 05:51:25 gte Exp $ # # Insert new changes at beginning of the change list. # diff --git a/doc/p10.html b/doc/p10.html index 26f4cac..eafab9f 100644 --- a/doc/p10.html +++ b/doc/p10.html @@ -2,17 +2,17 @@ - + Undernet P10 Protocol and Interface Specification

Undernet P10 Protocol and Interface Specification

-(As of ircu 2.10.10) +(As of ircu 2.10.11)

Undernet Coder-com, coder-com@undernet.org

-v0.10, 2nd March 2000. +$Id: p10.html,v 1.4 2000-04-11 05:51:25 gte Exp $

This document aims to be a practical guide for implementing and maintaining the protocol, not just a reference @@ -44,16 +44,19 @@ manual.

@@ -812,14 +815,21 @@ line would be:
3.2.4 - JUPE Messages
-
Any currently unexpired JUPEs are transmitted via "JUPE" -messages with the following format:
+
Any currently unexpired JUPEs are transmitted via "JUPE" messages +with the following format:
-
[NUMERIC PREFIX] JU * (+|-)[SERVER NAME] -[LIFETIME] [LAST MOD] :[REASON]
-
-
Notes:
+
[NUMERIC PREFIX] JU * (+|-)[SERVER +NAME] [LIFETIME] [LAST MOD] :[REASON]
+For example: + +
+
1  2  3 4                +5         6         +7 +
AZ JU * +juped.undernet.org 000003593 955419707 +:Juped Server
+Notes:
  1. @@ -843,9 +853,7 @@ The last time the JUPE was modified.
  2. The reason the JUPE was applied.
    3. -
- 3.3 Summary

The following table summarises the sequence of events that occur when a server connects to another server. S1 is our server, and S2 is a HUB @@ -901,7 +909,200 @@ the END_OF_BURST from S2


4. Continuous Operation -

[Back] +

This chapter provides details of the messages that can be sent after +successfully linking to a network, and synchronising the channel/user database. +

4.1 Channel state operations +

There are a number of messages that can modify the state of a channel, +these are: +

    4.1.1 - MODE +

    The MODE message can modify channel modes and bans, and also give or +take operator/voice status from channel members. +

        +
      [NUMERIC PREFIX] M [CHANNEL] (+|-)[MODESTRING] +<MODESTRING PARAMETERS>
    + +


    For Example: +

        +
      1     2 3          +4        5 +
      AZAAA M #coder-com +stinlko 500 TestKey BAC
    + +


    Notes: +
      +

      +
    1. +The numeric of the user issuing this MODE command. It can be assumed this +user is opped on the target channel.
      2. + +
    2. +The "MODE" token.
      3. + +
    3. +The target channel.
      4. + +
    4. +The "Mode string".
      5. + +
        +
      1. +This consists of up to 6 '+' or '-' (add or remove) prefixed channel modes. +(If no '+' or '-' are specified, a '+' is assumed unless a '-' has been +encountered previously in the mode string). For example, '+s+t+n-l-io' +is a valid mode string, as is '+stnmov'.
        2. + +
          +
      2. +Valid Mode modes are:
        3. +
      +
    + +
      +
          + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
        TokenFunctionParameters
        pSets/Unsets 'Private' Flag.None.
        sSets/Unsets 'Secret' Flag.None.
        mSets/Unsets 'Moderated' Flag.None.
        nSets/Unsets 'External Messages' Flag.None.
        tSets/Unsets 'Topic Limit' Flag.None.
        iSets/Unsets 'Invite only' Flag.None.
        lSets/Unsets 'Channel Limit' Flag.The channel limit.
        kSets/Unsets 'Channel Key' Flag.The channel keyword (Password).
        oOps and Deops users.Numeric of user to be opped.
        vVoiceNumeric of user to be voiced.
        bBanBan string.
        +
      +
    + +
      +
    1. +The "Mode string Parameters".
      2. + +
        +
      1. +This is a matching list of parameters to the modes supplied in the "Modestring".
        2. + +
        For Example: +
        If the Modestring is "+stnlo", a typical parameter string would be +"500 AZAA". The first 3 modes, 's', 't' and 'n' do not require parameters, +so non are present. The following two, 'l' and 'o' both require parameters, +so they are 500 and AZAAA respectively (This sets the channel limit to +500 users, and ops the numeric AZAAA).
      +
    + +


    N.B: The "MODE" message is also used to modify a client's user modes, +not just channel modes. See section 4.2 for details.

+ +
    4.1.2 - OPMODE +

    The OPMODE message is identical in syntax to the MODE message, however +it will only ever have an operator as the source. It is likely that the +source of this mode will not have ops in the target channel, but it should +succeed never the less. +

    4.1.3 - JOIN +

    4.1.4 - PART +

    4.1.5 - KICK +

    4.1.6 - TOPIC +

    4.1.4 - CLEARMODE +
      +

      AZAAA CM #coder-com ovpsmikbl
    +
+4.2 Client state operations +
4.2.1 - NICK +
AZAAA N Nick2 955423230
+4.2.2 - MODE +
AZAAA M Nick2 :+odi
+
+4.3 Channel/Client Messaging. +
4.3.1 - PRIVMSG +

4.3.2 - NOTICE +

4.3.3 - CNOTICE +

4.3.4 - CPRIVMSG +
 

+[Back]

5. Programmers reference: Client/Server @@ -925,15 +1126,17 @@ A. ...

8. Update History -

[20/01/2000]: Initial draft, structure, background info. -
[13/02/2000]: Added initial BURST documentation. -
[14/02/2000]: Continued BURST documentation / Begin NICK and SERVER +

[2000-01-20]: Initial draft, structure, background info. +
[2000-02-13]: Added initial BURST documentation. +
[2000-02-14]: Continued BURST documentation / Begin NICK and SERVER documentation. -
[26/02/2000]: Continued chapter 5, few example fixes, added token table -from msg.h. --Gte. -
[02/03/2000]: Added NICK spec. --Gte. -
[18/03/2000]: Added JUPE spec. -Kev -
[2000-04-10]: Added information about OPMODE and CLEARMODE tokens. -Kev +
[2000-02-26]: Continued chapter 5, few example fixes, added token table +from msg.h. -Gte. +
[2000-03-02]: Added NICK spec. -Gte. +
[2000-03-18]: Added JUPE spec. -Kev +
[2000-04-10]: Added information about OPMODE and CLEARMODE tokens. +-Kev +
[2000-04-11]: Started work on chapter 4. -Gte

8.1 TODO

  • @@ -946,7 +1149,7 @@ Go through examples, and ensure they are all correct.
    • Add common function headers, with argv listings.
  • -Add description of further server<>server messages, with special cases +Add description of further server to server messages, with special cases and outcomes.
  • diff --git a/ircd/s_err.c b/ircd/s_err.c index 2679456..aa1fa23 100644 --- a/ircd/s_err.c +++ b/ircd/s_err.c @@ -302,7 +302,7 @@ static Numeric numeric_errors[] = { /* 515 */ { ERR_BADEXPIRE, TIME_T_FMT " :Bad expire time", "515" }, /* 516 */ - { ERR_DONTCHEAT, " :Don't Cheat.", 516 } + { ERR_DONTCHEAT, " :Don't Cheat.", "516" } }; static Numeric numeric_replies[] = {