Just out of curiosity, are those with problems tagging packets for
some VOIP queue based on the IP address of the VOIP device(s)? I
believe I recall an issue in the shaper incorrectly tagging data if a
rule was created to match all traffic from a particular source
address. This code in shaper.inc was the culprit:
/* source address */
/* Using any for source on 'out' is due to not knowing what
* the packet looks like after NAT occurs
*/
if (isset($rule['source']['any']) || $direction == "out") {
$src = "any";
I recently moved and haven't gotten a chance to setup my pfsense
computer again, but I believe this was the only outstanding issue I
encountered with the shaper.
On 1/21/06, Bill Marquette <[EMAIL PROTECTED]> wrote:
> Shaper is still being worked on. I'd be surprised by anyone reporting
> that it works good.
>
> --Bill
>
> On 1/21/06, Forrest Aldrich <[EMAIL PROTECTED]> wrote:
> > John Cianfarani wrote:
> > > I have the same issue when using the shaper. I am using generic Asterisk
> > > VoIP traffic.
> > > I as soon as I enable the traffic shaper I get the cutting in an out and
> > > as soon as I disable it (even in the middle of a call) it is normal.
> > > In my tests there is no other traffic on the line other than voip.
> > > I thought it was still being worked on that's why I never reported
> > > anything.
> > >
> > > Thanks
> > > John
> > >
> > >
> >
> > This concerns me, too, as I'll be using VoIP shortlly - and if this
> > isn't working, then I cannot use PFSense.
> >
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, e-mail: [EMAIL PROTECTED]
> >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
