crazybyte

In my case shaping my upstream bandwidth makes sense. I want to keep seeding many torrents, to avoid they will die, and I want to do it using as much bandwidth as possible. But, at the same time I don't want to slow down my home network. Hence, it would be great if my pfSense instance manages it on my behalf, guaranteeing the seedbox the bandwidth when is not used by any other devices. Anyway, I believe there could be many other good reasons to do that.

Hi DZMM, first of all, I want to thank you for having shared your experience. I started to study HFSC yesterday and I have zero experience in traffic shaping. I read the blog article you linked on your first post and I found it really interesting. I still have many questions about this topic, and the tests I've done until now were unsuccessful. But I will continue to study and practice. That said, I have a couple of easy questions to submit to you. These are not related to my personal configuration, I will solve them by myself. You previously said: But from the official documentation I can see Why have you enabled the Quick flag? My second question is related to your solution about tagging traffic from the VLAN's specific rules and then process it from the floating rules. I like your idea, while I was checking on my pfSense instance I realized which below the Tag field, there is the Ackqueue/Queue one. I'm wondering why haven't you used directly this instead of creating an additional floating rule? Would it behave the same?