Skip to main content
GoodVibesTech
GoodVibesTech
Visitor III
December 4, 2025
Question

Traffic Shaper Per IP Based on Monthly Data Volume

  • December 4, 2025
  • 1 reply
  • 449 views

Hello Fortinet Community,

I am trying to implement cumulative traffic quotas per IP on a FortiGate device. The goal is to:

  1. Limit each server or IP to 6 TB per month.
  2. After reaching 6 TB, throttle traffic to 15 Mbps.
  3. Reset quotas automatically at the start of each month.

I understand from Fortinet TAC that FortiGate does not natively support data-volume-based traffic shaping over a time period. I have explored web-filter quotas, but they are daily, category-specific, and require proxy mode, which is not suitable for our use case.

My question is:

  1. Is it possible to achieve this using Forti Analyzer automation or event handlers?

  2. If yes, can someone provide guidance or example configurations?

  3. Are there any recommended best practices or workarounds to enforce per-IP monthly data quotas?

Note: FortiGate Version is 7.4.8 and so is FAZ.

Thank you in advance for any advice or guidance.

Best regards,

1 reply

farhanahmed
Staff
farhanahmed
Staff
December 4, 2025

FortiAnalyzer Event Handler can only trigger a stitch if: say sent/received bytes reach the 6TB limit but the 'Action' to limit and throttle is NOT controlled by FAZ.

 

I am not sure how would you throttle on the FGT, if there is a CLI command on FGT that can do it then you can set it up in 'Action' for the Event Handler.

    GoodVibesTech
    GoodVibesTechAuthor
    Visitor III
    December 6, 2025

    Thank you for the clarification. That makes sense ,if Forti Analyzer can only trigger the event but not enforce shaping directly, the challenge is finding a FortiGate-side action that can apply per-IP throttling dynamically.

    From what I can see, FortiGate doesn’t currently offer a CLI command to modify traffic-shaping policies on a per-IP basis on the fly, which limits what an Event Handler can actually automate. It seems the missing piece is the ability to programmatically adjust shaping rules once the quota is hit.

    I appreciate your input; this helps confirm the limitations and keeps me from going down the wrong path. If anyone has found a creative workaround or script-based method that can reliably enforce per-IP monthly quotas, I’m still very interested.

    Thanks again!

      Terms & ConditionsAccessibility statement