Re: [squid-users] Squid3.3.10 tcp_outgoing_tos still does work with freeBSD ?

Hi, Andrew!

Thanks for your reply!

Here is what i saw in my cache.log

2013/12/26 15:20:27.896 kid1| forward.cc(1063) connectStart:
fwdConnectStart: got outgoing addr 0.0.0.0, tos 64

2013/12/26 15:20:27.896 kid1| AsyncCall.cc(18) AsyncCall: The
AsyncCall fwdConnectDoneWrapper constructed, this=0x8042778d0
[call478]

2013/12/26 15:20:27.896 kid1| peer_select.cc(96) peerSelectStateFree:
http://n.baidu.com/v.gif?pid=107&url=http%3A%2F%2Fbaijia.baidu.com%2F&type=0&m=11&ct=1&a=1&c=top&pn=2&t=%E3%80%8A%E6%96%B0%E9%97%BB%E6%99%9A%E6%8A%A5%E3%80%8B%E5%85%B3%E5%BC%A0%EF%BC%9A%E8%AF%9E%E7%94%9F%E6%97%B6%E5%B0%B1%E6%9C%89%E8%87%B4%E5%91%BD%E7%BC%BA%E9%99%B7&ra=0.04313793289206358

2013/12/26 15:20:27.896 kid1| store.cc(570) unlock:
StoreEntry::unlock: key '9774012C8A4E51137F545C2B8170CB31' count=2

2013/12/26 15:20:27.896 kid1| comm.cc(554) comm_openex: comm_openex:
Attempt open socket for: 0.0.0.0

2013/12/26 15:20:27.896 kid1| comm.cc(595) comm_openex: comm_openex:
Opened socket local=0.0.0.0 remote=[::] FD 18 flags=1 : family=2,
type=1, protocol=6

2013/12/26 15:20:27.896 kid1| ip/Qos.cci(31) setSockTos:
Ip::Qos::setSockTos: setsockopt(IPV6_TCLASS) on local=0.0.0.0
remote=[::] FD 18 flags=1: (22) Invalid argument

On Sat, Dec 28, 2013 at 12:40 AM, Andrew Beverley <andy_at_andybev.com> wrote:
> On Thu, 2013-12-26 at 15:59 +0800, Ge Jin wrote:
>> Hi all!
>>
>> We want to use tcp_outgoing_tos with freeBSD 10.0-BETA2.
>
> [...]
>
>> So, it's the tcp_outgoing_tos still has bug in freeBSD or I have some
>> mistake there ?
>
> Have you tried increasing the logging level? Set it to at least 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]
>
>
Received on Tue Dec 31 2013 - 01:21:43 MST