Netgate Discussion Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Search
    • Register
    • Login

    Diffserv Code Point Match rule not working

    Scheduled Pinned Locked Moved Traffic Shaping
    2 Posts 2 Posters 1.3k Views
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • M
      Mchiefp
      last edited by

      Hello,

      I'm trying to setup a traffic shaping rule to move all traffic for my Crashplan backup service (running on an Ubuntu server) to a queue called "qOthersLow".  Crashplan supports setting the Diffserv Code Point value and I've followed this guide (https://www.tucny.com/Home/dscp-tos) to configure Crashplan with a TOS Dec value of 40, which translates into a DSCP class of af11.  I've confirmed that Crashplan is adding this DSCP designation to the packets by running this on my Ubuntu server:

      sudo tcpdump -v -n -i bond0 'ip and ip[1] & 0xfc == 40'

      07:19:22.299726 IP (tos 0x28, ttl 50, id 21841, offset 0, flags [DF], proto TCP (6), length 52)
          162.222.42.208.443 > 192.168.1.10.52530: Flags [.], cksum 0xde7c (correct), ack 1199785, win 3801, options [nop,nop,TS val 1399313738 ecr 19232212], length 0

      Next I've setup a pfSense Floating Match rule to do the following:

      • Under Advanced Options Diffserv Code Point = af11
      • Queue is set to qOtherLows
      • Everything else in the rule left alone

      Unfortunately after saving and applying this rule all my Crashplan traffic remains in the "qDefault" queue.  Any ideas? Anyone else have a better/different strategy to isolate Crashplan traffic?

      Paul

      1 Reply Last reply Reply Quote 0
      • N
        Nullity
        last edited by

        Did you reset pfSense's states?

        If you still have problems, you can use pfSense's firewall logs or tcpdump to see what is happening from pfSense's perspective.

        Do you need to use DSCP? Could use standard source/destination IP/port filtering?

        Please correct any obvious misinformation in my posts.
        -Not a professional; an arrogant ignoramous.

        1 Reply Last reply Reply Quote 0
        • First post
          Last post
        Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.