RUT QoS(Traffic Shaping) failed

I attempted to configure bandwidth prioritization for different LAN segments using Traffic Shaping > Classification Rules on the RUT241, but it is not working as expected.

Setup:

  • Repurposed the original WAN port as a LAN segment, creating two independent LAN segments:
    • Segment A: 192.168.10.0/24
    • Segment B: 192.168.100.0/28
  • The WAN side is connected via Wi-Fi client mode to another router (actual throughput ~20Mbps).
  • Added the following Classification Rules under Traffic Shaping:Target | Source Host | Destination Host | Protocol | Ports
    Bulk | 192.168.10.0/24 | All | All | All
    Priority | 192.168.100.0/28 | All | All | All
    Bulk | All | 192.168.10.0/24 | All | All
    Priority | All | 192.168.100.0/28 | All | All

Test Scenario & Observations:

  • Launched independent iperf3 clients from both segments, connecting to an iperf3 server on the WAN side.
  • Despite the priority settings, both Segment A and Segment B received exactly 10Mbps each, while the Wi-Fi client mode has a total practical throughput of 20Mbps.
  • Assuming QoS might not take effect due to sufficient bandwidth, I tested by limiting WAN bandwidth under Traffic Shaping > Interfaces (10Mbps → 5Mbps → 2Mbps → 1Mbps). However, the iperf3 results remained nearly identical for both segments.

Goal:

  • Segment A transmits video from security cameras to a server.
  • Segment B uploads sensor data (e.g., temperature) to a server.
  • Segment B is more critical, so in low-bandwidth conditions (Wi-Fi or mobile networks), video bandwidth should be reduced to prioritize sensor data.

Request for Advice:

  • Why is my QoS configuration failing?
  • How can I achieve the goal, whether through QoS, Traffic Shaping, or other methods?

Any insights would be greatly appreciated!

Additional Testing:

  • In the default configuration of the RUT241, I connected a switch to the physical LAN port, with two clients, and the physical WAN port connected to another router (which is connected to the server).
  • I configured Traffic Shaping > Classification Rules with fixed IP addresses (instead of using CIDR notation for segments) for Source and Destination, but the results remained the same.
  • The issue persists in both upstream and downstream iperf3 tests.