Stop the Lag: How to Fix pfSense Bufferbloat in Minutes

Fast internet does not automatically mean low latency. If your connection feels smooth until someone starts a download or upload, bufferbloat is often the real problem. This guide shows how to fix pfSense bufferbloat using limiters, FQ-CoDel, and one floating rule so your router handles congestion properly instead of letting queues build up uncontrollably.

Why Fast Internet Can Still Feel Laggy

Bufferbloat happens when packets hit your router or ISP equipment faster than they can be processed, causing long queues and unnecessary delay. The result is high ping under load, rubber-banding in games, choppy VoIP calls, and a connection that feels inconsistent even when you have plenty of bandwidth.

A bigger internet package does not solve this on its own. More bandwidth is like adding more lanes to a motorway, but if traffic is still entering chaotic junctions with no control, latency spikes remain. What matters is queue management, not just raw speed.

What pfSense Does Better With Limiters

The modern pfSense bufferbloat fix is to use limiters with FQ-CoDel. Instead of relying on basic tail drop behaviour, FQ-CoDel actively manages queue delay and spreads bandwidth more fairly across different flows. That keeps one heavy download, update, or upload from ruining latency for everything else.

Older traffic shaper wizard setups can still work, but for most current home and small office networks, limiters are the cleaner and more practical option. They are easier to configure, easier to troubleshoot, and better suited to reducing gaming lag and keeping VoIP stable.

Before You Start

Run a bufferbloat test before changing anything so you have a baseline. A typical bad result might show a Grade C and well over 100 ms of extra latency during download or upload. After a correct limiter setup, that can drop dramatically, often into A or A+ territory with only a few milliseconds of added delay.

You should also know your real ISP speeds, not just the advertised plan. The limiter values need to sit slightly below your actual maximum throughput so pfSense controls the queue first instead of your ISP modem or upstream equipment.

Recommended pfSense FQ-CoDel Settings

Why you should under-provision slightly

Set your WAN download and upload limiters a little below your measured line rate. For example, a 600 Mbps download connection might use a 550 Mbps limiter, and an 80 Mbps upload connection might use a 75 Mbps limiter. This small sacrifice in peak throughput is usually worth it because it massively improves responsiveness under load.

Core settings to use

• Scheduler: FQ_CODEL
• Queue Length: 1000
• Enable ECN: Yes
• Bandwidth: Slightly below your real tested WAN speed
• Create a child queue for both upload and download limiter pipes

Step-by-Step pfSense Bufferbloat Fix

1. Create the download limiter

1. Go to Firewall > Traffic Shaper > Limiters.
2. Add a new limiter named WanDown.
3. Set the bandwidth slightly below your real download speed.
4. Set the Scheduler to FQ_CODEL.
5. Set Queue Length to 1000.
6. Enable ECN.
7. Save the limiter.

2. Create the child download queue

1. Under WanDown, create a child queue named WanDownQ.
2. Enable the child queue.
3. Leave the rest of the settings at their defaults unless you have a specific reason to change them.
4. Save the queue.

3. Create the upload limiter

1. Add another limiter named WanUp.
2. Set the bandwidth slightly below your real upload speed.
3. Set the Scheduler to FQ_CODEL.
4. Set Queue Length to 1000.
5. Enable ECN.
6. Save the limiter.

4. Create the child upload queue

1. Under WanUp, create a child queue named WanUpQ.
2. Enable the child queue.
3. Leave the remaining settings at default.
4. Save the queue.

5. Create the floating rule

1. Go to Firewall > Rules > Floating.
2. Add a new rule with Action set to Pass.
3. Check Quick.
4. Set Interface to WAN.
5. Set Direction to Out.
6. Set Protocol to Any.
7. Set Source to WAN address.
8. Set Destination to Any.
9. Open Advanced Options and find the In/Out Pipe section.
10. Set the first box to WanUpQ.
11. Set the second box to WanDownQ.
12. Save and apply changes.

Why the Floating Rule Matters

The floating rule is what actually attaches your limiter queues to the WAN traffic. Without it, the pipes exist but do not shape the traffic the way you expect. This is one of the most common reasons people think their pfSense limiters are not working.

Because pfSense is stateful, new shaping rules usually apply to new connections rather than old ones that are already established. That means your first retest can look unchanged even when the setup is correct.

Test Results You Should Expect

A properly tuned setup often trades a small amount of peak speed for a huge latency improvement. In one example, a connection that originally scored Grade C with 123 ms of added latency improved to A+ with only around 4 ms of extra delay during downloads. That kind of improvement is far more valuable for gaming, calls, and general responsiveness than holding onto every last megabit.

For gaming, this is where bufferbloat fixes become noticeable. Matchmaking might still feel normal on a bloated line, but once the network gets busy, packet delay causes inconsistent hit registration, rubber-banding, and sudden ping spikes. Good queue management fixes the part that bandwidth alone cannot.

How to Properly Set Up Port Forwarding for Gaming and Remote Access

Troubleshooting When Your Score Does Not Improve

Clear old states first

If your retest does not improve immediately, clear firewall states or restart the device and browser you used for testing. Existing sessions may still be bypassing the new floating rule behaviour because they were created before the limiter was applied.

Common mistakes

Setting the limiter bandwidth too close to ISP maximum

Forgetting to create child queues

Applying the wrong pipes in the floating rule

Testing again without clearing old states

Assuming high bandwidth automatically means low latency

Check your local network too

Bufferbloat is a WAN queue problem, but poor local networking can still add latency on top. If you are gaming over weak wireless, congested 2.4 GHz, or a router filled with slow legacy clients, you may still feel delay even after fixing WAN shaping.

Why Your Wi-Fi Is Slow (Even With a Fast Plan)

Is This Worth It for Home and Small Office Networks?

Yes. This setup is especially useful for households with gaming, streaming, cloud backups, video calls, and multiple users sharing the same line. It is also valuable in small office setups where one large transfer can otherwise disrupt VoIP quality or remote work sessions.

The main trade-off is simple: you intentionally cap throughput slightly below the line maximum so pfSense controls the queue properly. In practice, that is almost always a good trade when the reward is much lower latency and a more stable network under load.

Final Takeaway

The best pfSense bufferbloat fix is not a complicated wizard or endless tuning. It is a clean limiter setup with FQ-CoDel, ECN enabled, child queues created correctly, and a floating WAN rule that applies those queues to traffic. Once that is in place, your connection stops feeling overloaded every time someone uses it heavily.

FAQ