On Apr 26, 2012, at 3:59 PM, Andrew Beverley <andy@xxxxxxxxxxx> wrote:
> On Wed, 2012-04-25 at 00:11 -0400, Brian R. Landy wrote:
>> Well, I was not using the correct field.
>
> But it's still not working?
Correct
>
>> I had also tried using something simple, like "clientside_tos 0xb8 all"
>> (which under 3.0 definitely tagged all traffic) and it did nothing under
>> 3.2.0.17.
>
> I assume that you're definitely checking packets from squid to the
> *client* that made the original file request?
I am. Both using tcpdump and because I am using tos for altq traffic shaping, I can see whether or not pf assigns traffic to the queue. Since my configuration does work under 3.0 I do have positive confirmation that I am watching the traffic properly with tcpdump and have altq configured properly.
>
> Anyway, to further debug this, can you please wind the debug level up to
> 3 or greater. If setting the TOS is failing then you will see something
> like:
>
> Ip::Qos::setSockTos: setsockopt(IP_TOS) on ...
>
I tried this and it this seems to indicate a problem, for example:
Ip::Qos::setSockTos: setsockopt(IP_TOS) on local=208.92.36.251:80 remote=192.168.170.42:58810 FD 25 flags=33: (22) Invalid argument
Brian
