Hi all
Whats the difference between the following optcions in:
BANDWITH CONTROL--->RULES-->
control max tcp windows
apply induced traffic
apply to traffic to/from the local machine
rule bidireccional
BANDWITH CONTROL--->RESTRICTIONS-->
priority leve 1, 2,...5
kilobis and porcentage available, this both options not working at the same time in two different rules. why?
Danke
bandwith control options
Moderator: Qbik Staff
3 posts
• Page 1 of 1
bandwith control options
by kantoborgy » Jul 16 05 9:33 am
- kantoborgy
- Posts: 17
- Joined: Jul 15 05 11:38 am
by genie » Jul 16 05 4:47 pm
Hi,
1. Control max TCP window is used for TCP traffic only and is applied when the driver recognises that the client cannot send/receive more than X bytes - it then sets TCP Max window to be less or equal to X.
2. Some protocols create secondary connections (like, FTP for example - contorl channel is a primary one, while data channel is a secondary one). If you want to apply the same rule for all connections spawned from the primary one you tick this checkbox.
3. Either the rule should be applied to the traffic originated/destined to the local machine - Wingate proxies, for example, while working on behalf of the client initiate traffic from the Wingate machine itself.
4. Bi-directional rule is required when you don't care where the traffic goes from source IP to destination IP or backwards.
5. Priority level controls the order how the packets are being fed down the wire - higher priority traffic is to be sent first.
6. Kbits restriction sets the hard limit - no more than X kbits. percentage means that the traffic controled by this rule can use up to X percent of the _available_ bandwidth regardless of the actual Kbit value of available bandwidth.
1. Control max TCP window is used for TCP traffic only and is applied when the driver recognises that the client cannot send/receive more than X bytes - it then sets TCP Max window to be less or equal to X.
2. Some protocols create secondary connections (like, FTP for example - contorl channel is a primary one, while data channel is a secondary one). If you want to apply the same rule for all connections spawned from the primary one you tick this checkbox.
3. Either the rule should be applied to the traffic originated/destined to the local machine - Wingate proxies, for example, while working on behalf of the client initiate traffic from the Wingate machine itself.
4. Bi-directional rule is required when you don't care where the traffic goes from source IP to destination IP or backwards.
5. Priority level controls the order how the packets are being fed down the wire - higher priority traffic is to be sent first.
6. Kbits restriction sets the hard limit - no more than X kbits. percentage means that the traffic controled by this rule can use up to X percent of the _available_ bandwidth regardless of the actual Kbit value of available bandwidth.
- genie
- Qbik Staff
- Posts: 1788
- Joined: Sep 30 03 10:29 am
3 posts
• Page 1 of 1
Who is online
Users browsing this forum: No registered users and 3 guests