Reverse lookup enabled and bittorrent stopped working
I've come across an interesting situation. After a drive meltdown, I reinstalled Debian Etch on my CP. Now, before the drive busted, Azureus worked beautifully. Now, however, when I use Azureus, I can neither connect to any other peers nor can I be connected to. All the tests says my firewall is open on the proper ports, and I've searched for some way to disable the reverse lookup that is now happening. The peers that are attempting to connect (or connect to) are being listed in my connection log on my DSL modem/router as 220.127.116.11.in-addr.arpa instead of 18.104.22.168 (or whatever the IP was), which had never happened before the crash. Something is doing this and I have no idea what it may be. Any help, folks?
Edit: Something odd I noted. Every now and then, people using BitComet clients (various versions) seem to be connected, but they show themselves as having no data whatsoever. I neither download from or
upload to them.
Follow up: Problem solved. Turns out, it wasn't a program controlling things, it was my Java version. A symbolic link was pointing to the wrong Java version. Sorry for the trouble!
Last edited by Fluxxdog; 05-06-2006 at 03:51 PM.