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

    FTP not working with Load Balancer ?

    Routing and Multi WAN
    5
    14
    5.9k
    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.
    • H
      hessie
      last edited by

      Hi !

      FTP connections timeout, though my balancing setup works fine.

      Anyone got an idea ? I followed the tip in the Load-Balancing-How-To to set up a "workaround" rule with 127.0.0.1 1-65535 through my default gateway but nothing changed.

      1 Reply Last reply Reply Quote 0
      • S
        sullrich
        last edited by

        @hessie:

        Hi !

        FTP connections timeout, though my balancing setup works fine.

        Anyone got an idea ? I followed the tip in the Load-Balancing-How-To to set up a "workaround" rule with 127.0.0.1 1-65535 through my default gateway but nothing changed.

        Known issue.  FTP is not compatible with dual wan or load balancing atm.

        1 Reply Last reply Reply Quote 0
        • H
          hessie
          last edited by

          Whoops, bad thing … :-( I did not knew that before..

          Is it at least possible to use policy based routing here and push all ftp traffic through one interface or will it also not work ?

          Do you know why its not working and are you working on a fix which should come "soon" or could that take longer ?

          Thanks

          1 Reply Last reply Reply Quote 0
          • H
            hoba
            last edited by

            @hessie:

            followed the tip in the Load-Balancing-How-To to set up a "workaround" rule with 127.0.0.1 1-65535 through my default gateway but nothing changed.

            This workaround works fine sending all ftp-traffic to the main WAN. Make sure your rule is on top of all other rules and you use "default" and not WAN as gateway.

            1 Reply Last reply Reply Quote 0
            • S
              sullrich
              last edited by

              You can disable the ftp helper and port forward 21 + the data range and it should work fine.  If you have a ftp server that allows the controlling of the data port range, only allow 1000 ports or so to keep the port range small.

              1 Reply Last reply Reply Quote 0
              • H
                hessie
                last edited by

                Thanks the workaround works now, I had it at the last position at the firewall rules which was wrong. I moved it to the top and now everything works as expected.

                Thanks !

                1 Reply Last reply Reply Quote 0
                • S
                  sullrich
                  last edited by

                  No problem.  Glad you got it working.

                  1 Reply Last reply Reply Quote 0
                  • T
                    tunge2
                    last edited by

                    Where do i add the ftp rule? I added the rule below, but that rule doesn't work?

                    Proto Source Port Destination Port Gateway Description

                    TCP/UDP  LAN net  20 - 21  *  20 - 21  *  FTP

                    1 Reply Last reply Reply Quote 0
                    • H
                      hoba
                      last edited by

                      If you search you'll find the workaround mentioned endless times here at the forum. However, the rule should look like:
                      Firewall>rules, Lantab, very top:
                      pass, protocol any, source any, destination 127.0.0.1, gateway default

                      This is the most easy rule to fix anything that runs on the pfSense itself with loadbalancing/multiwan, not only ftp but natreflection, packages, …

                      1 Reply Last reply Reply Quote 0
                      • T
                        tunge2
                        last edited by

                        Thanks, now it works!!  Is it possible to add this information to the load balancing document? I did not understand the original line in the most recent version of the load balancing document….

                        1 Reply Last reply Reply Quote 0
                        • H
                          hoba
                          last edited by

                          I edited the section: http://doc.pfsense.org/index.php/Multi-Wan/Load-Balancing#FTP.2FNAT-Reflection_Workaround

                          Hope this will prevent further confusion.

                          1 Reply Last reply Reply Quote 0
                          • T
                            tunge2
                            last edited by

                            thnx :) i hope that question never comes back again…...

                            1 Reply Last reply Reply Quote 0
                            • L
                              leimrod
                              last edited by

                              It might also be worth noting that pfSense needs to be restarted after implementing this rule for it to fully take affect. At least this was the case with my experience of trying to get FTP working

                              1 Reply Last reply Reply Quote 0
                              • H
                                hoba
                                last edited by

                                @leimrod:

                                It might also be worth noting that pfSense needs to be restarted after implementing this rule for it to fully take affect. At least this was the case with my experience of trying to get FTP working

                                Should usually not be needed. I guess it's a state problem if you tried it just before setting up the rule. In that case a diagnostics>states,reset states should fix it.

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