Those who are not afraid to experiment, welcome to https://forum.pfsense.org/index.php?topic=126637.msg699341#msg699341
Thanks to qubit, everyone now can try playing with FQ_CODEL at least.

I just wanted to say THANK YOU.  I've been like a whole month searching for this and couldn't find it anywhere and you were kind enough to not only state the exact same problem I was having but also to show up with a tutorial.

You're pure gold !

You can't use limiters with policy routing. You'd have to use floating rules to set limiters to match outbound traffic on the WANs in order to limit with policy routing/failover/LB

The problem with doing that on 2.3.x and 2.2.x is that limiters have some problems there where you can't use limiters on rules that perform NAT, which would cause the traffic to be dropped.

We've fixed that on pfSense 2.4, which is currently in beta

I think ISP fixed something.

I met the same issues. Thank you guys! have a nice day!

pki

would you conside hfsc to simply limit the bw ?

I followed the approach suggested here for multi wan and hfsc:
https://forum.pfsense.org/index.php?topic=120380.0

Not tested it on pipes, though but it may work.
Let you know if I get chance to try it out in my test lab.

A

dropped packet inbound, which means the receiving computer will not report the chunk of data as arrived as pfsense will have prevented the packet been passed on, so the ack never gets sent back to the sender, as a result the sender will backoff as it will assume its congestion.

This post is a litte bit old, but i had success configuring a limiter in a floating rule. The options used in my case were:

Action: Match
Direction: in
Protocol: any
Source: any
Target: NOT internal_networks
Schedule: working_hours
In/Out: UploadLimiter/DownloadLimiter

The idea was to limit every PC to a maximum BW usage (which requires the limiters to be configured in a certain way). I tested it with speedtest.net, and it limited upload and download ok.

Yeah, I'd like to see a simple solution to this as well.

For now, I just cap the iOS device's upload to like 40%.

What I did for plex is go to floating rules copy the high priority rule for https and put the plex port 32400. btw I gave http high priority in the wizard

Thats a good point. I just watch the download speed on a PC or the traffic graph in pfSense. And I do see ACKs flowing out on the WAN interface of course, but that shouldn't influence the borrowing of downstream queue capacity, right? And the ACK queue has 700kbits reserved and I only see about 100-125kbits of ACKs.

A little late to the party, no?  This post is 4 years old and this guy hasn't logged on in almost a year.

Interesting.  So with some cooperation from the client, it would be possible to do what I'm thinking.  Good to know.  I'll definitely refer back to this thread if/when I ever need to shape within my ovpn tunnels.

Yes for all questions.  Read this:

https://www.reddit.com/r/PFSENSE/comments/3e67dk/flexible_vs_fixed_limiters_troubleshooting_with/

And the story goes on: it seems that the observed 'half-duplex' behavior is actually not a problem of pfSense. It's really the DSL line! I'm observing the same phenomenon when connecting my machine directly to the DSL modem.

No way to do any kind of traffic shaping if we cannot rely on any specific bandwidth, i.e. when downstream bandwidth is dependent on upstream etc. I guess we have to look for another more reliable connection…

Thanks everybody for the good suggestions!

How are you qualifying your traffic?  Have you confirmed that your traffic is going into the proper queues?