pfSense

Hello everyone,

I am trying to apply a limiter in a pfSense multi-WAN environment and I would like to know whether this is a known limitation, a configuration issue on my side, or possibly a bug.

My setup is:

• Two WANs
• Oi is the default gateway
• Vivo (PPPoE) is a non-default gateway
• I want to limit the upload speed of only two specific hosts running qBittorrent, without affecting the rest of the network

What I tried:

1. I first tried applying the limiter directly on LAN rules, assigning those hosts to the Vivo gateway. It did not work.
2. Then I switched to a tag + floating rule approach, since NAT is involved once traffic leaves through the WAN.
3. I created a specific tag for the qBittorrent hosts and applied that tag both on the LAN outbound rules and on the NAT / port forward related rules.
4. I created a floating rule on the Vivo interface, direction `out`, using the Vivo gateway and dedicated limiter pipes.
5. I tested multiple variations of that floating rule, including different source settings, upload pipe plus auxiliary download pipe, resetting states, and re-importing the config.

Even so, the traffic is still not being limited. qBittorrent upload continues to leave through Vivo normally, and the limiter is simply not enforced.

What makes this scenario tricky is that it combines several factors at once:

• multi-WAN
• non-default gateway
• PPPoE
• port forwards for qBittorrent
• limiter through floating rules
• traffic classification using tags

In practice, the configuration is accepted, the rules appear to be correct, but the actual behavior does not match the expected result.

My question is:

Is this scenario officially supported and expected to work, or is there some known limitation or bug involving limiters + floating rules + multi-WAN with a non-default gateway?

Also, in your opinion, would the better approach here be to stop trying to do this per-host and instead move these clients into a dedicated VLAN routed exclusively through Vivo?

Any guidance would be appreciated.