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

    fq_CoDel Traffic Shaping with multiple OpenVPN Clients

    Scheduled Pinned Locked Moved Traffic Shaping
    5 Posts 2 Posters 1.0k 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.
    • J
      jasonsansone
      last edited by

      I have read through the other threads in this subform and followed various instructions, but I am still uncertain of how to utilize fq_CoDel limiters with my configuration. I am running the most recent RC release of 2.4.4 (as of this posting). I know how to setup the limiters, but not how to implement them under Rules.

      I have two client OpenVPN configurations, no server. One is a site to site trunk linking my home to my office. The other is to IPVanish. I segment traffic into the IPVanish VPN accordingly, everything else exits the WAN unless it is to an internal IP located on the office LAN. How to I utilize traffic shaping on this configuration?

      0_1537461113677_91aba8f6-3ac0-4002-9dc0-7529db496f7d-image.png

      0_1537461141549_646621bc-e25e-4734-848f-11b42da0f78a-image.png

      0_1537461173846_1b701bd7-40c5-42a7-9281-7552a5b6791a-image.png

      0_1537461195745_7cffb81c-2e3d-4bf4-a8f8-2c73bc721bf3-image.png

      1 Reply Last reply Reply Quote 0
      • T
        TheNarc
        last edited by

        I believe that all you should need to to is assign traffic to your limiter queues in your firewall rules. Since you only have one up and one down queue, all four of your rules will assign to the same queues (for LAN rules, in pipe to upload queue, out pipe to download queue; for WAN rules, in pipe to downloads queue, out pipe to upload queue).

        1 Reply Last reply Reply Quote 0
        • J
          jasonsansone
          last edited by

          So just modify the existing four routing rules (1 WAN, 3 LAN) but do not create or modify any floating rules as is suggested in other threads? Thank you.

          1 Reply Last reply Reply Quote 0
          • T
            TheNarc
            last edited by

            Yeah. I think the only reason to use floating rules to assign traffic to limiters would be so that you don't need to do that assignment on each LAN or WAN rule. For example, you could make a floating rule to just match all inbound traffic on the LAN interface and another to match all inbound traffic on the WAN interface, and do your limiter assignments, and then rule processing would continue on to the LAN and WAN rules. But you have so few rules, I feel like you may as well just assign in each of them. Plus, I know I've read reports of the "match" action on floating rules not working under certain circumstances . . . may or may not be a real issue, but there's no compelling reason to use them here.

            1 Reply Last reply Reply Quote 1
            • J
              jasonsansone
              last edited by

              Works perfect. Thank you so much.

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