From: Arthur van Leeuwen arthurvl@sci.kun.nl
To: lartc@vger.kernel.org
Subject: [LARTC] Queueing and BGP
Date: Thu, 02 Nov 2000 08:20:11 +0000 [thread overview]
Message-ID: <marc-lartc-98373938216883@msgid-missing> (raw)
In-Reply-To: <marc-lartc-98373938216879@msgid-missing>
<PRE>On Wed, 1 Nov 2000, bert hubert wrote:
><i> On Wed, Nov 01, 2000 at 01:24:09PM -0300, Aldrin Martoq A. wrote:
</I>><i>
</I>><i> > So, It doesn't make sense to mark packet (C) because it will never go to
</I>><i> > the local network and I cannot control that bandwidth, because I just
</I>><i> > receive it. And also It doesn't make sense to mark packet (D) because
</I>><i> > SQUID will eat all the bandwidth with packets (B) and (C) anyway.
</I>><i>
</I>><i> Because squids repackets your data, any shaping information is lost. Once
</I>><i> your data has left squid, there is no way to know anymore where it came
</I>><i> from.
</I>
><i> You can try to get the ingress policer working, which tries to do shaping on
</I>><i> the receiving interface (before squid). This should work, except that people
</I>><i> have been having trouble with the ingress policer.
</I>
Or, alternately, you might try to configure one squid per bandwith-partition,
thereby getting back your shaping information. This does come at a cost, but
it is actually relatively easy to set up. You might need NAT to do it
though... ;)
Doei, Arthur. (Yaay, coding shaping information into IP addresses... ;))
--
/\ / | Fight Scientology, See URL: <A HREF="http://xenu.xtdnet.nl/">http://xenu.xtdnet.nl/</A> |
/__\ / | Buttons. Lotsa buttons. I like buttons. [Big Dog] |
/ \/__ | A friend is someone with whom you can dare to Be yourself. |
Just Be +-Arthur van Leeuwen, <A HREF="mailto:arthurvl@sci.kun.nl------------------------+">arthurvl@sci.kun.nl------------------------+</A>
</PRE>
next prev parent reply other threads:[~2000-11-02 8:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-01 12:57 [LARTC] Queueing and BGP Gregory
2000-11-01 16:24 ` Aldrin
2000-11-01 17:28 ` bert
2000-11-02 8:20 ` Arthur [this message]
2000-11-02 9:34 ` dancer
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-98373938216883@msgid-missing \
--to=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.