Shaping worked 2.2 RC but not 2.2 Release.
-
My traffic shaping worked great with the RC release (https://forum.pfsense.org/index.php?topic=81692.0), but does not seem to be working with the release. I set NNTP traffic to lower priority. In release, this has no impact. NNTP traffic can hog the entire WAN bandwidth. I am using HSFC.
What is strange is when I am reading the queue status page, it shows qLink on the LAN interface at my cable's max speed. I figured I would see high traffic on a WAN interface queue, preferably qOthersLow. It appears the interfaces are reversed, or I'm reading the page incorrectly.
FYI, pfSense is 2.2 in a Proxmox 32-bit VM. Traffic Shaper has been deleted and re-created with the wizard with no change in results.
-
I restored a 2.2 RC VM to test NNTP on this current job and am seeing the same results. So, my theory about RC working doesn't seem so.
Would the fact it's an SSL connection to the NNTP server make a difference?
Still not sure why it shows the traffic as being on the default qLink queue of the LAN.
-
If no other traffic is happening then the NNTP connection will get it all even though it's in a low queue.
-
Sorry. I figured it out. Ignore my ignorance. I found where I needed to define new floating rules for port 563, which is SSL connection to NNTP server. That traffic is now being routed to the lower priority queue.
-
I would be careful about using the term "priority" when talking about HFSC. I assume you mean "less bandwidth"?
-
I would be careful about using the term "priority" when talking about HFSC. I assume you mean "less bandwidth"?
Correct. I was just using the wizard's terminology.
-
Correct. I was just using the wizard's terminology.
The wizard tries to be one size, fits all GUI, and that's why you see references to priority when creating an HFSC shaper. HFSC doesn't deal in priority levels, only bandwidth allocation.
