All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Michael T. Babcock" <mbabcock@fibrespeed.net>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] why shape incoming traffic
Date: Fri, 01 Mar 2002 19:34:07 +0000	[thread overview]
Message-ID: <marc-lartc-101501134529191@msgid-missing> (raw)
In-Reply-To: <marc-lartc-101494774514020@msgid-missing>

On Fri, Mar 01, 2002 at 04:50:10PM +0100, bert hubert wrote:
> > Isn't the usual solution to mark the packets at input and use the
> > marks for shaping?  When is that not adequate?
> 
> Try getting your mark to survive squid.

Of course, one could spend a few months figuring out how to track marks 
within squid so that outgoing requests have the same TCP options set as 
the incoming ones ...

PS, 'months' being estimate based on prior readings of source ...
-- 
Michael T. Babcock
CTO, FibreSpeed Ltd.     (Hosting, Security, Consultation, Database, etc)
http://www.fibrespeed.net/~mbabcock/
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/

  parent reply	other threads:[~2002-03-01 19:34 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-03-01  1:53 [LARTC] why shape incoming traffic Don Cohen
2002-03-01 10:04 ` bert hubert
2002-03-01 15:47 ` Don Cohen
2002-03-01 15:50 ` bert hubert
2002-03-01 19:27 ` Michael T. Babcock
2002-03-01 19:34 ` Michael T. Babcock [this message]
2002-03-01 21:48 ` Don Cohen
2002-03-02 11:16 ` Michael T. Babcock
2002-03-04  5:05 ` Michael T. Babcock
2002-03-04 15:22 ` Don Cohen

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=marc-lartc-101501134529191@msgid-missing \
    --to=mbabcock@fibrespeed.net \
    --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.