On 2016-May-10, at 10:14 AM, WebDawg <[email protected]> wrote: > Usually the only thing that you > can do in this situation is put your connection at its lowest setting > and control the connection from there. The problem with this is that > the connection will always be this lowest speed.
FWIW, our connection is also somewhat "variable" (i.e., our ISP often misconfigs their QoS at a higher speed when doing updates and it stays that way 'till there's an issue and a support person shuts it back down!). I've config'd pfSense's Traffic Shaper to use FairQ where, according to various bits of documentation I've been able to find, uses the bandwidth settings for limiting only when saturated and, otherwise, allows the limits to be exceeded. As far as I can tell, though I've not done extensive testing, this is the way it's working. Specifically, when our link is misconfig'd for a higher rate, we get the higher rate without being stuck at our lower/config'd limit (and without any shaping effect unless we saturate that limit, which doesn't seem to occur). Though we don't have a particularly busy network (biggest stressors are downloads and 2 concurrent UHD Netflix streams), I've actually been quite pleased with the FairQ setting. We've been using it for at least a couple of years, IIRC. _______________________________________________ pfSense mailing list https://lists.pfsense.org/mailman/listinfo/list Support the project with Gold! https://pfsense.org/gold
