Bandwidth Throttling

[asianman]

Bandwidth Throttling doesnt seem to work for me!
I have it set by IP address on source, but it seems to take effect for ALL users regardless of IP address set..

eg:

172.31.100.1
255.255.0.0
Restriction: 1024kbps
Source
Priority: Level 1

Not only restricts user 172.31.100.1, but restricts everyone else..
What's happened and how can I fix?

[genie]

Sure - because the mask you use filters out all 172.31 subnet - for bandwidth throttling mask is not the network mask but rather a filter to point out which part of the IP address should be used for decision making. If you want to filter out only one particular IP address, you have to use mask 255.255.255.255.

[asianman]

Oh of courrrsseee!!! Basic networking lol THANKS!

[genie]

No worries - as a matter of fact we figured out that this approach might be quite confusing (subnet mask vs. filtering) - we will probably (subject to user comments and usability study) change it to the IP range configuration.

[asianman]

Well now I know what it was, it makes things a whole lot easier to understand and it seems to be working well!

[asianman]

Now I've got the download bandwidth throttling working, how do I do upload throttling? Implementing a reverse restriction doesnt seem to work - the download speed seems to be restricted to what I set as reverse restricted

[genie]

If you want to apply reverse restriction, you have to mark rule as bi-directional - so that it will "see" packets coming back. Otherwise, you can create separate rule and set the destination IP to be the one you want to throttle.

[asianman]

Well I tried both methods, neither seemed to throttle the upload...
download throttling works ok:

Source IP: 172.31.100.1
Mask: 255.255.255.255
Restriction: 1024kbps
Level 1
= OK

Destination IP: 172.31.100.1
Mask: 255.255.255.255
Restriction: 128kbps
Level 1
= NO THROTTLING

??

[genie]

Erm... I am lost - .1 client uploads data to some host - meaning that the data traffic would be originated from .1 - right?

[asianman]

I'm sorry I'm lost too lol...

I have two seperate rules

RULE 1: Soure Throttling of 1Mbps = Works OK
RULE 2 Destination Throttling of 128kbps = No Throttling!

Rules are the same with the exception of Source/Destination

[genie]

Ok - are these rules marked as bidirectional?

[asianman]

No theyre not... Should they be? Download one is working without it switched to bidirectional

[genie]

Aye - because if the rule is unidirectional, thorttling through it would depend on the direction of the "heavy" data packets.

[asianman]

Hmm ok heres how I am testing

I have a 3.5Mbps downstream connection and a 512kbps upstream connection on ADSL...

I have the downstream throttle of 2Mbps working ok with the following setting:

Source IP: 172.31.100.1
Mask: 255.255.255.255
UNIDIRECTIONAL

nzdsl speed test shows 2Mbps as it should

---

Now if I try applying the same principle to the upstream throttle:

Destination IP: 172.31.100.1
Mask: 255.255.255.255
UNIDIRECTIONAL

nzdsl speed test shows 512kbps which is full speed...

Go figure?

[asianman]

PS - trying to make upstream 128kbps..

[genie]

Right - but what part of traffic is coming from upstream? If the rule is unidirectional and the client sends data _to_ the upstream server, then data packets will trigger the rule and the restriction will be applied - mind you, if the rule is not marked as bidirectional, only one part of the traffic will be throttled - the one that comes to the direction set by the rule.

[asianman]

Ok, but if I make ONE rule like this

BIDIRECTIONAL
Source: 172.31.100.1
Mask: 255.255.255.255
Apply Restriction: 2Mbps
Reverse: 128kbps

and then run a speed test, it will show the downstream speed of 128kbps and the upstream speed will still be 512kbps..

[genie]

How do you test it?

[asianman]

www.nzdsl.co.nz - speed test shows downstream and upstream speed

[genie]

How does it test upstream performance? I will try it tomorrow but if it simply calculates the rate of ACK packets coming back from the client - it is not enough. Try uploading some big file.

[asianman]

Still no go - tried uploading big file and transfer rate stayed the same. So somethings not configured right..

[asianman]

Should I be playing with "control max tcp window" "apply to induced traffic" "apply to traffic to from local machine" settings?

[genie]

I'll do the testing tomorrow - meanwhile, can you export and email your Wingate settings to me?

[genie]

Now, if you tried FTP traffic, then "apply to induced" should be ticked - otherwise FTP data channel will not be throttled. TCP window control helps to "flatten" data throttling, creating less spikes on the way.

[asianman]

Have emailed you settings - "control max tcp window" seems to screw it all up in regards to testing, puts my downstream speed to 100kbps lol

[genie]

:))) See - it works even better after all :) Seriously, though - this is why this settings is configurable - because this is the only way to reduce upstream traffic flow (from upstream I mean).

[asianman]

Oh well guess I'll just have to live with downstream throttle only! :'(

[genie]

Well, we'll see how your configuration looks like.

[asianman]

anything interesting?

[genie]

One quick question - I noticed you had WWW intercept activated in your configuration - did you have the rules marked as "Apply to local connection" as well?