All of lore.kernel.org
 help / color / mirror / Atom feed
From: bert hubert ahu@ds9a.nl
To: lartc@vger.kernel.org
Subject: [LARTC] Shaping incoming traffic to limit traffic-bills?
Date: Wed, 25 Oct 2000 16:28:21 +0000	[thread overview]
Message-ID: <marc-lartc-98373938216845@msgid-missing> (raw)
In-Reply-To: <marc-lartc-98373938216840@msgid-missing>

<PRE>On Wed, Oct 25, 2000 at 04:20:24PM +0200, Clemens Sibon wrote:
&gt;<i> Hi there,
</I>&gt;<i> 
</I>&gt;<i> I was just thinking.. When I limit my incoming bandwidth to keep the bills
</I>&gt;<i> low (no flat-rate) but the only thing the system does is drop packets, then
</I>&gt;<i> I do have to pay for this traffic since it gets dropped on my side. It does
</I>
Yes. But, as the HOWTO explains, TCP/IP responds to lost packets by slowing
down. If people just stream you lots of packets, you do need to pay.

&gt;<i> however reduce the amount of outgoing traffic, but are there ways to let
</I>&gt;<i> 'the other side' know that I can't handle their traffic instead of just
</I>&gt;<i> dropping it? I know Cisco (and others?) have some things like RED and
</I>&gt;<i> others..
</I>
RED, ICMP Source Quench, ECN all don't do what you want I'm afraid. Simple
per hop networks just don't work like that. You need to shape upstream to be
really sure.

Regards,

bert hubert

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


</PRE>

      reply	other threads:[~2000-10-25 16:28 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-10-25 14:20 [LARTC] Shaping incoming traffic to limit traffic-bills? Clemens
2000-10-25 16:28 ` bert [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=marc-lartc-98373938216845@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.