[Edited] Limiters not working with Port Forwarding
I have an FQ_Codel Limiter set-up as per the Lawrence systems and Netgate videos.
Traffic shaping works fine except for my torrent client.
I have my limiter set to 200mbps but the torrent client can download at speeds of over 40MB/s. Everything else gets limited to 25MB/s of total WAN bandwidth.
What is the problem?
Edit: Found the problem! The port forwarding rule for the Torrent client let it bypass the limiter. Setting the queues also to the port forward rule fixed the problem.
Edit 2: Adding the queues to the port forward rule fixes the problem but breaks the port forwarding. Any ideas on how to fix?
Formerly before title edit: "Torrents completely bypassing FQ_Codel Limiter"
OK, so to recap, trying to set a Limiter with a floating rule while using port forwarding does not work. The application that has the port(s) forwarded to it completely bypasses the limiter.
Trying to set Limiter queues to Port Forwarding rules also does not work. What happens is that inbound traffic gets blocked as if the port was never forwarded to the application.
Is this documented as a bug? Is there any work on this?
KOM last edited by
@sotirone You shouldn't need a port-forward to run a torrent client.
@kom I need port forwards in order for my client to be discoverable. I also use port forwarding for other services that also need the limiter set. I updated my post above with the newly created problem.
KOM last edited by
@sotirone That might be the mult-wan nat bug where inbound port-fowards only work for the default WAN.
@kom Although I am using "multi WAN" (WAN and VPN), my applications are running on the WAN interface. There are no Gateway Groups or anything, I just have the VPN assigned as a gateway for a couple of devices (not for the server running the torrent client).