Netgate Discussion Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Search
    • Register
    • Login

    Shaping FTP

    Scheduled Pinned Locked Moved Traffic Shaping
    6 Posts 3 Posters 2.6k Views
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • Y
      yaw
      last edited by

      All,

      I'm using 2.0 stable, and cannot get shaping for FTP to work. No matter what I try, all FTP downloads (to client on LAN) ends up in the default queue. Shouldn't it be as simple as adding a floating rule for port 21?

      match  on {  vr1  }  proto tcp  from any to any port 21  queue (qOthersLow,qACK)  label "USER_RULE: m_Other FTP"

      What am I missing?

      Thanks.

      1 Reply Last reply Reply Quote 0
      • P
        podilarius
        last edited by

        port 21 is the control port.
        port 20 is the port for active mode data transfer.
        and passive is anything over port 1024.
        If you are only shaping the control port, then you are not going to shape the data ports.

        1 Reply Last reply Reply Quote 0
        • Y
          yaw
          last edited by

          Okay… Port 20 is easy enough to add. Passive mode will be more difficult. Can I use layer 7 to put passive FTP traffic into queues? I tried that a bit yesterday, but wound up killing all traffic to the interface.

          What I did is create a new group with a FTP layer 7 queue. I then applied that to default rule that allows all traffic on that interface. For some reason, this killed all traffic to that interface.

          Thanks again.

          1 Reply Last reply Reply Quote 0
          • P
            podilarius
            last edited by

            I have not used layer 7 shaping yet … what I did was use the P2P catch all and assigned it the lowest possible priority. This way any other traffic won't have a problem and FTP/torrents can have what is left.

            1 Reply Last reply Reply Quote 0
            • marcellocM
              marcelloc
              last edited by

              keep in mind that active ftp transfers are done with client source port 20 instead of server destination port

              client:20 -> server:any

              Treinamentos de Elite: http://sys-squad.com

              Help a community developer! ;D

              1 Reply Last reply Reply Quote 0
              • Y
                yaw
                last edited by

                Good point. Thanks.

                1 Reply Last reply Reply Quote 0
                • First post
                  Last post
                Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.