Witam. Który mam profil wybrać by ograniczyć pasmo na dany adres ip mianowicie po adresie ip.
hfsc_lite.qos:
This 3-Band HFSC configuration is intended for consumer router as WAN gateway to cable or other broadband conneciton. HTB eats consumer router's CPU for breakfast past 50 Mbit. This uses HFSC, your QDISC, and extremely simplistic protocol filtering. The configuration is not the "academic ideal," but should allow close to 100/10, and do well to keep all services balanced. (IPV6+IPV4)
hfsc_litest.qos:
This single band HFSC configuration is intended for consumer router as WAN gateway to cable or other broadband conneciton. HTB eats consumer router's CPU for breakfast past 50 Mbit. Try a bare minimum QOS with HFSC and your QDISC to get full bandwidth and decent bloat reduction. FQ_CODEL effectively make sparse data priority, so this could be great QOS for a few users in the residence. (IPV6+IPV4)
layer_cake.qos:
This uses the cake qdisc as a replacement for htb as shaper and fq_codel as leaf qdisc. This exercises cake's diffserv profile(s) as different "layers" of priority. This script requires that cake is selected as qdisc. See: http://www.bufferbloat.net/projects/codel/wiki/Cake for more information
nxt_routed_hfsc.qos:
Uses a combination of HFSC and FLOW classifier to prioritize typical interactive protocols. This script is specially designed for clients behind NAT.
piece_of_cake.qos:
This just uses the cake qdisc as a replacement for htb as shaper and fq_codel as leaf qdisc. It just does not come any simpler than this, in other words it truely is a "piece of cake". This script requires that cake is selected as qdisc. See: http://www.bufferbloat.net/projects/codel/wiki/Cake for more information
simple.qos:
BW-limited three-tier prioritisation scheme with fq_codel on each queue. (default)
simplest.qos:
Simplest possible configuration: HTB rate limiter with your qdisc attached.