Thanks for the assist, but I just solved it. I created a new queue under LAN called qLink, same hierarchy as qInternet, assigned 1Gbit to LAN and 993MBit to qLink. Defaulted queue to qInternet, created SMB floating rule for all interfaces (top of the list) with qLink queue. Getting a whooping 80MBit transfer speed between PC's under same network compared to 8MBit. Also getting 10Mbit between interfaces (one client has 100M NIC). Next thing to work on: LanCache  ;D

Good questions. On the "By Queue" tab you'll see that each queue can be associated with multiple interfaces. Like you I'm unclear how available download bandwidth is shared between multiple LANs. Upload is simple as that's defined once, on the WAN interface. I'm not sure if the wizard is doing it incorrectly as it shows all LANs as peers at the top level with no common parent. I'd have expected a single download queue with the LANs as children, sharing that bandwidth (assuming that each LAN is faster than the WAN!). Steve

PRIQ doesn't rely on bandwidth specifications; all it cares about is higher priority packets go first.  The traffic shaper UI treis to accommodate everything at once, but not all elements apply to all shapers. Also, the traffic shaper isn't a limiter, so your queues will use up as much bandwidth as they can get while following the rules.  If you have no action in your high queues, your low queues will zip along.  When higher-class traffic appears, it gets priority, but the lower queues aren't throttled.  If your P2P queue is still getting 600K/s, then it means that your higher queues are being properly serviced without impacting the P2P queue too much.

The wan interface is your upload BW, so 1Mb And the lan/wifi is your download BW, so 3Mb

Thanks for the info, this makes it more clear! Unfortunately it seems like there is no easy solution, the version with stacked pfsenses is nice but little bit overkill for a roadwarrior szenario ;)

No? Happening on my media downloader too.  Set to 500k limit downstream, currently downloading at 30 megabits.

For the Priority field then, at least, there should be any other lable other than the following: "For hfsc, the range is 0 to 7. The default is 1. Hfsc queues with a higher priority are preferred in the case of overload." It could be just this label: "Priority does not apply for HFSC. Please keep it blank for HFSC"

@sideout: Yes you can delete them. thank you i will observe for while…

I just stumbled on this yesterday and it is the best writeup of HFSC that I have seen yet: http://ace-host.stuart.id.au/russell/files/tc/doc/sch_hfsc.txt

I advise you not to answer questions you find vague. Thank you.

I'm not an expert or even intermediate traffic shaper user, but I want to help you out so here goes… Create an alias for the two PCs that need top bandwidth, eg. VIP_PC Run the Traffic Shaper wizard to create a VoIP shaper only. Use the alias (VIP_PC) you just created as the VoIP source. That should be it.  The wizard will create a VoIP queue that gets top bandwidth, except you won't be having any VoIP phones using it, just those two PCs.  You can check it by looking at Firewall - Rules - Floating.  You should have two rules, one in one out, that directs all I/O for those aliased PCs to qVoIP

Great!!! Thanks , I will look at it.

Ok, seems that I won't get any further help here. I did remove the Shaping yesterday as I was doing some more testing and realized that p2p traffic now was able to consume 50Mbit fine, while with shaping I only got 20 Mbit, so there is either something completely wrong in my setup/logic, or .. don't know ? If anyone can shed some light into this, it would be much appreciated.

It's a bug as far as I can tell.  I see the same thing, as do others.  It seems to happen for me most when I manually refresh the view with F5.