From: Martin Devera <devik@cdi.cz>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] am i on the right track ?
Date: Mon, 14 Jan 2002 12:52:31 +0000 [thread overview]
Message-ID: <marc-lartc-101101278821609@msgid-missing> (raw)
In-Reply-To: <marc-lartc-101099113808821@msgid-missing>
I don't understand it .. 256kbit = 32kbps. Why
do you use 64kbps !?
On Mon, 14 Jan 2002, Chandrashekhar Joshi wrote:
> yes it is 64kbps (actually it is 256kbits so i suppose that works out to
> 64kbps right)
>
> thanks
> regards /shekhar
>
> Martin Devera wrote:
>
> >I have not too much time to read it just now. But just wondering
> >if you really want 64kbps or rather 64kbit ?
> >devik
> >
> >On Mon, 14 Jan 2002, Chandrashekhar Joshi wrote:
> >
> >>hi,
> >>
> >>i am trying to have bandwidth shaping on my linux router.
> >>i have a 64kbps link, on which i want to restrict the link use for http
> >>
> >....
> >
> >>MAIN LINK = 64kbps
> >>CLASS A = 24kbps (for HTTP/ FTP and other internet related activities )
> >>CLASS B = 40kbps ( reserved for PPTP-VPN access incoming and outgoing)
> >>
> >
> >
> >
> >
>
>
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://ds9a.nl/lartc/
next prev parent reply other threads:[~2002-01-14 12:52 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-14 1:44 [LARTC] am i on the right track ? Chandrashekhar Joshi
2002-01-14 9:44 ` Martin Devera
2002-01-14 12:38 ` Chandrashekhar Joshi
2002-01-14 12:52 ` Martin Devera [this message]
2002-01-14 12:57 ` Rob Kaper
2002-01-14 13:01 ` Martin Devera
2002-01-14 13:04 ` Rob Kaper
2002-01-14 13:18 ` Martin Devera
2002-01-14 13:57 ` Chandrashekhar Joshi
2002-01-16 9:39 ` Martin Devera
-- strict thread matches above, loose matches on Subject: below --
2002-01-14 14:08 [LARTC] Am I on the right Track? Sahil Gupta - NET4U
2002-01-15 0:52 ` Brendan Alderslade
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-101101278821609@msgid-missing \
--to=devik@cdi.cz \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox