On Thu, Mar 29, 2007, at 13:52:53 -0400, Scott Ullrich wrote:
> Revisit the traffic shaping wizard, on the "Peer to Peer networking"
> screen check "Lower priority of Peer-to-Peer traffic" and then check
> "p2pCatchAll".
That appears to have fixed it, thanks!
I thought it was setup like that befo
P2PCatch all is not enabled then.
Here is what my host shows:
# php -f test.php
1
Array
(
[step2] => Array
(
[download] => 3000
[upload] => 250
[inside_int] => lan
[outside_int] => wan
)
[step3] => Array
(
[provid
On Thu, Mar 29, 2007, at 12:29:37 -0400, Scott Ullrich wrote:
> Please open Diagnostics -> Command Prompt and in the PHP command box
> type in:
>
> echo isset($config['ezshaper']['step5']['p2pcatchall']);
This didn't return anything.
> And:
>
> print_r($config['ezshaper']);
Array
(
[step2]
On 3/28/07, Mark Kane <[EMAIL PROTECTED]> wrote:
The latest snapshot seems to be the same as the previous one (still
going to qlandef but doesn't seem to affect other traffic much).
1.0.1-SNAPSHOT-03-27-2007
built on Wed Mar 28 21:01:28 EDT 2007
# ps awux | grep pftpx
proxy550 0.0 0.1 6
On Wed, Mar 28, 2007, at 15:49:24 -0400, Scott Ullrich wrote:
> On 3/28/07, Mark Kane <[EMAIL PROTECTED]> wrote:
> > On Wed, Mar 28, 2007, at 14:28:00 -0400, Scott Ullrich wrote:
> > > So you do not have P2P Catch all option enabled?
> >
> > I do, and all other traffic gets caught by it fine. Here
On 3/28/07, Mark Kane <[EMAIL PROTECTED]> wrote:
On Wed, Mar 28, 2007, at 14:28:00 -0400, Scott Ullrich wrote:
> So you do not have P2P Catch all option enabled?
I do, and all other traffic gets caught by it fine. Here are
screenshots of the shaper rules and the queues page with an HTTP
download
On Wed, Mar 28, 2007, at 14:28:00 -0400, Scott Ullrich wrote:
> So you do not have P2P Catch all option enabled?
I do, and all other traffic gets caught by it fine. Here are
screenshots of the shaper rules and the queues page with an HTTP
download going.
http://tntpowerhost.com/mixx941/pfsense_sh
So you do not have P2P Catch all option enabled?
Scott
On 3/28/07, Mark Kane <[EMAIL PROTECTED]> wrote:
On Wed, Mar 28, 2007, at 14:08:48 -0400, Scott Ullrich wrote:
> On 3/28/07, Mark Kane <[EMAIL PROTECTED]> wrote:
> > With the updated snapshot, incoming FTP traffic still goes into the
> > q
On Wed, Mar 28, 2007, at 14:08:48 -0400, Scott Ullrich wrote:
> On 3/28/07, Mark Kane <[EMAIL PROTECTED]> wrote:
> > With the updated snapshot, incoming FTP traffic still goes into the
> > qlandef queue instead of qP2PDown but it doesn't seem to kill the
> > other traffic anymore. Is that what the
On 3/28/07, Mark Kane <[EMAIL PROTECTED]> wrote:
With the updated snapshot, incoming FTP traffic still goes into the
qlandef queue instead of qP2PDown but it doesn't seem to kill the other
traffic anymore. Is that what the change was supposed to do?
Please issue this command from a shell:
ps a
On Tue, Mar 27, 2007, at 19:28:05 -0400, Scott Ullrich wrote:
> I have commited a fix that should solve this problem for you. Please
> try a snapshot about 2 hours after you receive this.
>
> Scott
With the updated snapshot, incoming FTP traffic still goes into the
qlandef queue instead of qP2PD
On 3/27/07, Mark Kane <[EMAIL PROTECTED]> wrote:
Hi everyone.
I've recently noticed that incoming FTP traffic is not being sent to
the proper queue. I have traffic shaping setup per the wizard with VoIP
traffic going to qVOIPUp/Down and a catch-all for everything else
to qP2PUp/Down. For the mos
Hi everyone.
I've recently noticed that incoming FTP traffic is not being sent to
the proper queue. I have traffic shaping setup per the wizard with VoIP
traffic going to qVOIPUp/Down and a catch-all for everything else
to qP2PUp/Down. For the most part this has been working excellent.
Incoming F
13 matches
Mail list logo
