Classify long-lived streams with tc or iptables? (traffic shaping under Linux)
I am hoping to detect TCP streams which have been running for more than one minute (or for longer than N bytes, or longer than M packets), so I can classify them as bulk traffic ("downloads") and de-prioritise them.
How can I detect long-running streams with tc or mark them with iptables fwmark?
For example the TCP "sequence number" gets very large, but I don't know how to find this for masking in tc, and also masking doesn't seem applicable to detect large numbers, only small numbers. (Unless we do one mask for every high bit!)
(For intermittent interactive streams, such as ssh, which sometimes flood and sometimes fall silent, I plan to continue classifying them according to their TOS field or port number.)
I am hoping to detect TCP streams which have been running for more than one minute (or for longer than N bytes, or longer than M packets), so I can classify them as bulk traffic ("downloads") and de-prioritise them.
How can I detect long-running streams with tc or mark them with iptables fwmark?
For example the TCP "sequence number" gets very large, but I don't know how to find this for masking in tc, and also masking doesn't seem applicable to detect large numbers, only small numbers. (Unless we do one mask for every high bit!)
(For intermittent interactive streams, such as ssh, which sometimes flood and sometimes fall silent, I plan to continue classifying them according to their TOS field or port number.)
No comments:
Post a Comment