egginfo - Botnet Linking Explained

Botnet Linking / Sharing Userfile

We will go through how to link your bots together into a single partyline (dcc session). We will also discuss further on how to enable userfile sharing amongst your linked bots.

Let us start by reviewing what bot specific flags are available.

Botnet Flags
s	aggressive share (bot is sharing user records, aggressively)
p	passive share (bot is sharing user records, passively)
g	global share (bot is sharing all channels)
h	hub (bot is autolinked at highest priority)
a	alternate (bot is autolinked if no hub bots can be linked)
l	leaf (bot is not allowed to link other bots onto the botnet)
r	reject (bot will not be allowed to link to the botnet)
i	isolate (isolate the party line across a botlink)

To change a bot flag you need to use .botattr e.g.

.botattr bot +h            (would make the bot always attempt to link too any bot with the +h (hub) flag.)

You should not only 1 bot can be marked as a hub in any userlist, and subsequent +h bots marked on a userlist will be ignored (i.e. the user that comes 1st in the userlist and has +h will be assumed the hub). This also goes for +a (alt-hubs).

Important commands

.+bot <handle> address:telnetport

This is the command you would use to add any new bot into your bots userlist. the address can be the bots host or ip from 'set my-ip' and 'set my-hostname' sections of your config. the telnet port would be the number from ' listen 3334 all ' section of the config (the default being 3333).

Some people may have different ports for users and bots as below.

# listen 3333 bots
# listen 4444 users

In this case you can add the bot using:

  .+bot <handle> address:BotPort/UserPort 
e.g. 
  .+bot fiddle host.domain.com:3333/4444

.chaddr <bot> address:telnetport

You can use this to modify any details of a bot that have been changed, the syntax is similar to .+bot.

.dccstat

 SOCK ADDR     PORT  NICK      HOST              TYPE
 ---- -------- ----- --------- ----------------- ----
 3    D5E6D110  8987 (telnet)  *                 lstn  8987

.dccstat offers a quick way for you to check what port your bot is using without having to open up and look at your config, above the port is 8987.

.bottree .vbottree .botinfo .bots

The above are varius commands to see details of linked bots.

Examples

Lets now go onto some examples, using 3 bots fidde, dastardly, deity and eggdev this is how i would go about linking them.

From the partyline on fiddle:

.+bot dastardly someotherhost.com:5678
.+bot deity some.host.net:9841
.+bot eggdev somwhere.org:3334

From the partylines of dastardly, deity and eggdev:

.+bot fiddle somehost.com:8645
.botattr fiddle +h
.link fiddle (if required)

Now when i type .bottree I would see:

 dastardly
   `--fiddle
        |--deity
        `--eggdev

If you see anything similar to the following you need to go back and double check what host and port you are using and confirm they are correct.
*** [dastardly] Couldn't link to fiddle.

You really want to be seeing like this, depending on which bot you are on.
<fiddle> [16:13] Linked to dastardly.

Sharing userfiles

Sharing userfiles allows you to maintain a single user list without having to add a new user to each bot seperately. To be able to share you need to ensure modules, share, transfer and channels are loaded.

loadmodule share
loadmodule transfer
loadmodule channels

The bot that is sharing the usefile aggressively needs to be linked directly to all other bots that it will be sharing a userfile with. So this means that the hub will in most circumstances be sharing its userfile aggresively.

Let us take a moment to define aggressive and passive sharing... this means that the but sharing aggressively will be the one sending the userfile to all bots linked to it (i.e. all leaf bots). Passively means they will download the file and assume it as the masterfile. This does not prevent you from adding to the masterfile from your leaf bots, as any users you add while the bots are linked should also be transferred to the masterfile.

Taking the above into consideration you would need to type the following on each of the bots, assuming we want the 4 above to share userfiles.

fiddle:

.botattr dastardly +gp
.botattr deity +gp
.botattr eggdev +gp

dastardly, deity and eggdev:

.botattr fiddle +gsh

The g (global) flag means that all channel data will be shared. If you want to only share specific channels data you would limit what is shared by not including the g (global) flag. Instead you would need to type

.boattr fiddle |+s #channel

This would need to be done on every leaf bot for each channel. The +g flag negates this and simply allows global shares.

 fiddle
  |-+deity
  |-+eggdev
  `-+dastardly

This time you type .bottree you will see a + next to each of the bots. This means that they are sharing userfiles.

egginfo.org

Home, Tcl Tutorial, Tcl/Tk Installation, Modules, Tcl Scripts, Misc Downloads, Bot Commands,

Help/FAQ, Unix Commands, Message Commands, Shell Info/Reviews, About, Contact, Links. Nano & Pico.

Bnc's, Config Generator, OnJoin/Greet Generator, Identification Generator, Botnet creation & userfile sharing

IPV6, Vi Editor, Sitemap, Knowledgebase .

Select your language: