Re: [squid-users] tcp_outgoing_tos doesn't work in 3.2?

09.11.2012 20:58, Andrew Beverley пишет:
> On Fri, 2012-11-09 at 14:18 +0200, Pavel Bychykhin wrote:
>> Hi All!
>>
>> Recently i tried to upgrade my Squid 3.1.21 to 3.2.3.
>> Everything works fine, but tcp_outgoing_tos no longer affects outgoing packets.
>> Here fragment from my config:
>>
>> acl rfc1579 dst 192.168.0.0/16
>> acl rfc1579 dst 10.0.0.0/8
>> acl rfc1579 dst 172.16.0.0/12
>> tcp_outgoing_tos 0xC !rfc1579
>>
>> Rollback to old version solves the problem.
>> My system is FreeBSD 8.2. Squid installed from ports (squid-3.2.3_1).
>
> Can you set your debug to level 3 and see if/what TOS errors/messages
> you get? There will be a lot of messages, so look for the following
> strings:
>
> "fwdConnectStart: got outgoing addr" [will be followed by tos being set]
>
> "Ip::Qos::setSockTos: setsockopt(IP_TOS)" on [will be shown on error]
>
> Andy
>

Fragment from log of Squid 3.2:
2012/11/10 14:31:08.157 kid1| fwdConnectStart: got outgoing addr 0.0.0.0, tos 12
2012/11/10 14:31:08.157 kid1| The AsyncCall fwdConnectDoneWrapper constructed, this=0x28fbb340 [call982]
2012/11/10 14:31:08.157 kid1| peer_select.cc(87) peerSelectStateFree: http://www.myip.ru/ru-RU/index.php
2012/11/10 14:31:08.157 kid1| StoreEntry::unlock: key '2B27CF0FA399E53F4D6BDA4269A33291' count=2
2012/11/10 14:31:08.157 kid1| comm_openex: Attempt open socket for: 0.0.0.0
2012/11/10 14:31:08.157 kid1| comm_openex: Opened socket local=0.0.0.0 remote=[::] FD 12 flags=1 : family=2, type=1, protocol=6
2012/11/10 14:31:08.158 kid1| Ip::Qos::setSockTos: setsockopt(IP_TOS) on local=0.0.0.0 remote=[::] FD 12 flags=1: (22) Invalid argument
2012/11/10 14:31:08.158 kid1| fd_open() FD 12 www.myip.ru
2012/11/10 14:31:08.158 kid1| ConnOpener.cc(177) start: local=0.0.0.0 remote=195.161.112.6:80 flags=1 timeout 60

Fragment from log of Squid 3.1:
2012/11/10 15:17:52.602| fwdConnectStart: got outgoing addr 0.0.0.0, tos 12
2012/11/10 15:17:52.602| comm_openex: Attempt open socket for: 0.0.0.0
2012/11/10 15:17:52.602| comm_openex: Opened socket FD 14 : family=2, type=1, protocol=6
2012/11/10 15:17:52.602| fd_open() FD 14 http://www.myip.ru/
2012/11/10 15:17:52.602| fwdConnectStart: got TCP FD 14
2012/11/10 15:17:52.602| comm.cc(1196) commSetTimeout: FD 14 timeout 60
2012/11/10 15:17:52.602| comm.cc(1207) commSetTimeout: FD 14 timeout 60
2012/11/10 15:17:52.602| The AsyncCall SomeCommConnectHandler constructed, this=0x2886d970 [call1033]
2012/11/10 15:17:52.602| commConnectStart: FD 14, cb 0x2886d970*1, www.myip.ru:80
2012/11/10 15:17:52.602| StoreEntry::unlock: key '917E2363E482280648BBE338BA530A7D' count=2
2012/11/10 15:17:52.613| commConnectCallback: FD 14
2012/11/10 15:17:52.614| comm.cc(1196) commSetTimeout: FD 14 timeout -1
2012/11/10 15:17:52.614| comm.cc(1207) commSetTimeout: FD 14 timeout -1
2012/11/10 15:17:52.614| comm.cc(935) will call SomeCommConnectHandler(FD 14, data=0x28871250, ) [call1033]
2012/11/10 15:17:52.614| commConnectFree: FD 14
2012/11/10 15:17:52.614| entering SomeCommConnectHandler(FD 14, data=0x28871250, )
2012/11/10 15:17:52.614| AsyncCall.cc(32) make: make call SomeCommConnectHandler [call1033]
2012/11/10 15:17:52.614| fwdConnectDone: FD 14: 'http://www.myip.ru/'

This instance of Squid is running in jail. May be it's a key to problem?

-- 
Best regards,
Pavel