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

    Ftp server problem

    Scheduled Pinned Locked Moved
    NAT
    7
    25
    18.5k
    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.
    • A
      althornin
      last edited by

      Sorry, but you are wrong.
      In passive mode, the data connection is client initiated.
      I have perfectly working passive FTP.
      NAT forward the passive ports to your ftp server.

      Also - your FTP server may be giving its NAT'd IP address to clients.
      post the logs.

      Passive connection works like so (basically):
      Client connects to server on port 21 (command).  Trys to download a file.
      Server responds with its IP address and passive port that it wants the client to use.
      client connects to that IP and port.

      Opening a range on the firewall does nothing without using nat forwarding.

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

        When I opened the range of port on the firewall I also natted them….

        I'll do some more tests and then I'll post logs.

        Thanks

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

          Well after mapping the range port I can connect from my LAN to my Ftp Server in passive mode using extrenal Ip address, here the log

          [14:12:44] REST 0
          [14:12:44] 350 Restarting at 0.
          [14:12:44] PWD
          [14:12:44] 257 "/" is current directory.
          [14:12:44] TYPE A
          [14:12:44] 200 Type set to A.
          [14:12:44] PASV
          [14:12:44] 227 Entering Passive Mode (192,168,10,2,23,117).
          [14:12:44] Opening data connection to xxx.xxx.xxx.149 Port: 6005
          [14:12:44] LIST -aL
          [14:12:44] 125 Data connection already open; Transfer starting.
          [14:12:44] 149 bytes transferred. (9,70 KB/s) (15 ms)
          [14:12:44] 226 Transfer complete.

          The problem is not solved from outside,

          [14:15:44] 257 "/" is current directory.
          [14:15:44] TYPE A
          [14:15:44] 200 Type set to A.
          [14:15:44] PASV
          [14:15:51] Connessione interrotta dal software del computer host.
          [14:15:51] Server closed connection

          I really can't understand what the problem is  >:(

          I'm starting to think that maybe something related with my ISP.

          Maybe the way they natted the subnet to my firewall is just wrong….although they say their setup is ok.

          Any hints?

          Thnaks Spack

          1 Reply Last reply Reply Quote 0
          • N
            nsumner
            last edited by

            What FTP client are you using. I have discovered some problems using the Filezilla client which is unfortunate because all in all it is a great client but doing some research I discovered a lot of people (my self included) had problems with it and NAT transveral (on my end not the server).

            1 Reply Last reply Reply Quote 0
            • A
              aldo
              last edited by

              i just dealt with this issue again over the weekend. I would be quiet confident it is not a pfsense issue.
              make sure that ftp proxy is off on the wan interface.

              like explained above the most likely problem is the server is sending the local ip to the client.

              four things things

              (1) set the wan ip in the ftp server passiveip
              (2) try to lock the passive port range on the server
              (3) check your wan firewall rules. (but i guess you used the auto nat feature.
              (4) ensure ftp-proxy is disabled on wan

              we now run most of our ftp servers on filtered bridges or non natted networks now to stop this issue

              good luck use the filter logs and the state table to help you with this one.

              1 Reply Last reply Reply Quote 0
              • A
                althornin
                last edited by

                @Speck:

                Well after mapping the range port I can connect from my LAN to my Ftp Server in passive mode using extrenal Ip address, here the log

                [14:12:44] REST 0
                [14:12:44] 350 Restarting at 0.
                [14:12:44] PWD
                [14:12:44] 257 "/" is current directory.
                [14:12:44] TYPE A
                [14:12:44] 200 Type set to A.
                [14:12:44] PASV
                [14:12:44] 227 Entering Passive Mode (192,168,10,2,23,117).
                [14:12:44] Opening data connection to xxx.xxx.xxx.149 Port: 6005
                [14:12:44] LIST -aL
                [14:12:44] 125 Data connection already open; Transfer starting.
                [14:12:44] 149 bytes transferred. (9,70 KB/s) (15 ms)
                [14:12:44] 226 Transfer complete.

                The problem is not solved from outside,

                [14:15:44] 257 "/" is current directory.
                [14:15:44] TYPE A
                [14:15:44] 200 Type set to A.
                [14:15:44] PASV
                [14:15:51] Connessione interrotta dal software del computer host.
                [14:15:51] Server closed connection

                I really can't understand what the problem is  >:(

                I'm starting to think that maybe something related with my ISP.

                Maybe the way they natted the subnet to my firewall is just wrong….although they say their setup is ok.

                Any hints?

                Thnaks Spack

                sorry to take forever to respond.
                Look at your log:
                Your FTP server is responding with its IP and ports for the client to use on this line:
                [14:12:44] 227 Entering Passive Mode (192,168,10,2,23,117).

                Now, look at that and tell me why it won't work from outside your network!
                Your ftp server is giving its IP as the nat'd private IP 192.168.10.2 - which cannot be accessed from outside your lan.  Remember, passive FTP works this way - the server tells the client which IP and port to connect to for data transfer…if your server is giving out its NAT'd address....it will never work outside your lan.
                What FTP server software are you using?  If i know, i can probably help you configure it properly, to give clients your external IP.

                It has nothing to do with the client.
                this is why i wanted you to post some logs.

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

                  I'm using Microsoft Ftp Sever (iis 6 Win2k3)

                  Anyway I think that it report internal address since i'm connecting using Nat Reflection and the server "see" the internal client IP.

                  I've tried to set external IP address but on Ms site is reported that the server will automatically use the right ip address (using nat service).

                  Today if I have time i'll try to setup BulletProof Ftp Server and see what happens….

                  Thanks for your reply,

                  Speck

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

                    Just tried Bulletproof ftp server and all works  :-\

                    So i guess the problem is with IIS 6 Ftp service….

                    anyone know how to set external IP address on this kind of server?

                    Thanks to all for your help  ;D

                    Speck

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

                      Hi all,

                      I'm having the exact same problem as OP, but what I don't understand is why IIS works fine behind other NAT firewalls(firebox,ipcop,linksys,netgear). What is pfSense doing different? I run a number of IIS ftp sites behind three different firewalls and ALL of them show the external NAT address (from the passive scenario above).

                      thanks for the help

                      edit.. using Beta3

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

                        try to turn on static nat, or enable the ftp proxy.

                        -lsf

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

                          I've tried both of these and the results are the same.

                          Question: Is pftpx (the FTP proxy) supposed to rewrite the address returned for PASV and also take care of the port mapping?

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

                            Yes it does, and the only known problem currently has to do with FTP brdiging.  So this should be working.

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

                              Ok. So should I see a pftpx process running associated with the WAN interface?

                              Regardless of FTP proxy settings for either the LAN or WAN interface, there is only one pftpx process ever running and it's always associated with the LAN interface. (and I do reboot after changing this setting)

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

                                Yes you should, make sure the helper is enabled on WAN interface.

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

                                  I've confirmed the FTP helper is enabled on the WAN and LAN interfaces and I've rebooted the machine. There is only one process listed:```
                                  /usr/local/sbin/pftpx -c 8021 -g 8021 10.10.101.2

                                  
If it failed on startup whould it be logged anywhere?
                                  1 Reply Last reply Reply Quote 0
                                  • S
                                    sullrich
                                    last edited by

                                    It will only fail on startup if you have a really old version.

                                    If this is a full install run cvs_sync.sh releng_1 from a shell.

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

                                      Just to be certain, I've done fresh install's of Beta 2, Beta 3 and Beta 3 + cvs update.. and on ALL of them, there is ALWAYS only one pftpx process (LAN interface) running when I enable the FTP helper on the WAN interface. For all of these tests, I configured the interfaces, enabled the WAN FTP helper and rebooted and made no other changes. From what I can tell, the WAN interface FTP helper never starts regardless of the setting in the webConfig.

                                      Edit: Have now found an error message:

                                      May 8 11:45:32 pftpx[8480]: listening on x.x.x.x port 21
                                      May 8 11:45:32 pftpx[8480]: event_dispatch error: Operation not supported by device
                                      May 8 11:45:32 pftpx[8480]: pftpx exiting on signal 0

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

                                        When the sysem boot i see only this in the system log:

                                        May 23 14:46:15 pftpx[816]: listening on 127.0.0.1 port 8021
                                        May 23 14:46:15 pftpx[816]: listening on 127.0.0.1 port 8021

                                        How can i check if pftpx process is running?

                                        when i try to connect with both wan and lan Ftp helper enabled i get this

                                        May 23 14:48:15 pftpx[816]: #1 server timeout
                                        May 23 14:48:15 pftpx[816]: #1 server timeout

                                        and i can't connect!

                                        tried now ps -aux the only line with pftpx is

                                        proxy  816  0.0  0.2  656  492  ??  Ss    2:46PM  0:00.02 /usr/local/sbin/pftpx -c 8021 -g 8021 192.168.10.11

                                        Thanks

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

                                          I can add some info for this problem.

                                          My WAN is configured this way:

                                          IP 192.168.x.x GW 192.168.x.x Mask 255.255.255.0

                                          All my external IP are configured as Virtual IP ProxyARP.

                                          Maybe this configuration (wan with private IP and all pARP public IP) can "confuse" Ftp helper? maybe I need some special settings?

                                          Thanks in advance!
                                          Speck

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

                                            Only if you are blocking private networks in Interfaces -> WAN.

                                            1 Reply Last reply Reply Quote 0
                                            • First post
                                              Last post