All of lore.kernel.org
 help / color / mirror / Atom feed
From: Shanker Balan <shanu@exocore.com>
To: lartc@vger.kernel.org
Subject: [LARTC] Re: Shaping only FTP traffic
Date: Tue, 25 Sep 2001 10:49:09 +0000	[thread overview]
Message-ID: <marc-lartc-100141419921038@msgid-missing> (raw)
In-Reply-To: <marc-lartc-100140813700807@msgid-missing>

Hello:

Ivan Lopez wrote,
> but, because of the above commented behavior of the passive mode, you
> cannot predict which ports will be used by your clients... and i don't
> know any *good* thing for matching accurately this ftp passive
> connections (anyone else here knows how :?)

And that is exactly my problem -  You never know what ports will be
opened for ftp data transfer and hence cannot "catch" them.

Since the FTP data port is unpredictable, what i have temporarily done is
to use a dedicated class of 1.5Mbit solely for HTTP traffic and the
remainder of .5Mbit is used for "other" traffic on a 2Mbit link. This is
not a perfect solution but it makes sure that http traffic is not
affected.

Looks like there is no straight forward solution for shaping FTP traffic
using Linux. How do routers and other traffic management appliances
handle FTP traffic shaping anyway?

Is it possible to use the Iptable's "established,related" functions to
mark FTP data traffic and then use the "fw" classifier on it?

-- 
Emperor Palpatine:
	Everything that has transpired has done so according
	to my design.

_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://ds9a.nl/2.4Routing/

  parent reply	other threads:[~2001-09-25 10:49 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-09-25  8:55 [LARTC] Re: Shaping only FTP traffic Shanker Balan
2001-09-25 10:08 ` Ivan Lopez
2001-09-25 10:49 ` Shanker Balan [this message]
2001-09-25 11:29 ` Daniel Bergqvist
2001-09-25 11:56 ` Ivan Lopez
2001-09-25 12:43 ` Shanker Balan

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-100141419921038@msgid-missing \
    --to=shanu@exocore.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.