[pfSense Support] Re: Wrap Embedded 0.89.2: Traffic Shaper error

[w . plein]

My apologies, this appears to be related to the topic "Traffic Shaping, 
killing my DSL link speed to less than 100k"


My 3000/500 line is running 200/20 with my traffic shaping rules enabled (!)

I will turn it off, go back and read that thread in detail.



At 04:33 PM 10/28/2005, Bill Plein wrote:

I upgraded to 0.89.2 on my WRAP embedded (via update, not full install)

When attempting to set up traffic shaping (to see if it worked better than 
prior installs I've tried), I get this:


Warning: Cannot modify header information - headers already sent by 
(output started at /etc/inc/filter.inc:613) in 
/usr/local/www/wizard.php(89) : eval()'d code on line 1


followed by


Either your LAN or WAN interface doesn't support ALTQ. The wizard cannot 
continue.



Then if I go to my Traffic Shaper page, it shows everything that was set 
up by the traffic shaper!


My WRAP interfaces are set up as:

LAN   ->   sis0   ->   192.168.0.1
WAN   ->   sis1   ->   64.142.26.224
OPT1   ->   sis2   ->   (DMZ)

The DMZ is bridged with the WAN

Traffic shaping used to work with WRAP, any ideas?

--
--
Bill Plein


--
[EMAIL PROTECTED] 



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

Re: [pfSense Support] Re: Wrap Embedded 0.89.2: Traffic Shaper error

[Bill Marquette]

On 10/28/05, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
> My apologies, this appears to be related to the topic "Traffic Shaping,
> killing my DSL link speed to less than 100k"
>
> My 3000/500 line is running 200/20 with my traffic shaping rules enabled (!)
>
> I will turn it off, go back and read that thread in detail.

PPPOE?  And erm, I thought you said it didn't work? :)

--Bill

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

Re: [pfSense Support] Re: Wrap Embedded 0.89.2: Traffic Shaper error

[w . plein]

At 05:39 PM 10/28/2005, Bill Marquette wrote:

On 10/28/05, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
> My apologies, this appears to be related to the topic "Traffic Shaping,
> killing my DSL link speed to less than 100k"
>
> My 3000/500 line is running 200/20 with my traffic shaping rules 
enabled (!)

>
> I will turn it off, go back and read that thread in detail.

PPPOE?  And erm, I thought you said it didn't work? :)

--Bill


No, I turned off traffic shaping.

With Traffic Shaping turned ON, I got the error that it wasn't supported 
(but it was, I guess!). You have to go through the wizard to get the error, 
enable/disable on the shaper doesn't trigger it.


With the shaper enabled, I got the same slowdown that the other user was 
experiencing.


In reading the other thread, it sounds like ALTQ got upgraded but not 
picked up in the update, and I need to upgrade via full CF image, correct?


I was reporting one part of the bug (the error message), the other user was 
reporting the other half of the bug (the slowdown).




[EMAIL PROTECTED] 



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

Re: [pfSense Support] Re: Wrap Embedded 0.89.2: Traffic Shaper error

[Bill Marquette]

On 10/28/05, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
> At 05:39 PM 10/28/2005, Bill Marquette wrote:
> >On 10/28/05, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
> > > My apologies, this appears to be related to the topic "Traffic Shaping,
> > > killing my DSL link speed to less than 100k"
> > >
> > > My 3000/500 line is running 200/20 with my traffic shaping rules
> > enabled (!)
> > >
> > > I will turn it off, go back and read that thread in detail.
> >
> >PPPOE?  And erm, I thought you said it didn't work? :)
> >
> >--Bill
>
> No, I turned off traffic shaping.
>
> With Traffic Shaping turned ON, I got the error that it wasn't supported
> (but it was, I guess!). You have to go through the wizard to get the error,
> enable/disable on the shaper doesn't trigger it.
>
> With the shaper enabled, I got the same slowdown that the other user was
> experiencing.
>
> In reading the other thread, it sounds like ALTQ got upgraded but not
> picked up in the update, and I need to upgrade via full CF image, correct?
>
> I was reporting one part of the bug (the error message), the other user was
> reporting the other half of the bug (the slowdown).

Correct, you will need to reflash, the CF updates are PHP only, they
don't include kernel changes.

--Bill

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

Re: [pfSense Support] Re: Wrap Embedded 0.89.2: Traffic Shaper error

[w . plein]

At 07:27 PM 10/28/2005, Bill Marquette wrote:


Correct, you will need to reflash, the CF updates are PHP only, they
don't include kernel changes.


May I suggest that there be Release Notes or other convention (numbering?) 
that indicate when a kernel change has taken place?


I try to keep up with this list, but it's tough at times.

Software development convention would say that release notes go with every 
drop. I happen to work for a software startup (whose product is not yet 
shipping in production!) so I understand that full release notes are almost 
impossible to keep up with.


Anyhow, this is a constructive remark, not a negative one. I'm impressed 
with the changes since I've hopped on board as a user of this project's code.



[EMAIL PROTECTED] 



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

Re: [pfSense Support] Re: Wrap Embedded 0.89.2: Traffic Shaper error

[Scott Ullrich]

Once we release, every version will have concise notes.  We haven't
even made it to beta yet!

Scott


On 10/29/05, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
> At 07:27 PM 10/28/2005, Bill Marquette wrote:
>
> >Correct, you will need to reflash, the CF updates are PHP only, they
> >don't include kernel changes.
>
> May I suggest that there be Release Notes or other convention (numbering?)
> that indicate when a kernel change has taken place?
>
> I try to keep up with this list, but it's tough at times.
>
> Software development convention would say that release notes go with every
> drop. I happen to work for a software startup (whose product is not yet
> shipping in production!) so I understand that full release notes are almost
> impossible to keep up with.
>
> Anyhow, this is a constructive remark, not a negative one. I'm impressed
> with the changes since I've hopped on board as a user of this project's code.
>
>
> [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]