i've been trying to set up a botnet on my bots. Currently i have 3 linked bots. I followed the instruction on web site but the script is not working.
That's what i got:
[2:59am] <bot> Running netbots.tcl v4.09
[2:59am] <bot> 3 bots on the botnet.
[2:59am] <me> .netbots
[2:59am] <bot> What? You need '.help'
Can anyone please tell me why the script is loaded and functionnal but i can't use the netbots commands???
is it just the .netbots command not working, or none of them?
does .nethelp work? .. if it does please do .nethelp netbots and read carefully what it says
from what I can see you are not recognised as the owner of the bot by the script. Either you have messed up the settings, or the code... or there is something abit funny goin on :p
I suggest you look over the settings once more, when you have done that... do it once again .. if it still doesn't work, try changing the settings.
Check the nb_owner setting in netset.tcl. If that is enabled, you need to be a "permanent" owner, not just a +n. To be a permanent owner you need to add your handle to the "set owner" line in the bot's config file.
Papillon wrote:from what I can see you are not recognised as the owner of the bot by the script. Either you have messed up the settings, or the code... or there is something abit funny goin on :p
I suggest you look over the settings once more, when you have done that... do it once again .. if it still doesn't work, try changing the settings.
The only thing funny, perhaps not funny in this case, is that you have something exploiding eggdrop script and managed to hack themself into someone else's eggdrop's party line. In which case, aren't the owner +n or master +m of the bot and have possibly motive of asking for help here with eggdrop to take control of someone else's irc channel or the botnet of the irc network. My suggestion would be to contact the makers of eggdrop to let them know about a possible breach somewhere in eggdrop and for you here to monitor the user closely for any evidence to foward to the proper authorities. And if this isn't the case, I apologize, but the above thread did sound a bit fishy for something not good going on.
mcdarby wrote:And if this isn't the case, I apologize, but the above thread did sound a bit fishy for something not good going on.
That's okay. The wires in people's brains getting mixed up is a frequent occurence here
Without ruling out other possibilities, the problem as Bassez described it is consistent with enabling nb_owner but not setting the owner(s) properly in the config file.