You can play with it, but queue limit shows on every discipline, regardless of it actually being used. The UI is not complex enough to show/hide based on what is supported.

I don't know if you've seen this guide on fixed vs. flexible limiters, but this is the one I used.

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

I found the flexible limiter works best for my environment, and I verified the up and down limits were working by using speedtest.net.

Here is the latest config for multi modem's.  This is the list of updates:

1. Added in Alias's for:
    A. The Division , Battlefield 4 , Rocket League , Warframe , Wargaming Family of Games (WoT , WoS)
    B. Cleaned up a few Alias's as well.
2. Cleaned up Floating Firewall rules to a more condensed list.
3. Made a generic password - pfsense111 so that you can use my System config which has modifications to it.
4. Added back in apinger with Gateway monitoring of Level 3 external DNS for the IP so that when getting same gateway on cable modem's you will get a true RTT now instead of using default gateway.
5. Modified Traffic Shaper so all queues are set to 100.
6. Modified Traffic Shaper for the following split:
    A. qACK - 20%
    B. qHTTP / qGames - 35%
    C. qDefault / qCatchAll - 10%
7. Added NAT configs so that static port mapping is enable for all WAN's to help with console use at LAN Parties - this is just for generic console use on your tables. This is not going to fix Halo 5 issues on Xbox One problems with Teredao IP and Strict NAT.
8. UPnP is enable by default.

So to use this config do the following:

1. Download the Zip and extract.
2. Login to PFSense and restore
3. Remember the password is pfsense111
4. Rename the WAN's as you desire.  If you need more than 2 then enable Traffic Shaping for them as it is not checked right now. There are 4 WAN's in this config.
5. Modify DNS under General if you dont want to use who I have set there.
6. CHANGE THE LIMITER UNDER FIREWALL / LIMITER to what limits you want.   - right now this is set at 5Mbits for Down and 2Mbits for Up as I was testing.

As always backup your config before you put mine on your system.  Remember to reset your states.  Enjoy the config and happy LAN partying!!!!  if you have suggestions please post in a different topic as I want to keep this clean for edits and updates of the config.

Thanks.

PfseneMultiWANGoldConfig.zip

hi Derelict,

@Derelict:

If each subnet is limited, do you really care about limiting it further if it's somewhat equally shared?

decided to go on with this option, at least till i reach to any other suitable solution. can you please point me to the directions on how should i implement this (configuration wise)?

i get the "limiting each subnet" part. i create limiters (without dynamic pipes) and apply it in LAN rules for subnets. How am i gonna configure to "somewhat equally share" bandwidth within the users of that subnet?

thanks in advance.

You can use HFSC, create a separate queue for HTTP traffic for each WAN interface, then assign the queues depending on which WAN is used, set HFSC's queue upper limit to 70Mb.

Thanks for your observation. I wish I new what was going on with Suricata Inline Mode and the traffic shaper. The Pfsense is running on a Xeon server with 16MB and Intel I350 network card The hardware is the best and not an issue as far as I can see. I am back the Legacy Mode for Suricata until this matter is resolved.

Best Regards,

Howard

You could simply HFSC shape outbound WAN (uploads) with a 100Mbit upperlimit. If you make a queue for each LAN subnet and give them both the same queue settings it should evenly share the pipe.

Downloads are trickier since you have two LANs. I see in the other thread you're using CARP so I presume you have a pfsync setup so that eliminates the use of limiters due to a bug.

The only way I know of to do this with multi-LAN and HFSC is to place a node between you and the ISP shaping the traffic out one interface and into another node with LAN and OPT1.

Gig-E –- Shaper node --- Gig-E --- WAN --- existing node --- LAN & OPT1

Or you could use a 50Mbit upperlimit on each interface and they would not be able to borrow from each other.

All in all you cannot control how fast traffic arrives from your ISP. Can they rate-limit what they send to you?

@Harvy66:

You set your LAN interface bandwidth to 145Mb? Just asking because many people claim "I set X to Y", but it turns out they actually set "Z" to Y.

So for me to get the speed I want I have the LAN interface set to CODELQ at 186320Kbit/s this is the only way I can get to the speed results I am looking for. If I just type in 150Mb I get no where near 150Mb on a speed test.

PFsense.jpg
PFsense.jpg_thumb
Speedtest.jpg
Speedtest.jpg_thumb

2 queues, 1 lan (download), 1 wan (upload). Set both to 20Mbit.

@linucksrox:

I don't understand this answer. … why would I not be able to use pfsense to limit the rate at which the client is able to download from that server?

You can properly rate limit data leaving your interfaces but not interesting your interfaces. The term "download" is relative. I download from the server, but the server downloads from me. A less ambiguous way to describe the situation is saying you want to rate limit egress from OwnCloud to external clients.

What I have never used is ownCloud.

Limiters are pretty much broken in pfSense 2.2 and later.

@Harvy66:

If you're trying to diagnose why a packet came in the WAN but not out the LAN, it would be nice to know your dropped packet count went up by one instead of it just disappearing with no indication anywhere as to why.

Like I mentioned earlier in the thread, I think queue drops are only logged as such if the queue is the reason for the drop.

Other drops are not, but should they be? I dunno. I would prefer that all the rrdtool graphs in pfSense were more reliable, but since I do not use those graphs for anything important, I kinda don't care…

I would probably use tcpdump to solve the situation you describe, because I am unclear of the semantics involved in the interface/queue stats.

I was also having a problem with my cable connection. I don't have dual WAN but I read the following post which has fixed my problem, it might help with yours, but can read you have done some traffic shaping. Might be worth a look?
https://forum.pfsense.org/index.php?topic=98404.0