AZTCOFWCYBER SECURITY SOLUTIONS
Knowledge baseChange logDocumentation in English
Knowledge base/Why is not properly shaped?

AZTCOFW / TECHNICAL GUIDE

Why is not properly shaped?

Troubleshooting Traffic ShapingTroubleshooting

The reason is nearly always one of these choices:

  • The traffic matched a different rule than expected
    • The traffic did not match any rule

As with other questions in this section, this tends to happen because of rules entered either internally or by other packages that do not have knowledge of queues. Since no queue is specified for a rule, it ends up in the default or root queue, and not shaped.

Working around the limitation may require altering the rules to better match the traffic, or disabling internal rules that are matching the traffic in unexpected ways. Another tactic is to identify all other traffic and then use different shaping options on the default queue.

In rare cases, such as bittorrent, it may be impossible to accurately identify all traffic of a given type. One workaround is to isolate the traffic to one specific device on the network and then match based on that client device address.

Imported from the AZTCOFW knowledge base on 2026-09-05. Historical guidance may refer to older software versions. Confirm applicability before changing a production system.

Original source ↗
Privacy policy ↗

Search

Search website content and the English knowledge base.

Start with a product, topic or question.