pfSense is not based linux. It's based on FreeBSD. No you cannot shape directly based on MACs. However what you can do: create static IP <–> MAC pairings. Like this you can make sure that a MAC always has the same IP.

Let us know.  If it is an outbound BW shaping issue, there are posts here that address this.

@danswartz: The default location for these is in sip_general_additional.conf, but you tweak them in sip_general_custom.conf.  Like this: tos_sip=0 tos_audio=0 NB: this is for a freepbx-based system.  If yours is not, you need to figure out where to set these for your setup. Been looking for this solution for a long time. Thanks. Im on the PBXInAFlash asterisk flavor….

i made this post about year ago referencing an older post with the same issue with no resolution, never got a reply. hope you have better luck

I'm confused.  If the two computers are on the same subnet, the pfsense should not even be involved.  Can you describe your network topology more clearly?

@daftaronline: There were error(s) loading the rules: pfctl: real-time sc exceeds 80% of the interface bandwidth (51.20Kb)/tmp/rules.debug:23: errors in queue definition pfctl: real-time sc exceeds 80% of the interface bandwidth (416Kb) /tmp/rules.debug:24: errors in queue definition pfctl: Syntax error in config file: pf rules not loaded – The line in question reads [ real-time sc exceeds 80% of the interface bandwidth (51.20Kb) /tmp/rules.debug]: … when i enter trafic shaping wizard and click finish i get that warning. please help me… thx Obviously you have set some initial values that are not possible. As you see, realtime traffic can only exceed 80% of interface bandwidth. Try using percentage values. BR, Tommi

@pippolini: Same as above…. can anyone help us out here? i want to donate to the project in exchange for the new bounty. i tried running 2.0 BUT, i cannot migrate my 1.2.3rc1 over to it. even tried restoring only certain sections. please, all i need is the new shaper on the more stable RC.

I've got about 2700kbit/s of downstream (after overheads) to go around 36 clients.  :-[  Let's not even consider upstream. Gaming traffic is actually quite minimal (<30Kbit/s per client; more if the client is a game host) It's a matter of managing the other services (web surfing, streaming youtube/ tagged videos etc) so that they can't saturate the line.  Line saturation is a big culprit in making latencies skyrocket. Since most of the services being capped either use TCP (able to re-transmit, responds to ECN) or have buffers (streaming videos), dropping the packets on the downstream to force the source to throttle back actually works remarkably well. Comparatively, most online games use UDP (TCP is used only for authentication) and don't have netcode optimized for lag compensation and interpolation (like Halflife engine), dropping/ limiting the packet stream is out of the question.

Glad to be of help.  ;D  I kind of totally forgot about the queues being tagged to in/ out interfaces.  ::)

Check the wizard again, I am pretty sure you can whitelist an IP or somesuch.