Squid-reverse version 3.1.19_2 - not setting DSCP/QOS after upgrade.



  • Hello,

    I applied the squid-reverse update just before last weekend and it would appear ever since it seems as if squid is no longer able to modify QOS bits on outgoing traffic.

    the acl section of squid.conf contains:

    acl youtube url_regex -i youtube
    tcp_outgoing_tos 0x28 youtube
    acl execs src 10.101.3.0/24
    tcp_outgoing_tos 0x38 execs

    cache.log is filled with:

    2012/03/26 11:05:18| comm_set_tos: setsockopt(IP_TOS) on FD 53: (22) Invalid argument
    2012/03/26 11:05:18| comm_set_tos: setsockopt(IP_TOS) on FD 362: (22) Invalid argument

    outgoing traffic TOS bits are at the default vaules:
    10:55:52.034895 IP (tos 0x0, ttl 59, id 8691, offset 0, flags [DF], proto TCP (6), length 1500)
    10:55:52.034919 IP (tos 0x0, ttl 64, id 51876, offset 0, flags [DF], proto TCP (6), length 52)

    'squid -k reconfigure' doesn't produce any errors…

    any idea what I may have to do to correct this or is it not compiled into this binary?

    thanks,
    greg

    ==  less an issue but as a note,    I noticed the error pages are now in German.    Upgrading the package seems to have changed this setting as well.  easily fixed by selecting new language from the settings page.  just didn't catch that till someone complained.



  • i'll cross check this …
    sorry for inconvenience ...



  • seems to be some issue with the freebsd ports…



  • @trendchiller:

    seems to be some issue with the freebsd ports…

    Trandchiller,  you are speaking regarding the TOS issue correct?



  • Is anyone else using squid to mark DSCP/TOS vaules?  Did things break after an upgrade?  I downgraded my install and tired,  no good,  then re-upgraded..  I am still seeing these errors in the logs and none of my packets leaving the system are having their DSCP values modified any longer..  No amount of searching is turning anything up,  the error is seen in Mac OS X land quite a bit but i've yet to see one freebsd instance reported…

    thanks,
    greg

    2012/04/02 10:49:35| comm_set_tos: setsockopt(IP_TOS) on FD 237: (22) Invalid argument
    2012/04/02 10:49:35| comm_set_tos: setsockopt(IP_TOS) on FD 237: (22) Invalid argument
    2012/04/02 10:49:35| comm_set_tos: setsockopt(IP_TOS) on FD 237: (22) Invalid argument
    2012/04/02 10:49:35| comm_set_tos: setsockopt(IP_TOS) on FD 237: (22) Invalid argument
    2012/04/02 10:49:35| comm_set_tos: setsockopt(IP_TOS) on FD 251: (22) Invalid argument
    2012/04/02 10:49:36| comm_set_tos: setsockopt(IP_TOS) on FD 351: (22) Invalid argument
    2012/04/02 10:49:36| comm_set_tos: setsockopt(IP_TOS) on FD 222: (22) Invalid argument
    2012/04/02 10:49:36| comm_set_tos: setsockopt(IP_TOS) on FD 433: (22) Invalid argument
    2012/04/02 10:49:40| comm_set_tos: setsockopt(IP_TOS) on FD 729: (22) Invalid argument
    2012/04/02 10:49:43| comm_set_tos: setsockopt(IP_TOS) on FD 556: (22) Invalid argument
    2012/04/02 10:49:44| comm_set_tos: setsockopt(IP_TOS) on FD 231: (22) Invalid argument


Log in to reply