Hi,
For a start, do everything
slowly!
When I first setup a botnet, now consisting of 17 bots, I had a couple of attempts at it to get it right. The documentation can be a little confusing if you do not concentrate and try and rush through the process.
The process is helped if all bots on the botnet share a common channel as their hostmasks are grabbed when they are added to each respective bot.
For a start, +h is
not set in the bot you wish to have as hub instead, it's set in the bots that you wish to have link to your hub bot. It is also from the hub where you control the other bots, not the other way around. If Blade is your hub then in Eef you would do .+bot Blade and in Blade you would do .+bot Eef.
The command syntax is: .+bot <handle> [address[:bot port[/user port]]] [host]
address is the ip of the bot to add &
port is the address which you wish your bot to communicate through. Each bot has to have a different port otherwise you get nothing but confusion. This port also has to be enabled in each bots' config in the "##### BOTNET/DCC/TELNET #####" section.
Here's an example of using the command to add bots into each other (this process is repeated in each of the bots in the botnet):
.+bot Blade 213.197.58.118:3334
In Blade's config you would have: listen 3334 all
In Blade you then add Eef. Set ports at least 10 apart to stop any confusion. It also helps to write down which bot is assigned which port.
When that is done, in Eef you then do .botattr Blade +h (this makes Blade the hub)
Next, in each bot, .chattr <handle> +fo ie: in Blade .chattr Eef +fo and in Eef .chattr Blade +fo.
For information on user flags type .help whois
Eef should then automatically connect to Blade. This does not happen immediately. So, wait!
Any alterations to the config files will require a bot restart.
I hope this helps you
cant you make the help file