Linux Advanced Routing and Traffic Control list
 help / color / mirror / Atom feed
From: "Eduardo Fernández" <eduardo@cmusanjuan.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Packet loss with htb+sfq+l7filter
Date: Mon, 15 Nov 2004 23:03:33 +0000	[thread overview]
Message-ID: <1100559813.5830.3.camel@laserite> (raw)
In-Reply-To: <1100530341.2796.19.camel@laserite>

Hi Eicke,

But setting up a bridge there'll be another machine routing, so I'll
need ip_forward either way, and I won't avoid the problem if it's really
ip_forward, I will only move it to another machine.

Regards,

Eduardo

El lun, 15-11-2004 a las 23:37 +0100, Eicke Friedrich escribió:
> Hi,
> Eduardo Fernández wrote:
> > (http://kem.p.lodz.pl/~peter/qnet/). When I activate ip_forward I get
> > >20% packet loss and a lot of duplicates. Any ideas? I attach my shaping
> well we've done something similar but instead of using a route we used 
> a bridge (acting as traffic shaper and firewall). So you don't need 
> ip_forward maybe this is worth a try in your setup? In general a box 
> like your should easily handle much more traffic that 4+4MBit/s.


_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/

  parent reply	other threads:[~2004-11-15 23:03 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-15 14:52 [LARTC] Packet loss with htb+sfq+l7filter Eduardo Fernández
2004-11-15 22:29 ` mjoachimiak
2004-11-15 22:30 ` Eduardo Fernández
2004-11-15 22:37 ` Eicke Friedrich
2004-11-15 23:03 ` Eduardo Fernández [this message]
2004-11-16 15:41 ` Andy Furniss

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1100559813.5830.3.camel@laserite \
    --to=eduardo@cmusanjuan.com \
    --cc=lartc@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox