Gargoyle Forum

Hello and thanks in advance for excusing a noob question about Gargoyle firmware. I have just loaded Gargoyle 1.52 on my Netgear WNDR3700 V1 with great success! Wow, what an improvement over the stock firmware!

My primary question at this point pertains to the QoS Classification Rules. I have several connections sharing my 22/2 cable connection mostly ethernet with the exception of my wife's netbook and three android phones. Normally all is well except for when my son is gaming on his PS3 or XBox 360 at this same time as someone else is downloading via bittorrent or normal port 80 downloads. I have configured my total bandwidth up/down according to the instructions provided and am using ACC.

1) My concern is that I am choosing the correct method for sharing of my bandwidth. I have a D-Link DNS-321 NAS that handles my bittorrent downloading, as such I have assigned it a static ip and added an IP based upload/download classification of slow. I believe this to be the best way to limit congestion caused by P2P connections?

2) Next, I would also like to make sure that if I am downloading via JDownloader (port 80) on my PC the connections will be classified as slow. This is where I'm getting a little hung up, I believe there is a way to differentiate between browsing and downloading that might help with this? So far I am seeing all the Jdownloader traffic being classified as NORMAL traffic along with my browsing traffic. (I have not modified the stock classifications with the exception of adding the slow IP based classification for the NAS that handles P2P)

Thanks in advance for any advice you can provide with regards to these two questions.

You should make a special class for the PS3 with minimum bandwidth set to 80kbps. Then assign your PS3 a fixed IP address by entering its MAC address into Gargoyle. Finally a rule to route all PS3 traffic to the new class using the IP. Then while your son is playing observe that 80kbps is enough (or not). I don't know much about PS3 but this is what the XBOX requires, you need to check your situation.

If your torrent package is using port 80 then you will have difficulty differentiating such traffic from your web browser traffic. You might try the "Connection Bytes Reach" feature to throw port 80 connections into your slow class once they reach say 10MB or something. It will take some testing on your part to make sure it works. If you can get your torrent program to use some other ports that would be the best.

Perhaps others have some ideas.

I'll try your idea on the console classification..

As to dealing with the downloader manager traffic, I do not believe I can change the port it uses as it is not a P2P client, but rather a http download manager. I am not completely clear on how to configure the QoS classifcation to try to distinguish the large volume of data it uses versus standard web browsing. Is there a recommended starting point for the size 1MB, 2MB, etc?

Thanks again

I don't have any recommendation for you. Only trial and error will get you an answer. Fortunately its not hard to change.

In terms of the downloading what is your major concern? Ie that the machine in question is stealing all the bandwidth or an application is stealing bandwidth. If it's a machine the way I did it and I think most do is to have each machine as a rule, that way if someone is downloading that is the machine that will then be restricted to the percentage you have allocated. If you set up pbix's excellent acc then your son should be able to game relatively lag free as well.

If it's an application you could see if the downloader can be set for a specific port but not tried application specific restrictions. Generally if say I want to download a large file and game on my pc, I game and then download. Due to setting if someone else on my network is downloading which is usually the case then the acc kicks in and ensures my ping remains stable.

After rereading the post - Presumably if you have http traffic set up as a class (application layer) and then your machine as a different class as a rule below that class then the http download traffic and web traffic fit in the http rule.

If so the only way I can think of is have the downloader use a different port if possible. I think the data sizes you refer to are packet size/packet length which I don't think will show any differently for the two apps

tals wrote:I think the data sizes you refer to are packet size/packet length which I don't think will show any differently for the two apps

Your thinking is incorrect. Connection bytes does not equal packet size.

Connections can be monitored on the connection page.

I think you misread my response. The original poster was asking if he could restrict using download bandwidth and I believe looking at packet size/packet length as one of the classifiers.

The only other one is the application classification which is limited but I did cover in my response.

When I get my Internet back I'll be able to contribute better