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

@hoba:

my adsl2+ 16mbit/s down, 1 mbit/s up

plots digging a trench and installing network to hoba's house

May be need insert Queue ID - unique field, what create self value only with new Queue?
Value format can be, for example, 'queueXX'
All rules must be use this field for references to this queue.
This really?

Feel free to submit patches against -HEAD to get this included.

Sorry, It was a notice mostly for users not developers.
After syncing with RELENG_1 cvs everything works fine. Outgoing traffic shaping too. Thanks.

Nor can we sync dummynet rules to ALTQ :)  No, this will require significantly more effort.

–Bill

Thks. I shall try several tests

Use it at your own risk, no support will be given, yadda, yadda.

Yes, I understand that this quits of frames of the project.

But i very much need for filtering bridge & shaper
May be there is other way for join 2 subnets one range? Without use the bridge, but filtering and shaping traffic?
This structure to my network
(10.62.0.0/24: 10.62.0.1-inet router + about 10 hosts) <-WAN intf-> pfSense <- LAN intf -> (10.62.0.0/24: all other hosts)
All traffic between left and right subnets can be go without any nat but any protocols i want directing with rules & shaping

Any advice(idea)?

First run the shaper to get a basic config. Then create queues for all the servers with an upperlimit of 5,2,1,2 mbit/s. Add rules that assign each server IP to one of the queues.

To get started "abuse" the voipqueue for one of the servers (enter the Server IP at the VOIP page when running the Wizard). After the wizard has finished uncheck the realtime and add an upperlimit instead to the created voipqueues. Also lowering the priority makes sense. Then create a pair of these rules for each of your servers. Apply the settings and reset states before you test your new config.