All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kenneth Kalmer <kenneth.kalmer@gmail.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] [OT] Shaping and squid question
Date: Wed, 04 May 2005 21:00:11 +0000	[thread overview]
Message-ID: <fad9d48405050414002e49f5ff@mail.gmail.com> (raw)
In-Reply-To: <fad9d48405050404258b1b67@mail.gmail.com>

On 5/4/05, Andreas Klauer <Andreas.Klauer@metamorpher.de> wrote:
> On Wednesday 04 May 2005 13:25, Kenneth Kalmer wrote:
> > Does this mean that squid recieves the data at full speed and then
> > struggles to pass the data to the client who is shaped, thus becoming the
> > bottle neck?
> 
> If you shape everything on eth0 down to dialup speeds, including pure LAN
> traffic, then the answer is yes, you have an unnecessary bottleneck there,
> because the traffic caused by squid on ppp0 is not shaped at all.
> 
> I'm assuming that squid traffic looks like locally generated traffic to
> iptables/QoS. I don't really use squid, so I can't check.

Though so. squid traffic does look like locally generated traffic for
the shaping, but I shape by marking packets so squid's return data to
the client is also properly marked and shaped together with the other
protocols not handled by the transparent squid...

Here comes my first experiences with IMQ...

Thanks for the confirmation!

> 
> HTH
> Andreas
> _______________________________________________
> LARTC mailing list
> LARTC@mailman.ds9a.nl
> http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
> 


-- 

Kenneth Kalmer
kenneth.kalmer@gmail.com
http://opensourcery.blogspot.com
_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc

      parent reply	other threads:[~2005-05-04 21:00 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-04 11:25 [LARTC] [OT] Shaping and squid question Kenneth Kalmer
2005-05-04 12:47 ` Andreas Klauer
2005-05-04 21:00 ` Kenneth Kalmer [this message]

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=fad9d48405050414002e49f5ff@mail.gmail.com \
    --to=kenneth.kalmer@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.