From: Stef Coene <stef.coene@docum.org>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] About HTB , bandwidth limiting for ftp port...
Date: Fri, 14 Mar 2003 21:52:42 +0000 [thread overview]
Message-ID: <marc-lartc-104767883612084@msgid-missing> (raw)
In-Reply-To: <marc-lartc-104759525429091@msgid-missing>
On Friday 14 March 2003 05:19, Dhirendra Pal Singh wrote:
> Hi Martin,
>
> First of all thanks for the info.
> Now among all the links you have sent I think, the one which says about
> using the helper and mark the packets will be the one which will best do
> the job.
>
> So I think what you are pointing to, is that mark all the ftp packets
> (control and data) with a specific mark and then do bandwidth policies
> on the basis of that mark.. is that right Martin?
>
> Also I ran ethereal for further analysis. To my surprise ethereal showed
> FTP-DATA in front of the data which is captured by it duing ftp
> transactions.? Any idea how did ethereal found that out ??
>
> Thanks for helping and anticipation
> Dp
>
> PS.. In one of my previous querries you had asked about the idea of FAQ.
> I am totally for it...
I covered the subject on www.docum.org on the faq page :)
Stef
--
stef.coene@docum.org
"Using Linux as bandwidth manager"
http://www.docum.org/
#lartc @ irc.oftc.net
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
next prev parent reply other threads:[~2003-03-14 21:52 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-13 22:55 [LARTC] About HTB , bandwidth limiting for ftp port Dhirendra Pal Singh
2003-03-14 2:37 ` Martin A. Brown
2003-03-14 3:00 ` Jack Bowling
2003-03-14 4:19 ` Dhirendra Pal Singh
2003-03-14 21:52 ` Stef Coene [this message]
2003-03-15 0:16 ` Dhirendra Pal Singh
2003-03-15 10:41 ` Stef Coene
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-104767883612084@msgid-missing \
--to=stef.coene@docum.org \
--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.