See http://wiki.pfsense.com/wikka.php?wakka=HFSCBandwidthShapingNotes for a tom&jerry example  ;D Also http://forum.pfsense.org/index.php/topic,1384.0.html might be interesting

This night I test and then I tell you. THANKS

sullrich, many thanks for your reply. I will have to change NICs.

Thank you kindly, No voipers yet, maybe in the future I can dedicate a pipe to such critical services. For now I think I will try and hope I do not fail miserably.

Please upgrade to http://pfsense.com/~sullrich/RELENG_1_SNAPSHOT-07-12-2006/

I guess you will only see traffic in the voip queues at the end the traffic enters the tunnel. If you have set it up at both ends it might work as expected as the other end already sorted the packages. Note the might. You should assign higher priority for IPSEC traffic too at both ends btw. I still have to set this up in a real live environment to test out myself. We are evaluating a voipsetup soon at the office with 3 WANs from 3 different ISPs and VPNs. Additional to this there will be 3 other locations joining. I'll do some tests with this scenario.

Traffic shaping does not work with bridging currently.

No.  The system is working as designed.  We do not support editing of queues, we only support the default generated traffic shaper configuration.

Unfortunately creating a rules/queues for every single client is the only way it can be done right now with pfSenses shaper if you want to shape per IP. Concerning the wireless special settings I would do some throughput tests to know what limits you should set for the root queues and maybe be a bit conservative substracting a bunch of kbit/s from what you get to end up with good quality. The connection limit can be done with the advanced options of firewall rules. Just edit a rule and you find them in the middle of the page.

1. run cvs_sync.sh releng_1 from a shell prompt 2. create an alias named phones and stick the internal private ip AND the public ip of your provider into the alias 3. run traffic shaper wizard and on the voip screen type phones into the red box. Now it should account for the phone correctly.

Upgrade to RC1.  Follow the tips in the traffic shaper thread.  Search the forum for p2pCatchAll.

1.0 RC1 is now out, you may want to try it.

http://wiki.pfsense.com/wikka.php?wakka=HFSCBandwidthShapingNotes

Thanks you all for the answers, i will try this and let you know if it works. Thanks a lot again!!

Beta 4 has major issues.  If you are not cvs_sync.sh releng_1 your copy then it's broken on beta4.

The rest of the stuff I had already checked on, but somehow I neglected to do a recent speed test. Sure enough, the line tested at 230 Kb up, not the 256 I used to be getting when I checked it a couple months ago. After adjusting that, everything seems to be running a lot smoother. Thanks for the advice!

either at diagnostics>command or at the local shellmenu or ssh after exiting it with option 8.

@bruor: i also had this bug,  noticed that i was getting drops on my voip phone, and that things were not going into the voip outbound queue,  i have run the cvs sync to releng_1 and will post results here in the next day or so. You also need to rerun the traffic shaper wizard.

FAQ. http://faq.pfsense.com/index.php?action=artikel&cat=10&id=97&artlang=en&highlight=per%20user