Alternate speed limit bug

[Peetboy 0]

Hi, there is bug with alternate speed limiter. The values are switched. For example if you set alternate speed for upload to 1000kB it will set this speed for download and vice versa.

[Lee 84]

Hi, there is bug with alternate speed limiter. The values are switched. For example if you set alternate speed for upload to 1000kB it will set this speed for download and vice versa.

This is fixed in 1.3.1. :D

[Sabotazhnik 0]

limiter's value no longer included in tag ? it prevents hub from kicking users with too low limits, doesn't it ?

[Crise 26]

limiter's value no longer included in tag ? it prevents hub from kicking users with too low limits, doesn't it ?

Read change log for StrongDC 2.40 ^_^

[Big Muscle 1]

limiter's value no longer included in tag ? it prevents hub from kicking users with too low limits, doesn't it ?

Upload limit is included in connection field where it is more logical.

[Sabotazhnik 0]

Upload limit is included in connection field where it is more logical.

logical it is, but it makes preventing users from using too low limits more difficult..

[Big Muscle 1]

No, it doesn't. The only difference is the used field.

[Sabotazhnik 0]

No, it doesn't. The only difference is the used field.

it definately doesn't work on dbhub. yes, it's outdated and no longer supported, but works better than verli with much plugins. well, nevermind.

[Crise 26]

it definately doesn't work on dbhub. yes, it's outdated and no longer supported, but works better than verli with much plugins. well, nevermind.

The use a client to do the job... that can be done easily.

[Big Muscle 1]

If it doesn't work in some hub, it means that such hub isn't properly configured to read connection field. It is hub bug in most cases, because connection field is standard part of protocol command in contrast to tag which is ignored (and not to sent to users) by many hubs.

[Sabotazhnik 0]

The use a client to do the job... that can be done easily.

good idea, thanks :angry: