I.   Gathering The Information   

You need to make sure that bot bots are running on IRC and you need to correctly identify both bots Nick, Ident and Hostname. The following is an example using 2 bots named hubbot and linkbot on irc.

Now, DCC chat both bots, as this is where the commands will be sent (not via telnet to the shell) :

    /whoishubbot
     Hubbotishubident@satexas.com

    /whoislinkbot
     Linkbotislinkident@alamo.satexas.com
Special Note : It is very important that you pay close attention to the details of where the information for each bot is entered into the other bot, how, why and where. 99% of all mistakes are made entering in the wrong information, so please do not take anything for granted in the following steps.


   II.   Configuring The First Bot (hubbot)   

While in DCC chat with linkbot, type :

    .dccstat

    You will see an output like the following :

    <linkbot>   SOCK   ADDR       PORT   NICK     HOST              TYPE
    <linkbot>   ----------------------------------------------------------------------
    <linkbot>       3    180000C8    59630     (telnet)    *                   lstn
    (take notice to the listen port)-^

Now that we know the port, we need to let hubbot know this information, and configure it. While in dcc chat to hubbot, do the following :
    .+botlinkbotalamo.satexas.com:59630

     <hubbot> Added bot 'linkbot' with address 'alamo.satexas.com:59630' and no password.
    <hubbot> You'll want to add a hostmask if this bot will ever be on any channels that I'm on.

    .+hostlinkbot*!linkident@alamo.satexas.com

     <hubbot> Added '*!linkident@alamo.satexas.com' to linkbot

    .chattr linkbot +fo
     <hubbot> Global flags for linkbot are now +bfo

    .chpass linkbot SoMePaSsWoRd
     <hubbot> Changed password.

    .botattr linkbot +gs
    <hubbot> Bot flags for linkbot are now +gs
      Warning : Unless you want HubBot to share and send its .user file to Linkbot, leave off the s in the +gs above.

   III.   Configuring The Second Bot (linkbot)   

While in DCC chat with hubbot, type :

    .dccstat

    You will see an output like the following :

    <hubbot>   SOCK   ADDR       PORT   NICK     HOST              TYPE
    <hubbot>   ----------------------------------------------------------------------
    <hubbot>       3    128320C8    24686     (telnet)    *                   lstn
    (take notice to the listen port)-^

Now that we know the port, we need to let linkbot know this information, and configure it. While in dcc chat to linkbot, do the following :
    .+bot hubbot satexas.com:24686
    <linkbot> Added bot 'hubbot' with address 'satexas.com:24686' and no password.
    <linkbot> You'll want to add a hostmask if this bot will ever be on any channels that I'm on.

    .+host hubbot *!hubident@satexas.com
    <linkbot> Added '*!hubident@satexas.com' to hubbot

    .chattr hubbot +fo
    <linkbot> Global flags for hubbot are now +bfo

    .chpass hubbot SoMePaSsWoRd   (Note: same password as before!)
    <linkbot> Changed password.

    .botattr hubbot +ghp
    <linkbot> Bot flags for hubbot are now +ghp
      Warning : Unless you want Linkbot to share and get its .user file from Hubbot, leave off the p in the +ghp above.

    .link hubbot
    <linkbot> Linking to hubbot at satexas.com:24686 ...
    <linkbot> Received challenge from hubbot... sending response ...
    <linkbot> Linked to hubbot.
    <linkbot> Downloading user file from hubbot
    <linkbot> Userfile loaded, unpacking...
    <linkbot> Userlist transfer complete; switched over.

Special Thanks goes to Pete of #SATEXAS on efnet, for writing and developing the steps on this web page.


© 1996-2007 COMPANY_FULL
Map  -  Sales & Information  -  Parental Control Software