Re: [pfSense-discussion] Traffic shaper bug ?
What should I say, thanks to Ermal and to the core pfSense team ! Is there already a release date for the 1.3 ? I'm also taking beta... :-) Daniele Chris Buechler wrote: Ermal Luçi wrote: Expected behaviour. Since ALTQ shapes on outgoing that shapes every thing that goes through the interface where the shaper is enabled. For 1.2, it should be noted. For 1.3, Ermal has done a nice job completely rewriting the traffic shaper to accommodate these kinds of situations and more. The traffic shaper in 1.2 only works properly with two interface setups (LAN and WAN). -- regards - Daniele Guazzoni Senior Network Engineer, CCNP, CCNA Linux and AMD-x86_64 or do you still with Windows and Intel ? -- This message has been scanned for viruses and dangerous content by MailGate, and is believed to be clean.
Re: [pfSense-discussion] Traffic shaper bug ?
Chris Buechler wrote on 21-3-2008 23:22: For 1.3, Ermal has done a nice job completely rewriting the traffic shaper to accommodate these kinds of situations and more. The traffic shaper in 1.2 only works properly with two interface setups (LAN and WAN). Right now I'm running traffic shaping on an extra pfSense box, just to avoid this multi interface issue. Planning to move away to a bare FreeBSD/PF/ALTQ setup because of this, would prefer to stay with pfSense however. Do you have any clue when the new features become available? One suggestion: give us an option to bypass this annoying traffic shaping wizard. I know it's possible to delete the generated setup once the wizard has completed, but that's not really nice for those who cannot use the standard setup. Another suggestion: it would make a real difference if it were possible to make rules without specifying *both* the incoming and outgoing interface. ALTQ has that option, so perhaps you are planning that already. best regards, Jan Hoevers
Re: [pfSense-discussion] Traffic shaper bug ?
Ermal Luçi wrote: Expected behaviour. Since ALTQ shapes on outgoing that shapes every thing that goes through the interface where the shaper is enabled. For 1.2, it should be noted. For 1.3, Ermal has done a nice job completely rewriting the traffic shaper to accommodate these kinds of situations and more. The traffic shaper in 1.2 only works properly with two interface setups (LAN and WAN).
