PtokaX 0.3.3.2 released... - Page 3
 

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

PtokaX 0.3.3.2 released...

Started by PPK, 31 July, 2005, 18:24:31

Previous topic - Next topic

0 Members and 1 Guest are viewing this topic.

blackwings

the default is 50 on max logins, will it take allot more cpu to raise the value to 100?


bluebear

QuoteOriginally posted by blackwings
the default is 50 on max logins, will it take allot more cpu to raise the value to 100?

I recalls a pm with PPK (not sure if im correct) but he said this was made an option. The older ptokax has the limit set to 50, but now there is the setting, wich defaults to 100 (or 50 if im wrong).

Changeing the setting will not take more cpu. Its the amount of concurrent validateing users that desides how much cpus is used. The logics will say that, the more concurrent users who are validated the more cpu you will use. But this setting is not that important, it is unlikely that this many users will connect to you and be validated simultanious (not counting hub restarts and such). But setting this to low on older ptokax version will allow a connection flooder to block access to new users. But this is resolved, with the inbuild deflood.

If it was me who maintained ptokax, this setting would be removed, and the usage of operation time-out would be used instead.
Sincerely,
bluebear
--
http://www.thewildplace.dk/ is is closed - Use the following mirrors instead
http://bluebear.psycho-chihuahua.net
http://pxextension.piratez.dk/
[Lua extensions - Chat stats - YnHub PMSpy - DC Source code - and more]

PPK

MaxLogins is no more used for mas simultaneous logins in 0.3.3.2x (= no more way to use it to block hub with flooder), is used for something else and will be replaced with another and better setting  :))
"Most of you are familiar with the virtues of a programmer. There are three, of course: laziness, impatience, and hubris." - Larry Wall

bluebear

Sounds good, what kind of setting will this new one be?
Sincerely,
bluebear
--
http://www.thewildplace.dk/ is is closed - Use the following mirrors instead
http://bluebear.psycho-chihuahua.net
http://pxextension.piratez.dk/
[Lua extensions - Chat stats - YnHub PMSpy - DC Source code - and more]

PPK

Something like how much users with finished login sequence add to hub simultaneously -> send userlist to this users -> if hub send it to very much users then is upload on max and hub start dropping users with connection reset :rolleyes:
"Most of you are familiar with the virtues of a programmer. There are three, of course: laziness, impatience, and hubris." - Larry Wall

bluebear

If i understand this right:
Unlimited number of clients can be validated simultaniously. But the nicklist/motd will only be sent to a limited amount of clients simultaniously, and the rest will be placed in a queue?

This will still could be exploitet, as easily as before.

