From: don-lartc@isis.cs3-inc.com (Don Cohen)
To: lartc@vger.kernel.org
Subject: [LARTC] congestion problem
Date: Fri, 11 Oct 2002 17:49:41 +0000 [thread overview]
Message-ID: <marc-lartc-103435882911172@msgid-missing> (raw)
In-Reply-To: <marc-lartc-103433355114816@msgid-missing>
Client --- R1 --- R2 --- R3 --- Web
the Client it's me, the R1 router it's myne (so i can control it), the
R2 is my provider router, and R3 is the provider,provider router.
R2 - R3 is a 2mbit link
R1 - R2 is a 10mbit link
R2 have multiple interfaces and other 10mbit links
I have a 32kbit garanted bandwidth on the R2-R3, but without limit (rate
32kbit, ceil 2mbit)
You have guaranteed 32K upstream, downstream or both?
There's something strange about that in any case.
For upstream, how does r2 know which packets are from you?
Source address? Then some other customer of your ISP could deny
you service by spoofing your address (unless your ISP filters that).
Downstream is also strange, first cause your ISP's ISP would then
have to know about you, second cause you have little control over what
others send you. So if that is controlled at all it should be
shaped in accordance with your wishes.
You talk about downloading. But in that case the bandwidth is used
mostly downstream. You have limited control over that. Assuming
the servers are using tcp you could control the acks (more to the
point the windows) you send back to limit the rate at which they send
to you.
Of course, 32Kbit is slow enough that you're never likely to be happy
with download speed.
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
prev parent reply other threads:[~2002-10-11 17:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-11 10:49 [LARTC] congestion problem Ciprian Niculescu
2002-10-11 17:49 ` Don Cohen [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-103435882911172@msgid-missing \
--to=don-lartc@isis.cs3-inc.com \
--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.