Traffic shaper changes [90% completed, please send money to complete bounty]
-
Yes, it is completed. Only cosmetics issues and some wizards are left. In addition there will be an addition requested by Heiko for IPSec.
Just the people that pledged here have not.
-
Gotcha. Thanks, I'll be sending that money in shortly.
-
Other than money is there anything I can do to help this process along ?
I have a pretty large deployment and decent traffic, I would be more than happy to help test if it would help. I also have a few php guys i could bring in to help.
-
sorry if it has been mentioned before but is this going as a package into 1.2RCX?
-
sorry if it has been mentioned before but is this going as a package into 1.2RCX?
Doubtful. We will make a custom version available to those who have donated so far but due to the fact that a lot of people have stiffed this bounty we will NOT be making a general version available for everyone.
If you happen to know one of the bounty contributors you might convince them to let you have the custom version when we release it but if I was them I would say no.
This entire ordeal is going to force us to change how we do future bounties. Money will be required UP FRONT before any work starts.
-
Can I make a donation of a couple hundred bucks and be able to get this update?
-
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.
Second, we do not have a absolute release date for this custom version but can say it will be in the next 2-3 weeks after 1.2 is released.
If you are still interested send the donation to Chris Buechlers paypal account which is listed in the donations section of the website and please make sure you put "Traffic Shaper Bounty" somewhere in the description so we can remember who donated to this cause.
Thanks everyone that has donated so far.
-
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.
Second, we do not have a absolute release date for this custom version but can say it will be in the next 2-3 weeks after 1.2 is released.
If you are still interested send the donation to Chris Buechlers paypal account which is listed in the donations section of the website and please make sure you put "Traffic Shaper Bounty" somewhere in the description so we can remember who donated to this cause.
Thanks everyone that has donated so far.
Great. I'll get the IT Director to send you guys some money.
-
So this will be never integrated in pfSense for any users? neither in version 1.3?
-
No it will appear in 1.3. But 1.3 is a LOOOOOOONG way off.
-
Is there a ballpark ETA for 1.2? I'm redesigning our entire network and want to use it with the new traffic shaping as our edge firewall.
-
Would this help with load balancing incoming connections? What about balancing outgoing connections to which ever connection has the least usage?
If it can help with my project I'll consider donating $100.
-
Would this help with load balancing incoming connections? What about balancing outgoing connections
You can shape such setups.
to which ever connection has the least usage?
This is not a shaper decision. This is the load balancer option.
But you might create another bounty for creating such a feature. -
Hi,
Is ~50$ enough to get this custom version? It's important for me because i'm providing internet access for free (non-profit ISP). And i don't have much budget. -
I don't know if this can be done with pfsense now or with the new custom patch you are developing.
The question is if it's possible to create different groups or classes in the local users and to assign them different bandwith. For example you have a wireless network and clients can access through de captive portal, with dhcp, and i would like to create a gold client class, silver and bronze, and assign 1MB, 512 KB and 256 KB to each download rate.
I think this is not possible now, but i don't know if that would suit in this bounty or for a new one.
Thanks for your time and work.
-
The question is if it's possible to create different groups or classes in the local users and to assign them different bandwith. For example you have a wireless network and clients can access through de captive portal, with dhcp, and i would like to create a gold client class, silver and bronze, and assign 1MB, 512 KB and 256 KB to each download rate.
I think this is not possible now, but i don't know if that would suit in this bounty or for a new one.
It can be accomplished sort of right now.
But to fullfill your exact requirements it would really be a new bounty to keep things clean.
It is on my schedule and a bounty would speed things up cause i have the ground work for this mostly done.Although i would like to see this changes come with the propper captive portal changes and people gather up on a bounty for extending captive portal!(Again as a matter of pushing things).
-
OK so if I can scrape together like $200:
-
Will I get a package that I can install on 1.2 once it goes final ?
-
Will anyone be able to provide basic support if I cant get it to work ?
-
Will it get updated if updates of pfsense before 1.3 break it or will I be stuck on the same version of pfsense that it was originally written to work on ?
-
Will it get updated with general bug fixes ?
-
Can I send the patch to friends ? What about posting it on my blog ? What is the license of this package going to be ?
-
-
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.
-
I'm also interested in the traffic shapping in IPSec tunnel. So I sent $100 to Chris Buechlers paypal account today.
Thank you.
-
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