moro666 wrote:What is better, using weighting or using Periority to classify the connection ?
first i use weiting method, yes it do it's job, But it was hard to determain its' value on each rule, u need to do it exactly
But when I use Periority Method, it was easy to set it, & I think it was more useful for every rule.
whith it i have full line utilization, important connection have its' need, limiting less important ones,
& when it closed, non-important connections began to gain un-used bandwidth.
- when a rule limiting a not important connection/clinet , whith low periority, like 1 or 2, u shoud give this rule a low guarantied speed, as 5 kbyte/s
if you don't so, when important connection/client starts to connect, & eat more bandwidth, & the line reach to it's MAX
the low periorty rules will limite speeds almost near zero kb/s & may drop this client totaly & stop his traffic, tell the important rule ends it's job.
you only who can know what speed is needed for every client , & what ur max line speed can handle ?
I am under the impression that guaranteed speeds take precedence over priority levels. So that even if a traffic stream is classified with a priority level of 1 and a guaranteed speed of 5 K/s, it will be given 5 K/s no matter what happens. Let me know if you can set up a simple test that shows otherwise and I will try to reproduce it.
Prioritization is used to give full speed to a user (or protocol). It's real-world usage is to prevent an application from being swamped by other network traffic like file sharing. Prioritization is commonly used by applications such as VoIP and online games.
moro666 wrote:I use latest version now, & before we start these discussion, i was uing v2.00 .
& yes I knew [Weighting] is changed to [Scalefactor] , but it presented in main program interface as [Weighting Ratio]
give a look to my Bandwidth C., is there anything wrong with it ? [Open this pic. in a new page, it's croped Here!]
-My LAN range = 10.0.42.0/255
- My WAN IP = 22.214.171.124
- My Server Nme= SPEED
[[ every connection opend by a client , appear at traffic monitor as a connection through LAN
& the same connection passing throgh WAN, But my server is the local endpoint
is this mean , i have to limit this connection with 2 rules, 1 for LAN, & other for WAN ?
... I just want to know about giving a guarantied speed to these Low priority rules is OK ?
Or this may waste bandwidth ?
I want to limit a heavy downloader user at beaktimes, but not kill his connections, that's why i gave him low periority , & small amount of guaranted speed.
1- Prioritization is commonly used by applications ------ I use it to prioritize some group of clients, is this ok?
2- to prioritize an application, Like Yahoo messenger Voice & CAM, can this rule work :
* Adapter = LAN
* direction = Both
* SPEED = unlimited
* Piriority = 8 or 9
* Local Point = ANY - with Port= ANY
* Remote Point= ANY - with Port= 5100 [or any ports used By that application]
* Protocol = TCP or UDP [ debending on that Ap.]
this will make action on LAN side, Not WAN side,
SO.. do i have to make the same rule again but Adapter 'll be WAN ??
The 'adapter' setting in rule properties is only for classification, it doesn't affect processing
moro666 wrote:The MAX download speed for 512 ADSL line is 55 - 65 Kbyte/s <---- [& this what I put in Internet Line speed sitting]
but it may reduced during a day , Beak times.. it can reach 30 k/s or even 25 k/s MAX
If it can't handle it.. I'm thinking of Crazy idea [[ dynamic detection of internet speed ]]
The best way is to perform a bandwidth test to a web server every 10 minutes or so but it puts a lot of strain on the local internet connection. It would block all clients for 10 or 20 seconds because it needs to test the full width of the line.
Users browsing this forum: No registered users and 1 guest