I still think a operation timeout would be better (i know you don't want more timeouts).
For example.
hub sends
$Lock|
Now the client has 2 seconds to send $Supports or $Key
And then the same timeout for each command required to validateing this clients.
Sincerely,
bluebear
--
http://www.thewildplace.dk/ is is closed - Use the following mirrors instead
http://bluebear.psycho-chihuahua.net
http://pxextension.piratez.dk/
[Lua extensions - Chat stats - YnHub PMSpy - DC Source code - and more]

PPK

QuoteOriginally posted by bluebear
For example.
hub sends
$Lock|
Now the client has 2 seconds to send $Supports or $Key
$Lock is on start of login sqeuency and limit is after full login is finished and user be added to hub... timeout like this is here only waste of cpu :rolleyes:
"Most of you are familiar with the virtues of a programmer. There are three, of course: laziness, impatience, and hubris." - Larry Wall

Psycho_Chihuahua

[21:21:01] <.BlindGuardian.>
------------------------------------------------------------
Current stats:
------------------------------------------------------------
Version: PtokaX DC Hub 0.3.3.21 [debug] built on Aug 1 2005 04:03:42
Uptime: 19 days, 14 hours, 37 minutes
Users (Max/Actual Peak (Max Peak)/Logged) : 150 / 70 (70) / 61
Chat messages: 5237 x
Unknown commands: 0 x
PM commands: 10516 x
Key commands: 9378 x
Supports commands: 9485 x
MyINFO commands: 33851 x
ValidateNick commands: 5602 x
GetINFO commands: 56 x
Password commands: 7847 x
Version commands: 3500 x
UserIP commands: 39788 x
GetNickList commands: 7826 x
Search commands: 382872 x
SR commands: 128086 x
CTM commands: 8537963 x
RevCTM commands: 2048013 x
BotINFO commands: 0 x
------------------------------------------------------------
CPU usage (60 sec avg): 1.40%
CPU time: 8:38:53
Mem usage (Old style): 1437 kB
Mem usage (Peak): 7.00 MB (20.65 MB)
VM size (Peak): 8.38 MB (25.83 MB)
------------------------------------------------------------
SendRests (Peak): 0 (2)
RecvRests (Peak): 0 (2)
Data sent: 2.18 GB
Data received: 442.38 MB
Tx (60 sec avg): 382 B/s (1.67 kB/s)
Rx (60 sec avg): 344 B/s (287 B/s)


Intel 2,8ghz
512MB DDRAM
20 scripts
PtokaxWiki ?PtokaX Mirror + latest Libs

01100001011011000111001101101111001000000110101101101110011011110111011101101110001000000110000101110011001000000101010001101111011010110110111101101100011011110111001101101000

Snoris

#58
------------------------------------------------------------
Current stats:
------------------------------------------------------------
Version: PtokaX DC Hub 0.3.3.21 [debug] built on Aug  1 2005 04:03:42
Uptime: 4 days, 1 hours, 46 minutes
Users (Max/Actual Peak (Max Peak)/Logged) : 700 / 233 (233) / 49
Chat messages: 35 x
Unknown commands: 0 x
PM commands: 54 x
Key commands: 14498 x
Supports commands: 13631 x
MyINFO commands: 83067 x
ValidateNick commands: 14478 x
GetINFO commands: 2731 x
Password commands: 498 x
Version commands: 13631 x
UserIP commands: 11011 x
GetNickList commands: 13596 x
Search commands: 41053 x
SR commands: 29739 x
CTM commands: 25892 x
RevCTM commands: 11874 x
BotINFO commands: 0 x
------------------------------------------------------------
CPU usage (60 sec avg): 0.02%
CPU time: 0:01:46
Mem usage (Old style): 1920 kB
Mem usage (Peak): 5.12 MB (20.06 MB)
VM size (Peak): 7.18 MB (21.76 MB)
------------------------------------------------------------
SendRests (Peak): 0 (2)
RecvRests (Peak): 0 (1)
Data sent: 318.64 MB
Data received: 18.27 MB
Tx (60 sec avg): 0 B/s (529 B/s)
Rx (60 sec avg): 0 B/s (90 B/s)

*EDIT*
using a AMD 64 3500+ 1536MB ram


Quattro

#59
QuoteOriginally posted by bluebear
QuoteOriginally posted by bastya_elvtars
QuoteOriginally posted by BeeR
Hellu folks

can some1 tell me whats this is and whats happends if i change the value ??
MaxLogins=100

Maybe it sets the number of maximum simultaneous logins. A geek can also tell how this is influenced by WinXPSP2.

The MaxLogins setting is the threshold for how many simultanoius clients that can be validated.

I belive this setting has nothing todo with Microsoft Windows XP SP2 nor socket features in Microsoft Windows 2003 Server. But it is true that the windows sockets, in Microsoft Windows XP SP2 changes (restricts) some things. But it is mostly on raw socket, and programs affected would probably be programs like port scanners and such. Anyhow you should not concern your self about this, unless your developing software, or is some kind of superuser.

Hope this answer was usefull :)

I didn't notice any problems with my ptokax on winXP SP2
But i got troubles with DC++ though....
DC++ will drop connections with hubs randomly or can't send enough data to the hub to stay in, causing the hub to disconnect you.
This definitely has something to do with the 10 handshakes per second, i was tinkering with the setting a bit using a special program and finally i opened them all.
This fixed my problem

