All of lore.kernel.org
 help / color / mirror / Atom feed
From: Aldrin Martoq A. agm@cec.uchile.cl
To: lartc@vger.kernel.org
Subject: [LARTC] Queueing and BGP
Date: Wed, 01 Nov 2000 16:24:09 +0000	[thread overview]
Message-ID: <marc-lartc-98373938216880@msgid-missing> (raw)
In-Reply-To: <marc-lartc-98373938216879@msgid-missing>

<PRE>On Wed, 1 Nov 2000, Gregory Maxwell wrote:
&gt;<i> After seeing that post about directing traffic to various upstream links
</I>&gt;<i> based, basically, on the next-hop from an ISP's router I was wondering:
</I>&gt;<i> Is it possible to queue packets via realm?
</I>[..gated..]

According to the LAR HOWTO (chapter 11.3); yes, it is possible to queue
via realm numbers.

Now, I'm a newbie (1.5 weeks ago just downloaded the LAR HOWTO and don't
understand it 100% right now) and found I have to learn BGP, gated, etc
;-)

Well, my question is: How can I control the BandWidth if you can only
control what you send on the wire? Remember that 99.99% of the traffic is
*download* of web pages, and there is a transparent proxy (with around
20%-50% hit rate on peak hours).
                             ____________
          www.yahoo.com (A) [            ] (B)
          ---&gt;---&gt;---&gt;---&gt;--[&gt;--\    /--&gt;]---&gt;---&gt;---&gt;
 LOCAL NET                  [   SQUID    ]                 OUTSIDE (yahoo)
          ---&lt;---&lt;---&lt;---&lt;--[&lt;--/    \--&lt;]---&lt;---&lt;---&lt;
                        (D) [____________] (C)

Whenever a packet from the local networks try to goes outside (A), it
really never goes outside because it is redirected to SQUID. Then SQUID
send the request packet (B) (which is a diferent packet) and it receives
the packet (C). The packet (C) vanish in SQUID, but it creates a new
packet (D) in response, which is not the same packet as (C).

So, It doesn't make sense to mark packet (C) because it will never go to
the local network and I cannot control that bandwidth, because I just
receive it. And also It doesn't make sense to mark packet (D) because
SQUID will eat all the bandwidth with packets (B) and (C) anyway.

Tell me I'm wrong.

Aldrin.
&quot;So many links, so little time!&quot;



</PRE>

  reply	other threads:[~2000-11-01 16:24 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 [this message]
2000-11-01 17:28 ` bert
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-98373938216880@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.