I have not had a chance to load this yet.  I did find an error in the system log related to the traffic shaping though.  It is listed below.  I will load the update after everyone leaves today.  Are there any special steps to take after loading the update tarball?


php: : There were error(s) loading the rules: pfctl: real-time sc exceeds 80% of the interface bandwidth (491.52Kb) /tmp/rules.debug:34: errors in queue definition pfctl: Syntax error in config file: pf rules not loaded - The line in question reads [ real-time sc exceeds 80% of the interface bandwidth (491.52Kb) /tmp/rules.debug]:


Robert

On Tue, 2006-02-21 at 14:19 -0500, Scott Ullrich wrote:
http://www.pfsense.com/~sullrich/1.0-BETA1-TESTING-SNAPSHOT-2-20-06/
if you are running a full version, there are a couple of other testing
directories in ~sullrich with other versions (embedded, etc).

On 2/21/06, Robert Goley <[EMAIL PROTECTED]> wrote:
>  I care and will test.  I will be using it at this site and testing it for
> my Vonage line at home too.  what version would you like tested?
>
>  Robert
>
>
>  On Tue, 2006-02-21 at 13:10 -0500, Scott Ullrich wrote:
>  As far as we know yes. Bill has put out repeated pleas for testing
> and feedback but nobody seems to care.
>
> Scott
>
>
> On 2/21/06, John Cianfarani <[EMAIL PROTECTED]> wrote:
> > So is the traffic shaper working correctly now for voip in the latest
> > snapshot?
> >
> > Thanks
> > John
> >
> > -----Original Message-----
> > From: Bill Marquette [mailto:[EMAIL PROTECTED]]
> > Sent: Tuesday, February 21, 2006 12:28 PM
> > To: support@pfsense.com
> > Subject: Re: [pfSense Support] Traffic Shaper hints needed.
> >
> > You've horribly butchered bits vs bytes. Everything in the shaper
> > wizard is in bits. A 6Mb connection is 6Megabits, not 6MegaBytes,
> > hence the 600KByte download (notice the conversion I did?) FYI, if
> > you have 5 lines, you probably want to reserve 5 x line rate - if line
> > rate is 96Kb/sec then you want 480Kb (or whatever setting above that
> > is close - say 512Kb) for the reservation. That will allow all 5
> > lines to be talking at the same time.
> >
> > --Bill
> >
> > On 2/21/06, Robert Goley <[EMAIL PROTECTED]> wrote:
> > > I have a pfsense firewall setup that I am trying to prioritize Vonage
> > VOIP
> > > traffic. I am replacing a M0n0wall firewall that had some traffic
> > shaper
> > > config setup for the Vonage routers. I have 3 Vaonge routers carrying
> > 5
> > > phone lines across a 768KB/6MB (UP/DOWN) cable modem connection. I
> > may be
> > > making this harder on myself than it really is but I am not sure what
> > values
> > > to put where. I know that as a rule of thumb you only get %10 of the
> > > advertised bandwidth. For example, I have a 6 MB download speed but
> > only
> > > get about 600kb/s download rate from extremely fast servers. Vonage
> > > advertizes 90kb/s bandwidth usage per line. This is actually a
> > 8-10kb/s
> > > upload/download rate. When using the traffic shaper wizard, I can
> > specify
> > > the provider and optionally a IP address or alias. I chose Vonage and
> > an
> > > alias that includes all 3 routers. The next itme is reserved
> > bandwidth for
> > > VOIP. I don't know what I need to put here. Is it the advertised
> > speed
> > > 768KB or 76KB/s? I don't want to accidentally assign more bandwidth
> > than I
> > > have since that renders the traffic shaper useless. I did not have
> > major
> > > problems with my VOIP traffic with the M0n0wall. Since switching, I
> > have
> > > had quite a bit of broken voice etc. Could someone drop me a couple
> > of
> > > hints on this? I am using the 2-8-06 version from sullrich.
> > >
> > > Robert
> >
> >
> ---------------------------------------------------------------------
> > 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]
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to