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

    CoDel - light reading

    Scheduled Pinned Locked Moved Traffic Shaping
    1 Posts 1 Posters 712 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.
    • H
      Harvy66
      last edited by

      https://tools.ietf.org/pdf/draft-ietf-aqm-codel-01.pdf

      I was just reading through this and some minor things caught my attention

      1. The interval of 100ms is used because that's the estimated RTT for many connections. When CoDel is running on an end device, the RTT for a given queue can actually be known instead of just a fixed guess. Their example was to use the max TCP RTT within a queue. Since PFSense is stateful, I wonder if TCP RTT information can be acquired and used to dynamically change the interval. The Target is just 5% of the interval, so both can be dynamic

      2. Google changed CoDel to ignore small control packets. Not a good idea if you're running a network where you are concerned about the network being abused, but it could possibly be useful for non-ISP users to have that option.

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