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

    FTP support

    Scheduled Pinned Locked Moved 2.0-RC Snapshot Feedback and Problems - RETIRED
    6 Posts 3 Posters 2.5k 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.
    • N
      nmarques
      last edited by

      I'm trying to use FTP with pfsense 2.0 and I'm starting to feel my brain melting.

      I've read that pfsense 2.0 use libalias, in a normal freebsd instalation we have an alias_ftp.ko module, pfsense doesn't have any, is this normal?

      I just want NAT for outgoing ftp connections and automagicaly add fw rules for them. Did anyone got this working with 2.0?

      Thanks

      1 Reply Last reply Reply Quote 0
      • B
        bEsTiAn
        last edited by

        Hello

        Same question here. is this already supposed to be working ?
        I clearly see my FTP data traffic requests being blocked by the default deny rule at the moment

        thx

        Guillaume

        1 Reply Last reply Reply Quote 0
        • E
          eri--
          last edited by

          It will work only for the inerface where nat happens on the other interfaces you need to allow it.

          If this is needed for the non nat interfaces please convince me to implement it.

          1 Reply Last reply Reply Quote 0
          • B
            bEsTiAn
            last edited by

            my client hits the firewall on the internal interface
            I have set up the NAT rule on the external interface of my firewall
            so outgoing traffic gets the NAT IP of the firewall's public interface
            but ftp client's data traffic is blocked at the firewall's internal interface

            Is it wrong ?

            1 Reply Last reply Reply Quote 0
            • E
              eri--
              last edited by

              That is wright.
              You have to allow your client at the internal interface as it is now.

              1 Reply Last reply Reply Quote 0
              • B
                bEsTiAn
                last edited by

                OK that is how I have set it up, allowing TCP traffic for ports such as 20000->65535 for my clients. Not very safe for a firewall :(
                So that should give you enough conviction that FTP over NAT support would be good to happen as well non non-NAT interfaces ;)

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