I wanted to comment on this one specifically as there are certain limitations.
I'll donate $75, if the new traffic shapper support the following:
- shapping an all interfaces
Consider this on the list. I'm struggling trying to figure out how to implement this in HEAD with the new bridge infrastructure (you can bridge more than two interfaces...essentially making a firewalling switch)
- shaping traffic inside individual IPSEC tunnels, that is tunnels terminating at the local pfsense box.
This may not be possible. ALTQ works outbound on the interface. While we could in theory shape the traffic coming _in_ to your network via the tunnel (assuming you aren't doing tunnel to tunnel routing), the best we could do for outbound is shape the entire tunnel. The traffic is already encrypted by the time it hits the WAN interface and can't be inspected to see what ports it's on.
I might be able to donate more if it will be somehow possible to route traffic depending on the amount of traffic queueing. What I mean, is something like this:
Route everything through IPSEC tunnel X on Interface 1, prioritise VoIP. If there isn't enough bandwidth available, route everythoing except VoIP through Interface 2 instead of Interface 1.
Hmmm, that digs into kernel space that I don't think I can modify in a satisfactory way.
--Bill