All of lore.kernel.org
 help / color / mirror / Atom feed
From: bert hubert ahu@ds9a.nl
To: lartc@vger.kernel.org
Subject: [LARTC] Queueing and BGP
Date: Wed, 01 Nov 2000 17:28:00 +0000	[thread overview]
Message-ID: <marc-lartc-98373938216882@msgid-missing> (raw)
In-Reply-To: <marc-lartc-98373938216879@msgid-missing>

<PRE>On Wed, Nov 01, 2000 at 01:24:09PM -0300, Aldrin Martoq A. wrote:

&gt;<i> Now, I'm a newbie (1.5 weeks ago just downloaded the LAR HOWTO and don't
</I>&gt;<i> understand it 100% right now) and found I have to learn BGP, gated, etc
</I>&gt;<i> ;-)
</I>
Well no, you probably won't be talking bgp to your 'magic routers', so you
really don't need to know gated.

&gt;<i> So, It doesn't make sense to mark packet (C) because it will never go to
</I>&gt;<i> the local network and I cannot control that bandwidth, because I just
</I>&gt;<i> receive it. And also It doesn't make sense to mark packet (D) because
</I>&gt;<i> SQUID will eat all the bandwidth with packets (B) and (C) anyway.
</I>
Because squids repackets your data, any shaping information is lost. Once
your data has left squid, there is no way to know anymore where it came
from. 

You can try to get the ingress policer working, which tries to do shaping on
the receiving interface (before squid). This should work, except that people
have been having trouble with the ingress policer.

Regards,

bert hubert

-- 
PowerDNS                     Versatile DNS Services  
Trilab                       The Technology People   
'SYN! .. SYN|ACK! .. ACK!' - the mating call of the internet


</PRE>

  parent reply	other threads:[~2000-11-01 17:28 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 [this message]
2000-11-02  8:20 ` Arthur
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-98373938216882@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.