Traffic shaper changes [90% completed, please send money to complete bounty]

eri--

@eri--:

What it can do:
1- Supports CBQ, HFSC, PRIQ schedulers whith any combination of them on any number of interfaces. To suit any strange environment.
2- You can shape
Bridge, PPTP, PPPoE, OpenVPN or tun devices, IPSec incoming, Overall IPSec tunnels, L2TP, or any other device/software that does IP traffic in a distinguishable way.
3- You can create policy filtering as there is a new tab which allows expressing a late match syntax with support for tagging and matching on tags(i call them marks in the GUI), directions. Simple allows one PF expert to do policy filtering.
4- The queues are specified in each rule you create, there is no more a rules tab on the shaper section. This makes things cleaner and easier to manage.
5- You can shape/override DHCP, DNS, or any default policy of pfSense by just creating rules from the GUI.
6- The easiest way to create a policy for multiple interface shaping and filtering, at least in contrast with what i have used.
7- [Is on its way] Multiple wizards to use on different environments.

Requirments:
1- Know how.
Meaning you should know what you want then i guarantee it can be done with this new module and the wizards should help on this,

Am i missing anything Scott?!

Adding another feature so it remains as a documentation too:

8- If you have 3 different networks separated from each other and you want to combine to a single centralized management with pfSense and the new shaper, they can be handled/shaped separated or even provide failover for them. Kinda, basic support for different domains.

9- Shaping inside IPSec tunnels works now.

sbyoon

I'm also interested in the traffic shapping in IPSec tunnel. So I sent $100 to Chris Buechlers paypal account today.

Thank you.

craigdrown

Hi,
we've spent a lot of time looking at traffic shaping, and really like the approach of bandwidthabitrator.net, which is to…
... do nothing until pipe is 85% full (user specifiable)
... if > 85% then clamp specific connections that have the highest bytes transferred and longest connection time. (Clamp as in introduce some latency to slow 'em down). This happens pretty quickly and then the process is repeated...
Advantages:
* super easy to set up
* gets the pesky p2p stuff even if on port 80
* allows all users to get lots of bandwidth without the risk of them bogging down other users when it's busy.

pftop already does all the stats for finding the offending connections, it just needs a clever head to work out how to slow down those particular connections.

I realize this is significantly different to existing traffic shaper work, so please make a new thread if approp. We'll donate US$500 up front if someone takes this up.
Thanks,
Craig

sporkme

@sullrich:

@Rich:

Can I make a donation of a couple hundred bucks and be able to get this update?

First of all, absolutely. We really want to get Ermal compensated for all of his hard work.

OK, I never promised anything, and I'm currently one broke bastard. But if people that pledged money in this thread didn't follow through, shame on them!

I just sent $50, I wish it was more. I don't even need this feature nor would I use it for work - I just want to tinker at home, but it irks me that people didn't pony up. I hope everyone that stiffed the devs sleeps well. :P

edit: you'll see my donation from an "@fasttrackmonkey.com" address.

eri--

@craigdrown:

Hi,
we've spent a lot of time looking at traffic shaping, and really like the approach of bandwidthabitrator.net, which is to…
... do nothing until pipe is 85% full (user specifiable)
... if > 85% then clamp specific connections that have the highest bytes transferred and longest connection time. (Clamp as in introduce some latency to slow 'em down). This happens pretty quickly and then the process is repeated...
Advantages:
* super easy to set up
* gets the pesky p2p stuff even if on port 80
* allows all users to get lots of bandwidth without the risk of them bogging down other users when it's busy.

pftop already does all the stats for finding the offending connections, it just needs a clever head to work out how to slow down those particular connections.

I realize this is significantly different to existing traffic shaper work, so please make a new thread if approp. We'll donate US$500 up front if someone takes this up.
Thanks,
Craig

I think the new shaper is superior than this.
Not currently, but for 1.3 will be ready a discipline that does that but better in many ways.

You can do such configuration and people seem pretty happy with it(HFSC). Though you have to identify traffic properly.
If you want to still donate that money i will make sure that a feature to better identify traffic goes in for 1.3.
Which would allow finding P2P and other traffic on any port!

Jonb

Can you name and shame these ungratful people and also say how much you are short by of what the original plegdes are. thanks

heiko

Sorry,
for me!!! "name and shame" is also a bad style.

It is here a pillory? To educate people here is pointless, only the changes of the bounty-system is an option, but this is only my opinion!

Greetings
Heiko

heiko

Hello eri,

1600 $ done! to paypal@chrisbuechler.com

Greetings
Heiko

sullrich

@heiko:

Hello eri,

1600 $ done! to paypal@chrisbuechler.com

Greetings
Heiko

Thanks Heiko!!! I agree, we need to make some changes to the bounty system to prevent this from ever happening again.

eri--

Thank You Heiko for your support.

bogus

Hi all,

I hope we get some compensation for Eri– for his work.

100$ on it's way to paypal@chrisbuechler.com

Carry on this great work.

I hope to see 1.2 and this package soon.

Detlef

ridnhard19

Hi, Eri– will the new shaper support the embedded version before major inclusion with 1.3? If so I'll defiantly throw-in for this. I have a couple embedded pfSense box's including a firebox with 5 ethernet ports and this would be a excellent enhancement.

eri--

Yes.

eri--

Here are some pictures of the new shaper just for completenes and preview.

RELENG_1_interface_view.PNG_thumb

RELENG_1_queue_selection.PNG_thumb

RELENG_1_queues_view.PNG_thumb

RELENG_1_floating_rules.PNG_thumb

RELENG_1_wizards_second_step.PNG_thumb