Bandwidth throttaling question

[HiLinks]

hi
1- i want to know that what does the meaning of following options in rules configaration of bandwidth throttaling?
(a) Control max TCP windows
(b) Apply to Induced traffic
2- if i limit bandwidth of any of my client to 64 kbps, does it also limit the transfer rate of cached objects and the shared files?
please explain me in details , i will be highly thankfull !
Best Regards

[genie]

Hi,

1. Control MAX TCP window means that when the requested window size in TCP connection is bigger than the remaining traffic limit for the current time slot Wingate would lower TCP window size to make it no bigger than the remaining limit of the traffic.
Induced traffic is the one that an application protocol generates. For example, FTP protocol uses two channels - control channel (port 21 by default) and data chanel which can use dynamically allocated port numbers. If "Induced" checkbox is ticked, then this secondary traffic will be controled by the same throttling rule.
2. It depends. If your rule filter uses an internal address of the client then yes, it will be throttled.

[HiLinks]

HI
Thanks for your reply, kindly explain a few more things,

2. It depends. If your rule filter uses an internal address of the client then yes, it will be throttled

i have created a restriction having priority level 3 and speed limit to 64 k bits, and a rule with

(a) Protocol = all
(b) control max tcp windows = not checked
(c) apply to induced traffic = checked
(d) apply to traffic to/from local mechine = checked
(e) apply restriction = 64 k bits
(f) allow different restrictions to be applied to reserve trafic = not checked
(g) rule is bi-directional = checked
(h) surce ip = 192.168.0.2
(i) surce mask = 255.255.255.255
(j) any port = checked
(k) destination ip = 0.0.0.0.
(l) destination mask = 255.255.255.255
(m) any port = checked


now tell me
(1) is this rule also limit the transfer rate of cached objects and shared files?
(2) as i have restricted the client pc 192.168.0.2 to 64 k bits, please tell me is this rule reserve 64 k bits bandwidth only for this client , or when this client is not useing full 64 k bits, other clients can use the remaining bandwidth? in other words, does this rules only set the max limit of bandwidth for that client or dedicate the configured bandwidth only for that client?

[genie]

Yes, the rule should restrict all client's activity since it is checked as bi-direct. However, the destination mask should be 0.0.0.0 - otherwise the rule will not notice any traffic at all.

[HiLinks]

Hi
thanks for ur reply again, but, sory to say, its not the enough answer of my questions, u people alwayz answer only in few words, its not neccesaray that every one have same skills like u people to understand each n every thing in few words, please answer my question in details, step by step, i will be very thankfull, sory again if i hurt u, but really its a fact that when ever i asked any thing in this form, no one reply me in detail so i can understand better, and the same problem with ur software :wingate: help files, there are also just only the overview of its features, not the detailed help. its really a gud software but its support is its only week point.
Regards

[HiLinks]

so u mean to say that the above mentioned rule also restrict the transfer rate of cached objects and shared files? and wut about my second question

(2) as i have restricted the client pc 192.168.0.2 to 64 k bits, please tell me is this rule reserve 64 k bits bandwidth only for this client , or when this client is not useing full 64 k bits, other clients can use the remaining bandwidth? in other words, does this rules only set the max limit of bandwidth for that client or dedicate the configured bandwidth only for that client?

[genie]

Yes, because it will still be a transfer to 192.168.0.2

[genie]

However, you can untick checkbox marked "Apply to local traffic" and it will no restrict this local transfer then.

[HiLinks]

Yes, because it will still be a transfer to 192.168.0.2

it means that however 192.168.0.2 is online or offline, or useinf full 64 k bits or useing only 20-25 k bits, the 64 k bits bandwidth of my total bandwidte that is 256 k bits is reserved for 192.168.0.2, and all other clients can use only 192 k bits bandwidth?

i have 10 clients 192.168.0.2 to 192.168.0.11 and have total bandwidth 256 k bits, and my problem is that if any of that clients start downloading, it sucks almost all bandwidth and other clients have very slow transfer rate mean while, i just want to make such setting that all clients shares all bandwidth but no one can download more than 64 k bits so that other clients can have sufficent bandwidth

so please explain wut can i do for this/

[genie]

No, it does not reserve the channel - it allows the client to use UP TO 64K of traffic a second.

Does your current rule specify IP 192.168.0.0/255.255.255.0? In that case it covers all your subnet and does not allow more than 256K of traffic to be consumed by all members of this subnet cumulative.

[HiLinks]

oh its okay, i just want this thing that clients can have up to 64 k bits. i dont want to reserve the bandwidth permanently........ its okay, and tell me about cached objects in win gate cache and also tell me about shared files that shared by windows file shareing, will they also be limited to 64 k bits? if i uncheck the to/from local mechine , i think it will also unrestricted clients that uses www proxy server, that i dont want, as i have configured www proxy server to work transparently to intercept requests on port 80. is there any solution for this?

[genie]

Yes. by all means. If you want to leave this wildcard rule in place, you have to create special unrestricted rules also for port 139 and 445 for file sharing and for port 80 - make them unrestricted.