hey guys how you doing, hope you all okay
just wonder how i can set max speed 50kb per client while update?
just wonder how i can set max speed 50kb per client while update?
limit update's max speed!!
10/22/2015 21:39
SnapPop#1
10/22/2015 23:23
Hynix1337#2
You can limit the user at download manager just change USER_LIMIT "1" or setup a virtual machine with your server files and limiting the virtual networkcard of the vm there ;)Quote:
hey guys how you doing, hope you all okay
just wonder how i can set max speed 50kb per client while update?
10/23/2015 03:52
SnapPop#3
setting USER_LIMIT "1" wont solve it while even just 1 player can use the maximum upload speed of the server
any more ideas ?
any more ideas ?
10/23/2015 13:27
Anonymous-6723#4
Neither his second solution will, you will limit the machine's speed to 1000kb/s for example.. First user takes 200, third 600, 4th and 5th 100.. and then what?
Probably the way is trough server.cfg if it has such param. I couldn;t find myself one :)
Probably the way is trough server.cfg if it has such param. I couldn;t find myself one :)
10/23/2015 13:39
Exo#5
Probably you will have to make your own download server xD
Drew had theory and a cpp example maybe you want to check'em out.
Drew had theory and a cpp example maybe you want to check'em out.
10/23/2015 15:21
SnapPop#6
you mean these paramsQuote:
Code:
MaxConnectionsPerServer "5000" MaxConnectionsPer1_OServer "5000"
you mean creating custom library/addon for DownloadServer which can limit the connection speed per ip ?Quote:
Drew had theory and a cpp example maybe you want to check'em out.
there's no other way?
10/23/2015 15:55
Timlock#7
The only way to do this would be with a filter....
and in the filter you would have to limit the number of bytes that can be processed per interval from server -> client.
a basic filter will use 4096 - 8192 bytes per interval, but using async socket handlers you can send that every 1ms. which will allow 4mb-10mb per second per connection.
The solution would be to allow only 6-12 intervals to occur every second, which would slow your connection to 40-60 kbps.
and in the filter you would have to limit the number of bytes that can be processed per interval from server -> client.
a basic filter will use 4096 - 8192 bytes per interval, but using async socket handlers you can send that every 1ms. which will allow 4mb-10mb per second per connection.
The solution would be to allow only 6-12 intervals to occur every second, which would slow your connection to 40-60 kbps.
10/23/2015 16:12
Anonymous-6723#8
@Timlock's explanation is good enough!
I tried to find rest of the params, but I couldn't find anything else. And yes I do mean the same param you showed above, but they are not the proper ones.
Edit:
That's just a theory which I did not test.
[Only registered and activated users can see links. Click Here To Register...]
Try using these lines as server.cfg params, for example try the last one.
Restart download server and then try to shut it down, if you get a msg box saying do you really want to close the DownloadServer or something like that, try the rest of the params from the picture, it might work. Needs testing :)
I tried to find rest of the params, but I couldn't find anything else. And yes I do mean the same param you showed above, but they are not the proper ones.
Edit:
That's just a theory which I did not test.
[Only registered and activated users can see links. Click Here To Register...]
Try using these lines as server.cfg params, for example try the last one.
Code:
PromptAtClose 1
10/23/2015 16:42
Exo#9
It works.Quote:
I tried to find rest of the params, but I couldn't find anything else. And yes I do mean the same param you showed above, but they are not the proper ones.
Edit:
That's just a theory which I did not test.
[Only registered and activated users can see links. Click Here To Register...]
Try using these lines as server.cfg params, for example try the last one.
Restart download server and then try to shut it down, if you get a msg box saying do you really want to close the DownloadServer or something like that, try the rest of the params from the picture, it might work. Needs testing :)Code:PromptAtClose 1
10/23/2015 20:22
SnapPop#10
humm, do you know an existing filter or you mean code mine ?Quote:
well my skills at c# is still low but your idea can be taken from Chernobyl's srprot it's just need some re code as it has a penalty: if the client exceeded the max allowed bytes the connection get terminated
yeah saw that param (MaxSendQueDepth) too but didn't consider that it's related, so i didn't test itQuote:
[Only registered and activated users can see links. Click Here To Register...]
Try using these lines as server.cfg params, for example try the last one.
Code:PromptAtClose 1
which one ? MaxSendQueDepth ?Quote:
10/24/2015 16:50
Timlock#11
PromptAtClose 1 worked, i cant easily test if any others are working, but ill try.
10/24/2015 17:53
Anonymous-6723#12
Well try these ones if you can figure out what they doing, if they work I and someone write it here or PMs me, I will try to dig all of them for all of the modules :)
10/25/2015 17:08
Goofie#13
There is a program out there, where you can set upload speed etc. Just get a better net.
#Best solution 2k15
#Best solution 2k15
10/25/2015 19:33
Anonymous-6723#14
On specific *.exe files you mean or overall?
10/25/2015 23:05
SnapPop#15
@Timlock, @Zed , really sorry guys can't test that param at the moment as my own net is crap and for testing the dedicated's upload speed, it wont be accurate
so can you guys test and confirm ?
@Goofie which program you refer to ? and what do you mean by 2k15 (think i don't get that part) ?
@thread when i posted this thread asking for help i thought you guys already have solution used on your own servers
updates which containing sro_client on servers with a lot of users while leaving the maximum upload speed as it is, is sounds like a shell or a natural built-in ddos xD
my ex-dedicated server had 6~7mb/s upload speed and was lagging as hell if just 1 user can update his client with his 7+mb/s download speed
like i just said it's almost built-in ddos
if there's no existing solution so let's do it as we always did
P.S: ksro already using such technique , when i try to update ksro client the maximum download speed doesn't exceed 35kb/s
so can you guys test and confirm ?
@Goofie which program you refer to ? and what do you mean by 2k15 (think i don't get that part) ?
@thread when i posted this thread asking for help i thought you guys already have solution used on your own servers
updates which containing sro_client on servers with a lot of users while leaving the maximum upload speed as it is, is sounds like a shell or a natural built-in ddos xD
my ex-dedicated server had 6~7mb/s upload speed and was lagging as hell if just 1 user can update his client with his 7+mb/s download speed
like i just said it's almost built-in ddos
if there's no existing solution so let's do it as we always did
P.S: ksro already using such technique , when i try to update ksro client the maximum download speed doesn't exceed 35kb/s