Re: Hi, and a couple questions
Andy Smith <[email protected]>
| Newsgroups | gmane.network.irc.bopm |
|---|---|
| Message-ID | <[email protected]> |
On Fri, May 27, 2005 at 11:26:24PM -0400, Jeff Lec wrote: > We want to have one bopm handle the entire network (around 36k users), > because many of the linked servers will have AUP violations for scanning > remote hosts. Will there be any problem with us making a fairly decent > number of queries per second to the opm blacklist dns? We'll be setting > the one bot to scan, and will be happy to repopt additional open proxies > that we come across. This is not likely to become a problem, however, it would be nice if you would look into running an rbldnsd of your own and taking an rsync of our zone file every half hour. That would also give you more control. > This leads to the next question. Right now, we're using the > network-bopm.pl script and a bopm that relies on services (operserv, to > place AKILLS (global klines). We want to have bopm be independent of > services and not relying on a perl script to handle all the connection > parsing, so I am currently working on getting bopm to connect as a > server directly and handle all the connection parsing and kills itself. > It will be running on one of the hosts that allows scanning. Do you > have any recommendationsto help the one bot handle the network worth of > connections? See any problems with doing it? Craig already gave one useful answer. Personally I can see upsides and downsides but I don't think it's been tried enough in practice to really give an authoritative answer. Let us know how you get on :) Thanks for using BOPM. -- Andy Smith -- Occasional BOPM Developer And Support Monkey. Please copy all BOPM support queries to the BOPM list, _not_ just directly to me! If I've helped you with BOPM then please check my wishlist! http://www.amazon.co.uk/exec/obidos/registry/23IJ4U7N4J3X9
signature.asc
(application/pgp-signature, 189 B)
-----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.5 (GNU/Linux) iD8DBQFCmIV3IJm2TL8VSQsRAuefAKD1NotmASVQJVFy2WmYEIRlndP6uQCg+lkk E2fDzVCtx62CcSGchpiDlnE= =pfEO -----END PGP SIGNATURE-----