------------------------------------------------------------ revno: 13115 revision-id: squid3@treenet.co.nz-20140406044159-ncweod3m3pi0bli3 parent: squid3@treenet.co.nz-20140406044108-2yb033l26c4zhoq1 author: Andrew Beverley committer: Amos Jeffries branch nick: 3.4 timestamp: Sat 2014-04-05 22:41:59 -0600 message: Updates to qos_flows documentation Minor updates to the qos_flows documentation based on recent squid-users questions. ------------------------------------------------------------ # Bazaar merge directive format 2 (Bazaar 0.90) # revision_id: squid3@treenet.co.nz-20140406044159-ncweod3m3pi0bli3 # target_branch: http://bzr.squid-cache.org/bzr/squid3/3.4 # testament_sha1: 645cbbe2910a02d89dc8f943d65c394b03dab0dd # timestamp: 2014-04-06 04:43:00 +0000 # source_branch: http://bzr.squid-cache.org/bzr/squid3/3.4 # base_revision_id: squid3@treenet.co.nz-20140406044108-\ # 2yb033l26c4zhoq1 # # Begin patch === modified file 'src/cf.data.pre' --- src/cf.data.pre 2013-12-15 05:06:25 +0000 +++ src/cf.data.pre 2014-04-06 04:41:59 +0000 @@ -2035,10 +2035,19 @@ LOC: Ip::Qos::TheConfig DOC_START Allows you to select a TOS/DSCP value to mark outgoing - connections with, based on where the reply was sourced. For - platforms using netfilter, allows you to set a netfilter mark + connections to the client, based on where the reply was sourced. + For platforms using netfilter, allows you to set a netfilter mark value instead of, or in addition to, a TOS value. + By default this functionality is disabled. To enable it with the default + settings simply use "qos_flows mark" or "qos_flows tos". Default + settings will result in the netfilter mark or TOS value being copied + from the upstream connection to the client. Note that it is the connection + CONNMARK value not the packet MARK value that is copied. + + It is not currently possible to copy the mark or TOS value from the + client to the upstream connection request. + TOS values really only have local significance - so you should know what you're specifying. For more information, see RFC2474, RFC2475, and RFC3260.