From: Martin Josefsson <gandalf@wlug.westbo.se>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Nearly complettly victory
Date: Sun, 15 Dec 2002 21:31:10 +0000 [thread overview]
Message-ID: <marc-lartc-103998798129184@msgid-missing> (raw)
In-Reply-To: <marc-lartc-103997189019035@msgid-missing>
On Sun, 2002-12-15 at 18:02, David Coello wrote:
> Hi
>
> At last i achive to make QOS works limitting bandwidth per port but with
> one exception : ftp. I don´t know why this port doesn´t works (aplies the
> default rule not the own). Anyone has experience with a similar problem?
Do you know how ftp works?
It uses one control-connection on a static port and dynamic
data-connections. So it's only the control-connection that uses a known
port. It's the data in this control-connection that you probably are
limiting, and this is not what you want.
It is possible to mark all packets that are part of a ftp
data-connection using iptables.
iptables -t mangle -A PREROUTING -m helper --helper ftp -j MARK
--set-mark 1
This will work if you have the ip_conntrack_ftp module loaded or
compiled into your kernel. It will only work for the ports
(control-connection) which ip_conntrack_ftp has been told to listen to.
(default only port 21, change with module option 'ports')
For control-connections on port 21 you use "ftp" to match.
If it's say port 2121 and you've told ip_conntrack_ftp to listen to that
port you should use "ftp-2121" to match.
I hope this helps.
--
/Martin
Never argue with an idiot. They drag you down to their level, then beat
you with experience.
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
prev parent reply other threads:[~2002-12-15 21:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-15 17:02 [LARTC] Nearly complettly victory David Coello
2002-12-15 21:31 ` Martin Josefsson [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-103998798129184@msgid-missing \
--to=gandalf@wlug.westbo.se \
--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.