Page 1 of 1

LAG

Posted: Thu Aug 13, 2009 3:10 am
by intel233
I have a bot on my ircd and when I do anything it lags really bad. I made the bot a admin and that seems to have fixed the issue but would prefer not to have it with admin rights. What would I need to change so the lag is not really bad?

Re: LAG

Posted: Thu Aug 13, 2009 5:46 pm
by Stealth

Re: LAG

Posted: Thu Aug 13, 2009 8:51 pm
by intel233
Saw that but was hoping for another solution. I will just make the bot a admin.

Re: LAG

Posted: Thu Aug 13, 2009 9:11 pm
by katsklaw
hmm, that poses an interesting theory though.

Which is better?

1> Bot is non-oper and has nofacklag, gets hacked and floods until the ircd crashes (hopefully returning due to a well configured crontab). If you're smart the bot won't return (you had the forethought to plan for such an event).

2> Bot is an admin level user, gets hacked and hacker add access for themselves where ever possible creating a security breach that could ultimately turn out to be a nightmare to track depending on the configuration of the bot, level of access the bot has and cleverness of the hacker.

Re: LAG

Posted: Thu Aug 13, 2009 10:27 pm
by Stealth
I have not yet seen an IRCd crash as a result of someone sending too much data, and part of me is inclined to believe this is a myth. However, if the IRCd sends and receives everything without fakelag and your recvq and sendq values are high, it would enable a user to load up clones and DDoS the IRCd by sending massive amounts of data to it.

Re: LAG

Posted: Fri Aug 14, 2009 4:58 am
by katsklaw
well sure. It is possible to crash an IRCd like this. Rather easy to do on older versions of Anope and with the correct script can be done on demand. Obviously, I won't share exactly how for reasons that should go without saying, but it's very possible that other IRC related applications can be just as vulnerable and I say that simply because of how the flood works.

The likely hood of a bot that has it's own allow block and allowed to flood being hacked it rather remote, but like all things networked, it's still possible. I was just bouncing a few scenarios around my head to see which is worse, nothing serious meant by it. It's really just personal opinion as to which is worse .. a compromised O:Line or a crashed ircd.. :)