egghelp/eggheads community

Botnetop component.

2003-09-10T01:25:35-04:00

If you read the netbots documentation you will notice it says:

Note that the delay (bop_delay) is automatically skipped if there are fewer than 3 bots opped on the channel.

So although you set bop_delay to 300 , if you only have 2 bots on the channel... this will be skipped.

This section of code was taken from botnetop.tcl:

Code:

if {!$bop_delay || [bop_lowbots $chan]} {  utimer 5 [list bop_askbot $hand $chan]} else {  utimer [expr [rand $bop_delay] + 5] [list bop_askbot $hand $chan]}...proc bop_lowbots {chan} {  global botnick  set bots 1  foreach bot [chanlist $chan b] {    if {$bot != $botnick && [isop $bot $chan]} {      incr bots    }  }  if {$bots < 3} {return 1}  return 0}

Which, if I understand it right, means that when there are only 2 bots on the channel ... bot_delay automatically becomes 5 seconds.
How many bots do you have on the channel ? I am talking about bots which are flagged as +b so they are recognized as bots by other bots.

Statistics: Posted by z_one — Wed Sep 10, 2003 1:25 am

Botnetop component.

2003-09-09T15:31:49-04:00

Well.. bot joined the network. he attempts to login to services and after an succesfull log in will ask for his needs. If it's oped and deoped by the lagged services will get an notice or something to login in order to be op on the channel. Stop any "contact" with the other bots and attempt to login to services. After he successfully logged in continue the "contact" with the other bots. Something like this anyway.

Statistics: Posted by caesar — Tue Sep 09, 2003 3:31 pm

Botnetop component.

2003-09-09T14:46:59-04:00

caesar: Yeah, something like that. But how?
z_one:

Code:

# botnetop.tcl settingsset nb_component(botnetop) 1set bop_delay 500set bop_maxreq 2set bop_modeop 1set bop_linkop 1set bop_icheck 0set bop_hcheck 1set bop_osync 1set bop_addhost 1set bop_log 2

I've set it to 500, hehe, so it'll ask late.[/code]

Statistics: Posted by Yourname — Tue Sep 09, 2003 2:46 pm

Botnetop component.

2003-09-08T14:57:04-04:00

Well, an nice lil "workaround" will be to make it ask for ops ONLY if he is identifyed with the services. Only then he can ask from other bot's for his needs. Also, when the bot (who is not yet identifyed) get's deoped by the services dosen't he get an notice or something? When the services are lagged or something similar, if he get's oped and then the lagged services deop him and send an notice about this he would attempt to login and stop any "requests" from any other linked bots untill he get's identifyed by the services.. something like this anyway.

Statistics: Posted by caesar — Mon Sep 08, 2003 2:57 pm

Botnetop component.

2003-09-08T14:48:36-04:00

What are your botnetop settings ?

Statistics: Posted by z_one — Mon Sep 08, 2003 2:48 pm

Botnetop component.

2003-09-06T10:11:24-04:00

hehe, no gumby, there's a nice solution someone keeps giving me everytime I ask this frigged question, so I'm waiting for that. Hold on and keep watching this thread, you'll be surprised to see the solution

Statistics: Posted by Yourname — Sat Sep 06, 2003 10:11 am

Botnetop component.

2003-09-06T06:16:52-04:00

well sounds to me like that is simply how it works yourname.. its like +bitch on services.. seeing how you cant control services.. but can control your bots.. i would *cringe* take the mode off the room... and set your bots +bitch... you seem to not want ops opping people. This mode in effect does the same damn thing +bitch does... another possible solution.. would be to add services to your bots... and give it enough access so your bots let it win... therefore no flood...

Statistics: Posted by gumbydammit — Sat Sep 06, 2003 6:16 am

Botnetop component.

2003-09-06T03:11:23-04:00

I always seem to be asking this and forgetting the answer on 6 month period. *sigh* :/

Anyways.

On DALnet, there are services. And channels have this ident thingie on which means if the channel is set to ident, all the ops MUST identify to services before they can get opped. So, unless and until an op does'nt identify the op won't get opped by services. And if a human or some other op ops this newly joined op, the services will deop him. You know what I mean?

Now, this is the scenario, sometimes the services are lagging or the bot did'nt identify or it takes time for the services to acknowledge that the bot has identified or somethng and it joins the channel, and another botnet op bot has opped it, services will deop that new bot. Why? because the new bot has'nt identified yet. And that way a op flood comes on, services keep deopping the bot, and the other opped bot keeps opping the newcomer bot.

Any workaround to this? (Please don't tell to turn the ident option off, it's secure, for the other human ops. Plus I'm not the founder)

Statistics: Posted by Yourname — Sat Sep 06, 2003 3:11 am