From: Gustin Johnson <gustin@echostar.ca>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] traffic not getting into class
Date: Sun, 23 Dec 2007 22:51:48 +0000 [thread overview]
Message-ID: <476EE684.7020108@echostar.ca> (raw)
In-Reply-To: <20071217120952.1d06da9d.mailinglists@lucassen.org>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
<snip>
>
> ${TC} filter add dev ${DEV_IFB} parent 1:0 prio 4 protocol ip u32 \
> match ip protocol 0x6 0xff \ match ip dport 21 0xffff \ classid 1:14
> # ftp-server
>
> This works fine, but traffic for 1:14 (ftp) never gets into 1:14.
>
> Is there a certain rule order in which filters must be written? As
> far as I can see I haven't made any mistakes in these filters...
FTP is more complicated to filter than ssh. There is a control
connection and a data connection.
> Anyone a hint?
The following sites give some info on the ftp protocal, though there is
a ton of more info if you use google.
http://www.slacksite.com/other/ftp.html
http://www.troubleshootingnetworks.com/ftpinfo.html
As an aside, ftp services really should be replaced with one of the
better alternatives.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFHbuaEwRXgH3rKGfMRAq2dAJ9fYPz6yvBQPuima3sUNCt0OQpHWQCfcxHw
nUC+eYmSP+0MNj+DEkyUQDkkBW
-----END PGP SIGNATURE-----
_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
prev parent reply other threads:[~2007-12-23 22:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-17 11:09 [LARTC] traffic not getting into class richard lucassen
2007-12-18 14:38 ` Shane McKinley
2007-12-20 13:00 ` Andrei Kovacs
2007-12-23 22:51 ` Gustin Johnson [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=476EE684.7020108@echostar.ca \
--to=gustin@echostar.ca \
--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