bandwidth controll setup encountered BlueScreen

[takusa100]

Maybe cuz i created too much rules,when i pressed the "Apply" button ,system turned into BlueScreen :"Kernel stack size less than 0x500 bytes" . i think it's WG's problem ,it's foreign to the Hardware or Os, because i tested it at least 2 machines, the results were same.

Can increase this "Stack Size" to support more rules ?


regards,
takusa

[genie]

Hmmm..... How many rules are there?

[genie]

I have the fixed driver here - can send it to you for testing if you let me know what OS you are using.

[takusa100]

hi genie:
thanx for your help.

oh,i'm using win2003 Stardard version, and i created almost 300 rules ...

now i don't test them yet ,i think it will consume too much cpu's usages,so there are some settings to reduce it a bit ?

the machine's memory is larger(768M),so Can i increase the packet cache to 200 or more in the "Priority" Tab ? will it be useful about it ?

i'm very interesting to use your great drivers, and my email is Rich.Olive at gmail dot com.
thanx for that .

regards,
takusa

[genie]

Nope - gmail does not accept it - do you have other email addresses?

[takusa100]

takusa at 126.com :)

[genie]

Well, looks like it accepted it - at least no complains so far :)

[takusa100]

hi great genie:
thanx for your wonderful gift! At least now it works stably with more than 300 rules.

i observed the traffic for a while, i noticed the WG's Bandwidth control works well specially with a burst traffic,like open html; IM software,but when i test a continued stream traffic ,especially some application which need real-time, like some network games:WoW World ;counter-strike,the latency is not stable,often appeared paused status.
are there any configurations to slove this situation ?
thanx again.

regards,
takusa

[genie]

Hey, good news!

Well, as a matter of fact there is (or are, rather:)

1. for TCP-based rules check the checknox "Control max TCP window" - it will reduce TCP window size in line with the unused amount of bandwidth
2. Make rules unbalanced - for example, traffic, leaving your network might have higher priority or bandwidth than incoming traffic or vice versa.
3. Increase packets life span - make it 5 sec or 10 sec (you have to experiement)
4. Change averaging window size - make it 5 sec (which allows longer bursts).

[takusa100]

genie,thanx for all your experiences,i'll test them one by one.

but excuse for my poor english,i can't understand below completely.

2. Make rules unbalanced - for example, traffic, leaving your network might have higher priority or bandwidth than incoming traffic or vice versa.

i think i can know the "unbalanced" concept that you said,just like ADSL: upload speed or priority is not same as download. is it ?
but how can i implement this in WG? Just create 2 rules for every ip ,one is outbound with low priority and low bandwidth;another is inbound with higher one, and uncheck "bi-direction" item ? is that right ?
i noticed that at the tail of every rules had a column"Rev Restriction" and the value of every row is same :"<balanced>"
this value is that you said ? it look like nowhere can modify this value .

i'm a rookie, hehe ,so problem is too much :)

regards
takusa

[genie]

Aye, unbalancing a rule requires two restrictions - on the first rule screen there is an option to set the second restriction.