L7 doesn't care what ports are used. It just looks at the actual data
contained in the first few packets, and if any of the patterns in use
match, then that connection gets marked as such. I would say the FTP
pattern will match regular or passive connections just fine. This is
entirely seperate from the issue Matthew is trying to point out to
you, where you're trying to filter traffic from the box that L7-filter
is running on. Typically nobody will be using the box that L7-filter
is running on for anything. It'll be a router, most likely, and not a
user's machine. Classifying ftp traffic is easy. Classifying *any*
type of traffic from the L7 box is what he's trying to tell you about.
On 9/11/06, Lewis Shobbrook <mylists@...> wrote:
> The FAQ does not really help me. One of main objectives was to rein in FTP as
> you can't use the regular tc filters etc accurately on passive transfer. I
> was hoping to be able to use L7 to improve egress traffic handling as well.
> If I use the regular packet schedulers for the std tcp 21 & 20 ftp ports, will
> L7 handle the passive tranfers to & from the box at all?
> I know I can use the ftp config to limit rates for individual transfers, but
> it would seem to me to be inferior to the concept of using L7 htb u32 &
> sfq,which would be more dynamic making use of available throughput during
> periods of lower network load.
>get ye flask
You can't get ye flask.