[squid-users] tos - setsockopt() problem - fwmarking possible?]

[ sorry for the delay -- lost use of one hand -- hunt and peck on the
keyboard ]

Hi Henrik

Thanks very much for your note.

I think that you mis-typed the RFC it's actually 3168 ... anyway. The ip
TOS is now 4 bits, so the squid.conf.default ought to be changed to
reflect 0 -> 63 rather than 0 -> 255 as is now indicated.

Looking thru the archive, i noticed that you have mentioned on several
occasions that meta-data marking (iptables/fwmark/nfmark) is not
possible in squid.

Does this remain the case? It would really nice if I could patch it mark
hits/misses with fwmark -- marking this way allows an efficient hash
table for my tc config.

Cheers & Thanks Again

Charles

On Sat, 2005-02-19 at 16:22 +0100, Henrik Nordstrom wrote:
> On Thu, 17 Feb 2005, lartc@manchotnetworks.net wrote:
>
> > has anyone noticed on fc3 a tos setsockopt() problem ??
> >
> > if i try to set tos_outgoing to 0x8 it works just fine. set it to 0xEE
> > and no tos marking happens.
>
> The ToS octet in TCP/IP has a long muddled history, but things have now
> settled and these days it is 6 bits in size for DS (RFC2474) and the top
> two bits is used by ECN (RFC3158) and can not be set by applications.
>
> For details see
>
> RFC2474 Definition of the Differentiated Services Field (DS Field)
> RFC3158 The Addition of Explicit Congestion Notification (ECN) to IP
>
> RFC3158 has some quite interesting reading in section "22. Historical
> Definitions for the IPv4 TOS Octet" and I recommend to start by reading
> this.
>
> Regards
> Henrik
Received on Tue Mar 01 2005 - 02:32:03 MST