DHT blocker - Page 2
 

News:

29 December 2022 - PtokaX 0.5.3.0 (20th anniversary edition) released...
11 April 2017 - PtokaX 0.5.2.2 released...
8 April 2015 Anti child and anti pedo pr0n scripts are not allowed anymore on this board!
28 September 2015 - PtokaX 0.5.2.1 for Windows 10 IoT released...
3 September 2015 - PtokaX 0.5.2.1 released...
16 August 2015 - PtokaX 0.5.2.0 released...
1 August 2015 - Crowdfunding for ADC protocol support in PtokaX ended. Clearly nobody want ADC support...
30 June 2015 - PtokaX 0.5.1.0 released...
30 April 2015 Crowdfunding for ADC protocol support in PtokaX
26 April 2015 New support hub!
20 February 2015 - PtokaX 0.5.0.3 released...
13 April 2014 - PtokaX 0.5.0.2 released...
23 March 2014 - PtokaX testing version 0.5.0.1 build 454 is available.
04 March 2014 - PtokaX.org sites were temporary down because of DDOS attacks and issues with hosting service provider.

Main Menu

DHT blocker

Started by Jorgo, 05 August, 2010, 20:24:41

Previous topic - Next topic

0 Members and 1 Guest are viewing this topic.

For_Ever_MeXxX

He is right Mutor, my Opchat get spammed again, too...

lUk3f1l3w4lK3R

First version of this script did exactly what the script did, that i tried to make myself: it didnt disconnect users with DHT enabled clients (yes, there where DHT enabled clients).
Now the 2nd version of your script works like it should work.

I dont know what caused the issue with your first version
but thanks for updating your script.

Good work as allways Mutor.

Thx alot.

For_Ever_MeXxX

#27
Yes, it was always the same IP for one User...


I was getting the msg from 3 user with DHT in 4secs 4-5times then it stops and after same mins it was starting again...

somewherenotthere

Quote from: Mutor on 21 September, 2010, 04:57:14
No Sir, I was asking if more than one user on a common IP
Hey Mutor, no problem. The users were completely different, and in fact one user was myself (owner) as I was testing the reporting capability. I have since disabled it and have had the problem again, last part of IP left intact for your consideration:

Quote[15:43:37] <*> <*> The Reg, *with I.P.: *.*.150.180 is using DHT.
[15:43:38] <*> <*> The Reg, *with I.P.: *.*.150.180 is using DHT.
[15:43:39] <*> <*> The Reg, *with I.P.: *.*.150.180 is using DHT.
[15:43:41] <*> <*> The Reg, *with I.P.: *.*.150.180 is using DHT.
[15:43:41] <*> <*> The Reg, *with I.P.: *.*.37.234 is using DHT.

If you note: the first 4 are the same person, the last is a different person. This swaps each time, leading me to believe that it is triggered by it checking one user.

It is not a terrible problem, just slightly annoying in what is really helpful script (many kudos to Mutor and other contributors) as the hub is meant for a certain country only, and the apexdc++ devs for some really silly reason decided that they should ship it with it enabled.

Again, thank you for helping out so much Mutor, you have made running a hub much nicer with the many scripts you have made/helped make.

somewherenotthere

Quote from: Mutor on 22 September, 2010, 00:07:05
Another revision, testers welcome.
Also I removed the original script as
I feel at least some people may have
been using that version unwittingly.

Hey Mutor, seems to be better now... i was using the one with the options listed as "0 ,1 , etc"


For_Ever_MeXxX

Working great now... No problems anymore...

Great work, Mutor.  ;)

merlin_xl54

Hi Mutor,

Thanks for all your work. I received this in error from the bot. scripts\DHTDetector.lua:27: bad argument #1 to 'insert' (table expected, got number)
Line 27--> table.insert(Tab[user.sIP],1,GetProf(user))

Thanks again,

M
Living is easy with eyes closed.

SMF spam blocked by CleanTalk