4 ms·
Is it overly pedantic for me to say QoS has nothing to do with inbound traffic or is that an older, say, traditional definition? My understanding is one can on
by throw7 11y ago
Is it overly pedantic for me to say QoS has nothing to do with inbound traffic or is that an older, say, traditional definition?
My understanding is one can only "shape" outbound traffic. You are under no control at all of the incoming packets.
- ktsaou 11y agoLinux kernel magic. It is called IFB. Check this explanation at the FireQOS tutorial: https://github.com/firehol/firehol/wiki/FireQOS-Tutorial#controlling-incoming-traffic https://github.com/firehol/firehol/wiki/FireQOS-Tutorial#con...
- brbsix 11y agoYou can install an ingress queue and apply a filter to inbound traffic. There are few other more arcane techniques but you're right that control is quite limited. Here's an example for something I was working on yesterday (traffic policing to simulate slow download): sudo tc qdisc add dev eth0 handle ffff: ingress sudo tc filter add dev etch0 parent ffff: protocol ip prio 50 u32 match ip src 0.0.0.0/0 police rate 30kbit burst 3k drop flowid :1 Here's an example of using IFB to shape incoming traffic (what the OP was referencing): http://serverfault.com/a/386791/301799 http://serverfault.com/a/386791/301799
- wtallis 11y agoIt's definitely an outdated definition that comes from the mindset that QoS means shaping traffic according to what protocol it uses. That's far too narrow a meaning, and the technique of explicitly classifying traffic is mostly obsolete given the availability of AQMs and FQ that need little or no configuration.