We have had many problems as EFNetters lately. Netsplits, DoS attacks, server unlinkings etc. Another problem is rival channels trying to gain ops and close down channels. This has happened alot and fortunately none of our channels have been taken. We had 2 shells and 7 bots. They were pretty stable and even if 1 shell had some downtime the other remained online and kept things going. Then disaster. Shell #1 had a serious HDD crash, fortuneatley there was a recent backup. However all the other bots pinged out and we were left with an @home user a sleep sitting with +v. It took over 12hours to get everyone out and to cycle the bots. 5 or 6 days later the Shell #1 with the bots on packed its bags and never returned. 1 shell, 2 bots. This went from bad to worse. The bots pinged out once a day and ops lost 3 or 4 times a week. It had to stop.
All 4 +n got togethor and decided on a new MeGA botnet. 7 shells, 16 bots, and 4 bncs. We laid down the rules, Each +n would ahve shell access and bounce access. There would be only 1 +m per channel and no global ops or +m. We picked the shells and orgnised payments and contracts. We like to do things properly in the UK. IF ANY ONE PERSON MISSES A PAYMENT THE WHOLE THING IS OFF. is scrawled in the motd. That is the most important rule.
We ordered the shells each using different idents and hosted in various places in america and on different backbones. HQ was the first bot set up. It is what is known as a limbo hub. It never journeys on to IRC and controls the userlist and such. This bot has to be stable and fast.
We then set up the other bots using eggdrop1.4.4 and netbotsV.3.5. Each .conf was then modified to the bots own name host etc etc. Other tcl include NOCHANCTCP to stop idiots getting everyones pings (I find most people do this when the channel goes quiet and they think they are lagging) or versions. ircN addon,. this is usefull as it tells ppl it is an ircN user not a bot and serves as a nice anti-idle. No bot has ever been k-lined or d-lined using this script. We use a nice password util, this make sure pusers have 3r33tanDp|mp1N passwords not the usual abc123 or nick123. We unbound all but 2 msg commands. And rebound the op and setpass commands differently. This greatly increases security and stops people trying the addhost and ident commands.
The botnet went online and sat in our secret channel. With all 4 of us on the partyline of HQ we set about our task. We then set about routing the bots to the hub. Each shell has a mini hub which will then connect to the main hub this means if the hub is down then the can still operate as a net not as individuals. We got them all linked and sharing user files. Then disaster number 1. .netjoin #*********, HQ can't do those commands, somebody had set it up as default control bot. So we elected the new control bot. and edited all the tcls accordingly on all the 6 of the shells. Boom we got all the bots into all the channels and set it up all nice, they opped each other set the correct modes. We set up all the users and it worked fine. A shell pinged out and came back. SUPER
bacardi
#bacardi# bottree
HQ
`-+*******
| `-+******
|-+*******
| `-+******
| `-+******
|-+******
|-+******
| `-+*******
| |-+*******
| `-+*******
|-+*******
| `-+*******
`-+*******
`-+*******
Average hops: 1.8, total bots: 14
? Discuss This Article here.
|
Syndicate
