Traffic shaper changes [90% completed, please send money to complete bounty]
-
bill the changes you are proposing sound very interesting. if interfaces could be extended to support all the ng interfaces loaded on the pppoe server we have another 200 for your bounty.
it can nearly do it now. with a bit of a hack to it but gets it's white spacings wrong.
would you think this is supportable in the multiple interfaces area of your plan
I think so - do PPPOE server interfaces show up as individual interfaces in the Rules (or even interfaces) screen? I'm thinking it doesn't, but I haven't really seen how the PPPoE server works either. I'll try and spend some time tonight, I agree, it's likely possible, but I don't know enough about how that section of code works to be able to say for sure. If it comes up as individual interfaces that rules can be created on, then I'm reasonably confident that it'll "just work".
–Bill
-
Only major problem is ngX is dynamic. The ordering may shift.
-
Only major problem is ngX is dynamic. The ordering may shift.
Good point. Although I don't think ngX necessarily has to be dynamic. But making major interface changes, while on my own personal list of things to do, aren't necessarily compatible within the scope of this change. If these are truly dynamic and not tied to the standard rules editor, then I don't think we'll be able to make it part of this change. Although this change should set the stage for this feature in the future.
–Bill
-
Nope, its not associated unfortunately.
-
ok that was confusing could you clarify these points.
is it possible?
would you include it?
all i am trying to do is hfsc with them no other gaurentees all have equal preferance.well look forward to the clarification
-
ok that was confusing could you clarify these points.
is it possible?Possible, yes. With the current way interfaces are configured, no. The shaper changes I'm working on won't directly help here, but would be considered a prereq to being able to do this.
would you include it?
One thing at a time :) If PPPoE server 'nics' (all the ng interfaces) were already individually assignable for rule management in pfSense, you'd get the shaper changes "for free" so to speak. The changes I'm looking at would just come along for the ride. As it sits, I'd consider this a different project, but one that relies on this change before it can be seriously thought of. Depending on how the code ends up getting written, it may be possible to hack up a config.xml that'll create the correct rules - not sure, I'm still researching the proper way to do the queues as it is (it's looking like we'll have a number of nasty recursive loops).
all i am trying to do is hfsc with them no other gaurentees all have equal preferance.
well look forward to the clarification
Hope that helps.
–Bill
-
Not sure that we can accept Pakistan funds without Big Bubba getting down and angry with us.
-
i too would be willing to throw some money your way for this, however seeing as I'm pretty close to broke it wouldn't be much.
-
I'll donate $100. Let me know when you need it.
-
Just sent in $100 to Paypal…while I would like you to consider it part of this bounty, please use it as/when the project needs...you've earned it with or without a multi-interface traffic shaper!
-
Bill what paypal account do i send my donation to?
-
ok that was confusing could you clarify these points.
is it possible?Possible, yes. With the current way interfaces are configured, no. The shaper changes I'm working on won't directly help here, but would be considered a prereq to being able to do this.
would you include it?
OK i think i understand what are the overall thoughts on this. should i start up a bounty on it.
we use pppoe server for all our wireless concentration. if this change looks achievable outside of the shaper scope i will make a bounty for it.maybe you or scott can clarify the scope of the change a little more clearly and i can brief it
One thing at a time :) If PPPoE server 'nics' (all the ng interfaces) were already individually assignable for rule management in pfSense, you'd get the shaper changes "for free" so to speak. The changes I'm looking at would just come along for the ride. As it sits, I'd consider this a different project, but one that relies on this change before it can be seriously thought of. Depending on how the code ends up getting written, it may be possible to hack up a config.xml that'll create the correct rules - not sure, I'm still researching the proper way to do the queues as it is (it's looking like we'll have a number of nasty recursive loops).
all i am trying to do is hfsc with them no other gaurentees all have equal preferance.
well look forward to the clarification
Hope that helps.
–Bill
-
Bill what paypal account do i send my donation to?
paypal at chrisbuechler.com if you want pfSense to hold onto it until I'm done, or billm at pfsense.org if you wish to send it direct to me sooner.
–Bill
-
Aldo, didn't see any content in that post…did I miss something?
--Bill
ok that was confusing could you clarify these points.
is it possible?Possible, yes. With the current way interfaces are configured, no. The shaper changes I'm working on won't directly help here, but would be considered a prereq to being able to do this.
would you include it?
OK i think i understand what are the overall thoughts on this. should i start up a bounty on it.
we use pppoe server for all our wireless concentration. if this change looks achievable outside of the shaper scope i will make a bounty for it.maybe you or scott can clarify the scope of the change a little more clearly and i can brief it
One thing at a time :) If PPPoE server 'nics' (all the ng interfaces) were already individually assignable for rule management in pfSense, you'd get the shaper changes "for free" so to speak. The changes I'm looking at would just come along for the ride. As it sits, I'd consider this a different project, but one that relies on this change before it can be seriously thought of. Depending on how the code ends up getting written, it may be possible to hack up a config.xml that'll create the correct rules - not sure, I'm still researching the proper way to do the queues as it is (it's looking like we'll have a number of nasty recursive loops).
all i am trying to do is hfsc with them no other gaurentees all have equal preferance.
well look forward to the clarification
Hope that helps.
–Bill
-
Just wanted to update the thread. I'm still working on this, had some issues with some of the new gui libraries that we needed to get fixed as well as some VM issues that are now resolved. I'm hoping to spend some time during my vacation to get a new wizard completed which should allow me to generate configs that I can use to create the backend :) Due to the use of the new gui library, I can pretty easily say that this won't appear in the RELENG_1 branch at all, but I'll attempt to backport it for those that have pledged and donated for this so it can get tested and have some eyes on it earlier (and of course so you can have a new toy :)).
–Bill
-
Thanks Bill.
I have a request: could you make the wizard optional please?
I realize that altq is really difficult to understand, but sometimes you just want to set things up yourself. This is especially true when you are trying to learn about the software.
-
@sai:
Thanks Bill.
I have a request: could you make the wizard optional please?
I realize that altq is really difficult to understand, but sometimes you just want to set things up yourself. This is especially true when you are trying to learn about the software.
The wizard is already optional. I do plan on making the manual configuration a little more reliable and less prone to easy breakage (the real problem) though.
–Bill
-
Hey Bill mind if I chip in on this project? I'm finding more free time on my hand these days, so I'm specifically interested in helping with transparent shaping and investigating the muliwan/multinterface shaping of altq.
-
Hey Bill mind if I chip in on this project? I'm finding more free time on my hand these days, so I'm specifically interested in helping with transparent shaping and investigating the muliwan/multinterface shaping of altq.
You might check out http://wiki.pfsense.com/wikka.php?wakka=NewShaperNotes. I think I can handle bridge, and multi-lan w/out too much problem. Multi-wan is going to be a tad more challenging I think.
–Bill
-
Hey Bill mind if I chip in on this project? I'm finding more free time on my hand these days, so I'm specifically interested in helping with transparent shaping and investigating the muliwan/multinterface shaping of altq.
You might check out http://wiki.pfsense.com/wikka.php?wakka=NewShaperNotes. I think I can handle bridge, and multi-lan w/out too much problem. Multi-wan is going to be a tad more challenging I think.
–Bill
cool, I'll experiment with altq and multi-wan shaping and update the wiki with my findings and ideas. Off the bat though I'm not sure if this can be done without modifying altq itself. Also I'll experiment with the ideas you currently have to see if I can add any additional info. What about transparent/l7 shaping? have any ideas or wiki entry on that? I have a few idea's I'd like to share on that, I probably make a wiki entry once I setup a testing platform this weekend and put together some notes.