Gargoyle Forum

Coming from a mikrotik background i can tel you why this works so well. Time critical tcp ack packets are around 80 bytes in length, then you have other ack packets slightly larger also included in the 400 bytes. Then you have most dns requsts and replys taht also fit here and dont forget sin packets, some voip and icmp packets. They all weigh in at under 400 bytes with the exception of dns and voip which might have some packets over this size. Anything heavy is usually close to 1500bytes but its the ack priority that makes tcp streams work well under load. I set mine to 512 bytes to make sure i catch most dns packets and slightly improve voip.

Thank you for the explanation

nworbnhoj wrote:That would be a great trick to publish as a wiki gargoyle_tip (nudge nudge) http://www.gargoyle-router.com/wiki/dok ... goyle_tips

Yes, it would, but it never made it.

@shm0, would you mind posting a screenshot of your QoS implementing dumas777's solution? A picture is worth a lot for this sort of thing. I don't think dumas777 has been here in a while, so he's not apt to see this.

For now, this is what I'm thinking. This is just the one for DL, as the UL one is the same except for total bandwidth.

Packet threshold is 512 bytes instead of 400, per the earlier post.

http://imgur.com/FqFALyL



edit:ispy