So i recommend everyone using this program, sorry i can't remember the name or adress :S
quattro-place.no-ip.com:1418
PtokaX DC Hub 0.3.3.0 build 17.09 Not Running :(
wdp10.no-ip.info:1412
DCH++ v1.0-Release (Plugin API v1.0) Special Quattro? Build
For DCH scripting and plugins

bluebear

QuoteOriginally posted by Quattro
I didn't notice any problems with my ptokax on winXP SP2
But i got troubles with DC++ though....
DC++ will drop connections with hubs randomly or can't send enough data to the hub to stay in, causing the hub to disconnect you.
This definitely has something to do with the 10 handshakes per second, i was tinkering with the setting a bit using a special program and finally i opened them all.
This fixed my problem

So i recommend everyone using this program, sorry i can't remember the name or adress :S

Did you get any error with ID 4226 in your eventlog?
I have no problems with loss of connections to hub or anything else. Error ID 4226 i get sometimes (to many handshakes) but it do not cause loss of connections.
And a handshake has nothing to do with a connection already established, means that your connection loss probably did not happen because of restrictions on incomplete outbound connections. When i get the 4226 it is because i use all available bandwidht; this results in slow establishment of new connections and the limit will be reached fast. Mostly of all this will only slow down your programs, and i do not belive your dc client problem was directly caused by thease new restrictions in sp2. If your use many different p2p programs simultanious you might suffer greatly under this new restriction. The restriction might cause some programs to do unexpected things, like crash or maybe even drop a connection. The developer of your client should be the one to fix that.
Sincerely,
bluebear
--
http://www.thewildplace.dk/ is is closed - Use the following mirrors instead
http://bluebear.psycho-chihuahua.net
http://pxextension.piratez.dk/
[Lua extensions - Chat stats - YnHub PMSpy - DC Source code - and more]

Quattro

SP2 is definitely the cause of the connections being dropped
Because changing the amount of handshakes solves this problem
quattro-place.no-ip.com:1418
PtokaX DC Hub 0.3.3.0 build 17.09 Not Running :(
wdp10.no-ip.info:1412
DCH++ v1.0-Release (Plugin API v1.0) Special Quattro? Build
For DCH scripting and plugins

bastya_elvtars

You can do this setting with XP-Antispy.
Everything could have been anything else and it would have just as much meaning.

bluebear

QuoteOriginally posted by Quattro
SP2 is definitely the cause of the connections being dropped
Because changing the amount of handshakes solves this problem

Okay then, but after reading what you described I still don't see any logical reason to why the limit on incompleted outbound connections, also should effect connections that is already established (completed).

I've testet it, by writeing a small program that connects to dcdev hub, and then it keeps flooding new connections that will not be completet (cause the ip is not used). And the programs connection to hub is not dropped nor is it in any other programs i use.

But if this little program bast posted solved your problem it's just great.
Sincerely,
bluebear
--
http://www.thewildplace.dk/ is is closed - Use the following mirrors instead
http://bluebear.psycho-chihuahua.net
http://pxextension.piratez.dk/
[Lua extensions - Chat stats - YnHub PMSpy - DC Source code - and more]

BeeR

#64
------------------------------------------------------------
Current stats:
------------------------------------------------------------
Version: PtokaX DC Hub 0.3.3.21 [debug] built on Aug  1 2005 04:03:42
Uptime: 1 days, 11 hours, 37 minutes
Users (Max/Actual Peak (Max Peak)/Logged) : 2000 / 1592 (1592) / 1586
Chat messages: 293 x
Unknown commands: 0 x
PM commands: 183 x
Key commands: 794705 x
Supports commands: 760167 x
MyINFO commands: 825114 x
ValidateNick commands: 794758 x
GetINFO commands: 1 x
Password commands: 35 x
Version commands: 774919 x
UserIP commands: 146425 x
GetNickList commands: 772113 x
Search commands: 234793 x
SR commands: 2352944 x
CTM commands: 737860 x
RevCTM commands: 484344 x
BotINFO commands: 9 x
------------------------------------------------------------
CPU usage (60 sec avg): 8.58%
CPU time: 0:55:26
Mem usage (Old style): 3408 kB
Mem usage (Peak): 30.82 MB (49.64 MB)
VM size (Peak): 26.11 MB (44.97 MB)
------------------------------------------------------------
SendRests (Peak): 30 (47)
RecvRests (Peak): 0 (8)
Data sent: 13.87 GB
Data received: 661.20 MB
Tx (60 sec avg): 37.08 kB/s (376.11 kB/s)
Rx (60 sec avg): 11.13 kB/s (12.41 kB/s)


P4 2.8
1Gb ram
A cold BeeR is stunning !!

badtrip

hello



this is my stats...


I using a   P3 600Mhz
                                    250Mb pc133

------------------------------------------------------------ 
Current stats: 
------------------------------------------------------------ 
Version: PtokaX DC Hub 0.3.3.21 [debug] built on Aug  1 2005 04:03:42 
Uptime: 0 days, 0 hours, 5 minutes 
Users (Max/Actual Peak (Max Peak)/Logged) : 120 / 31 (66) / 31 
Chat messages: 2 x 
Unknown commands: 0 x 
PM commands: 0 x 
Key commands: 50 x 
Supports commands: 43 x 
MyINFO commands: 63 x 
ValidateNick commands: 49 x 
GetINFO commands: 0 x 
Password commands: 12 x 
Version commands: 48 x 
UserIP commands: 105 x 
GetNickList commands: 48 x 
Search commands: 7 x 
SR commands: 0 x 
CTM commands: 101 x 
RevCTM commands: 36 x 
BotINFO commands: 0 x 
------------------------------------------------------------ 
CPU usage (60 sec avg): 1.92% 
CPU time: 2:06:32 
Mem usage (Old style): 1933 kB 
Mem usage (Peak): 5.62 MB (10.00 MB) 
VM size (Peak): 7.61 MB (8.10 MB) 
------------------------------------------------------------ 
SendRests (Peak): 0 (0) 
RecvRests (Peak): 0 (0) 
Data sent: 328.76 kB 
Data received: 22.33 kB 
Tx (60 sec avg): 94 B/s (187 B/s) 
Rx (60 sec avg): 94 B/s (52 B/s)

gander

heres mine...

got a p3 800mhz


------------------------------------------------------------
Current stats:
------------------------------------------------------------
Version: PtokaX DC Hub 0.3.3.21 [debug] built on Aug  1 2005 04:03:42
Uptime: 0 days, 11 hours, 31 minutes
Users (Max/Actual Peak (Max Peak)/Logged) : 400 / 251 (519) / 251
Chat messages: 3537 x
Unknown commands: 1 x
PM commands: 7 x
Key commands: 2529 x
Supports commands: 2425 x
MyINFO commands: 8324 x
ValidateNick commands: 2461 x
GetINFO commands: 0 x
Password commands: 58 x
Version commands: 1852 x
UserIP commands: 1363 x
GetNickList commands: 1799 x
Search commands: 12468 x
SR commands: 17257 x
CTM commands: 48740 x
RevCTM commands: 38688 x
BotINFO commands: 4 x
------------------------------------------------------------
CPU usage (60 sec avg): 0.75%
CPU time: 0:05:09
Mem usage (Old style): 2148 kB
Mem usage (Peak): 12.45 MB (15.20 MB)
VM size (Peak): 11.59 MB (15.06 MB)
------------------------------------------------------------
SendRests (Peak): 0 (4)
RecvRests (Peak): 0 (1)
Data sent: 229.81 MB
Data received: 153.98 kB
Tx (60 sec avg): 117 B/s (5.30 kB/s)
Rx (60 sec avg): 158 B/s (161 B/s)

witch

Hola guys!

i run 0.3.3.21.nt.dbg powered by RC10.01e, but damn where is Op-Chat gone. is it a BUG or it's just me.

thx in advince  :D



Psycho_Chihuahua

Here a Giant Hub  :D

running on a AMD 2500+ with 1Gb Ram

[23:28:37] <-SanitariuM->
------------------------------------------------------------
Current stats:
------------------------------------------------------------
Version: PtokaX DC Hub 0.3.3.21c [debug] built on Aug 19 2005 07:09:19
Uptime: 0 days, 22 hours, 58 minutes
Users (Max/Actual Peak (Max Peak)/Logged) : 150 / 5 (6) / 2
Chat messages: 242 x
Unknown commands: 0 x
PM commands: 3 x
Key commands: 640 x
Supports commands: 646 x
MyINFO commands: 681 x
ValidateNick commands: 642 x
GetINFO commands: 0 x
Password commands: 21 x
Version commands: 635 x
UserIP commands: 9 x
GetNickList commands: 617 x
Search commands: 204 x
SR commands: 0 x
CTM commands: 5 x
RevCTM commands: 3 x
BotINFO commands: 6 x
------------------------------------------------------------
CPU usage (60 sec avg): 0.00%
CPU time: 0:00:24
Mem usage (Old style): 1886 kB
Mem usage (Peak): 3.64 MB (10.12 MB)
VM size (Peak): 6.55 MB (7.95 MB)
------------------------------------------------------------
SendRests (Peak): 0 (0)
RecvRests (Peak): 0 (1)
Data sent: 698.00 kB
Data received: 216.50 kB
Tx (60 sec avg): 0 B/s (12 B/s)
Rx (60 sec avg): 0 B/s (0 B/s)

Scripts:
AsyncWhois
hostname
ResolveIP
Triggerbot
IPLog
Callscript
Lawmaker
D2Af
PtokaxWiki ?PtokaX Mirror + latest Libs

01100001011011000111001101101111001000000110101101101110011011110111011101101110001000000110000101110011001000000101010001101111011010110110111101101100011011110111001101101000

uffetjur

#69
one of five hubs running on same machine:


p3, 560Mhz, 1024 MB Ram:

------------------------------------------------------------
Current stats:
------------------------------------------------------------
Version: PtokaX DC Hub 0.3.3.21 [debug] built on Aug  1 2005 04:03:42
Uptime: 3 days, 23 hours, 36 minutes
Users (Max/Actual Peak (Max Peak)/Logged) : 1000 / 378 (389) / 320
Chat messages: 1643 x
Unknown commands: 0 x
PM commands: 2776 x
Key commands: 7824 x
Supports commands: 7679 x
MyINFO commands: 16231 x
ValidateNick commands: 7889 x
GetINFO commands: 0 x
Password commands: 6221 x
Version commands: 5958 x
UserIP commands: 13998 x
GetNickList commands: 5989 x
Search commands: 485937 x
SR commands: 325614 x
CTM commands: 21687877 x
RevCTM commands: 3948110 x
BotINFO commands: 28 x
------------------------------------------------------------
CPU usage (60 sec avg): 1.47%
CPU time: 2:02:24
Mem usage (Old style): 2408 kB
Mem usage (Peak): 12.25 MB (29.79 MB)
VM size (Peak): 12.14 MB (30.79 MB)
------------------------------------------------------------
SendRests (Peak): 1 (4)
RecvRests (Peak): 0 (3)
Data sent: 13.47 GB
Data received: 1.42 GB
Tx (60 sec avg): 28.69 kB/s (37.70 kB/s)
Rx (60 sec avg): 4.23 kB/s (4.12 kB/s)
Somewhere in Cyberspace

PPK

QuoteOriginally posted by witch
is it a BUG or it's just me.
No is not bug, check profilemanager and enable opchat for profiles where you want to have it  :]
"Most of you are familiar with the virtues of a programmer. There are three, of course: laziness, impatience, and hubris." - Larry Wall

blackwings

#71
why is the option to choose what action that should be taken,
when a person hammer the hub removed from deflood in 0.3.3.21??


witch

QuoteOriginally posted by PPK
QuoteOriginally posted by witch
is it a BUG or it's just me.
No is not bug, check profilemanager and enable opchat for profiles where you want to have it  :]
damn me blind lol, just not to used to see op-chat anble box on profile manager...hehe

thx a lot dude  :D



witch

in  0.3.3.21.nt.dbg what exactly function "New Conections from same Ip" do? and what the meaning of 2 numeric boxes?

thx in advince  :P



blackwings

QuoteOriginally posted by witch
in  0.3.3.21.nt.dbg what exactly function "New Conections from same Ip" do? and what the meaning of 2 numeric boxes?

thx in advince  :P
for example, if you have 7/10 in New Conections from same Ip, then if a user from the same ip tries to connect more that 7 times to the hub in less then 10 seconds, then deflood with ban it or whatever. This function was it I talked about in mine post above.


SMF spam blocked by CleanTalk