ftp client passive mode

sasa1

Hi,
on my pfsense I disabled the "ftp client proxy" and tried the connection to the remote server in ftp but I have this result:
230 Login successful.
ftp> ls
500 Illegal PORT command.
425 Use PORT or PASV first.
ftp>

Thanks.

johnpoz

Your still doing the port command - says so right there!! in what you posted.

And that it says its illegal is telling you most likely that you sent your rfc1918 address. Or you didn't at the wrong time..

Also if your trying to use the cmd line ftp client in windows - it doesn't support passive.. you can do the command all day.. It doesn't support it.. never has..

Here this is with using the ftp proxy - works just fine with windows client

ftp> user anonymous
331 Please specify the password.
Password:
230 Login successful.
ftp> ls
200 PORT command successful. Consider using PASV.
150 Here comes the directory listing.
1000GB.zip
100GB.zip
100KB.zip
100MB.zip
10GB.zip
10MB.zip
1GB.zip
1KB.zip
1MB.zip
200MB.zip
20MB.zip
2MB.zip
3MB.zip
500MB.zip
50MB.zip
512KB.zip
5MB.zip
upload
226 Directory send OK.
ftp: 183 bytes received in 0.02Seconds 9.63Kbytes/sec.
ftp>

sasa1

on another PC that is in another network but with the same configuration (therefore always using the ftp Windows client and always behind pfsense) I can access the ftp server:

C:\Users\Administrator>ftp speedtest.tele2.net
Connesso a speedtest.tele2.net.
220 (vsFTPd 3.0.3)
200 Always in UTF8 mode.
Utente (speedtest.tele2.net:(none)): anonymous
331 Please specify the password.
Password:
230 Login successful.
ftp> ls
200 PORT command successful. Consider using PASV.
150 Here comes the directory listing.
1000GB.zip
100GB.zip
100KB.zip
100MB.zip
10GB.zip

I would like to have the same possibility also on this PC where it doesn't work.
Thanks.

johnpoz

And for active to work, you would have to use the ftp client, and you would have to set it up... And the port your client says to use to talk to it would have to be open..

I just showed you ftp client works just fine.. I gave you the info on how ftp actual works..

If something is not working, I suggest you sniff on pfsense for this ftp traffic and take a look to what could be going wrong..

If this client is on a different network, say your DMZ you listed - the ftp active proxy would have to be listening on that interface as well, you only have it listening on your LAN.

You can have it listen on multiple interfaces

sasa1

so "Enable the FTP Proxy" (about FTP Client Proxy) must be enabled?
I have enabled the component again and I have selected all the networks but the error message remains the same.
what can I check in pfsense to find the problem?
thanks.

johnpoz

@sasa1 said in ftp client passive mode:

so "Enable the FTP Proxy" (about FTP Client Proxy) must be enabled?

YES if your going to do ACTIVE mode! Already went over this... windows ftp client can not do passive, so if you want to use that then yes your going to have to use the ftp proxy package..

sasa1

I have enabled "ftp client proxy" and I have selected all the networks but the error message is this:
ftp> ls
200 PORT command successful. Consider using PASV.
425 Failed to establish connection.

johnpoz

@sasa1 said in ftp client passive mode:

200 PORT command successful. Consider using PASV.
425 Failed to establish connection.

And what port was trying to be used... Sniff on pfsense and look and see!

Try a different client that gives you better logging, like filezilla which will show you the port command sent. So you can see what IP and port... Then sniff on pfsense - is the proxy changing it on your wan.. Is the port your telling to connect to already in use? etc..

Your not policy routing out some vpn are you, etc. What is the make up of your setup... If it working on 1 network.. clearly it works, etc.. so you have to figure out what other issue is there..

sasa1

I tried with filezilla and a strange thing happens, if I use the domain name it gives me an error if instead I use the IP address it works:

Stato: Risoluzione dell'indirizzo IP speedtest.tele2.net in corso
Stato: Tentativo di connessione non riuscito con "EAI_NONAME - Nome nodo e nome server non forniti, o sconosiuti".
Errore: Impossibile collegarsi al server
Stato: In attesa di un nuovo tentativo...
Stato: Connessione a 90.130.70.73:21...
Stato: Connessione stabilita, in attesa del messaggio di benvenuto...
Stato: Server non sicuro, non supporta FTP su TLS.
Stato: Il server non supporta caratteri non ASCII.
Stato: Accesso effettuato
Stato: Lettura elenco cartelle...
Stato: Elenco cartella di "/" completato

is very strange !

johnpoz

My guess is you typo'd the name... simple to test if resolves or not.. do a dig or or nslookup, or whatever your fav dns tool is..

$ dig speedtest.tele2.net

; <<>> DiG 9.16.0 <<>> speedtest.tele2.net
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 8563
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;speedtest.tele2.net.           IN      A

;; ANSWER SECTION:
speedtest.tele2.net.    0       IN      A       90.130.70.73

;; Query time: 8 msec
;; SERVER: 192.168.3.10#53(192.168.3.10)
;; WHEN: Sun Mar 29 10:31:06 Central Daylight Time 2020
;; MSG SIZE  rcvd: 64

Or maybe you put in url like http:// not sure.. what your doing wrong.

Can not tell from what you posted if your using active or passive. Pretty sure filezilla defaults to passive.. Which we have been over already multiple times!!

sasa1

the strange thing is this..that the name is correctly resolved !!

nslookup speedtest.tele2.net
Server: one.one.one.one
Address: 1.1.1.1

Risposta da un server non autorevole:
Nome: speedtest.tele2.net
Addresses: 2a00:800:1010::1
90.130.70.73

with filezilla, using the IP address, it works both in active and in passive mode.

johnpoz

Yeah that doesn't make any sense at all... Local issue is you typo'd the name when you put it in to filezilla or had a space or something wrong... Works fine here with name.. filezilla would use the same dns as your OS... Unless its switched to trying to do doh or something?

So so these machines not even using pfsense for dns..

sasa1

I have typed the name several times and it is the same that I use when I try the connection from the DOS client, I really can't understand!
however with Filezilla using the IP address I can make the ftp connection.

what can I check to understand where the problem is in the ftp connection using the DOS client?
Thanks.

johnpoz

Dude we already went over this - what are you NOT understanding about active vs passive??

the built in windows ftp client will NOT do passive - period! So your ftp proxy package would have to be setup.. Which multiple people have shown you works just fine..

sasa1

I already installed the "ftp proxy client" package but it still doesn't work.

I should add that on other servers (which are in other datacenters) where I have configured pfsense in the same way, ftp access works fine.
I don't understand why only in this circumstance the access in ftp access doesn't work.
Thanks.

johnpoz

Your in a DC.. You understand active only works when traffic can get back to you on the random high port that can be used.. Its quite possible that is not allowed upstream of pfsense.

all of which could be figured out in 30 seconds of sniffing that I suggested multiple posts back, but you seem unwilling to do the 30 second test, but just keep asking why it won't work without providing any actual info... Ie your sniff..

First step in troubleshooting is understanding how the protocol works active vs passive - again! Read the link I provided, then knowing how that works and the environment your in.. Which could cause that to break down... Sniff on pfsense to validate traffic is doing what its suppose to be doing..

sasa1

in Windows, on the local firewall, I have enabled incoming traffic from ports 1024-65535.

I want to analyze the traffic to understand where the problem is, I only asked for help on how to get this information through sniffing.
Thanks.

johnpoz

Well sniff it on pfsense, diagnostic packet capture..

On the lan side sniff for the dest IP so you can see all traffic going there, then on the wan side of pfsense sniff on the dest IP..

Sniff on the client other than for trying to figure out why its not resolving is going to be pretty useless, unless its local firewall blocking the return traffic on active.. Which sure it could be..

But your going to want to sniff both lan and wan side on pfsense to validate the ftp package is changing the IP of the client for the active to work.

Rico

Why would you use the Windows FTP Client anyway? Because of scripting? Then check out WinSCP...

-Rico

sasa1

@johnpoz said in ftp client passive mode:

Well sniff it on pfsense, diagnostic packet capture..
On the lan side sniff for the dest IP so you can see all traffic going there, then on the wan side of pfsense sniff on the dest IP..
Sniff on the client other than for trying to figure out why its not resolving is going to be pretty useless, unless its local firewall blocking the return traffic on active.. Which sure it could be..
But your going to want to sniff both lan and wan side on pfsense to validate the ftp package is changing the IP of the client for the active to work.

I captured the packages and this is the result:

13:05:05.516740 IP 93.57.xxx.xxx.24479 > 90.130.70.73.21: tcp 0
13:05:05.561254 IP 90.130.70.73.21 > 93.57.xxx.xxx.24479: tcp 0
13:05:05.561304 IP 93.57.xxx.xxx.24479 > 90.130.70.73.21: tcp 0
13:05:06.766410 IP 90.130.70.73.21 > 93.57.xxx.xxx.24479: tcp 20
13:05:06.766447 IP 93.57.xxx.xxx.24479 > 90.130.70.73.21: tcp 0
13:05:06.772561 IP 93.57.xxx.xxx.24479 > 90.130.70.73.21: tcp 14
13:05:06.817096 IP 90.130.70.73.21 > 93.57.xxx.xxx.24479: tcp 0
13:05:06.817115 IP 90.130.70.73.21 > 93.57.xxx.xxx.24479: tcp 26
13:05:06.817145 IP 93.57.xxx.xxx.24479 > 90.130.70.73.21: tcp 0
13:05:10.066607 IP 93.57.xxx.xxx.24479 > 90.130.70.73.21: tcp 16
13:05:10.111300 IP 90.130.70.73.21 > 93.57.xxx.xxx.24479: tcp 34
13:05:10.111368 IP 93.57.xxx.xxx.24479 > 90.130.70.73.21: tcp 0
13:05:11.043716 IP 93.57.xxx.xxx.24479 > 90.130.70.73.21: tcp 7
13:05:11.128910 IP 90.130.70.73.21 > 93.57.xxx.xxx.24479: tcp 0
13:05:12.783654 IP 90.130.70.73.21 > 93.57.xxx.xxx.24479: tcp 23
13:05:12.783690 IP 93.57.xxx.xxx.24479 > 90.130.70.73.21: tcp 0
13:05:14.296534 IP 93.57.xxx.xxx.24479 > 90.130.70.73.21: tcp 26
13:05:14.341011 IP 90.130.70.73.21 > 93.57.xxx.xxx.24479: tcp 0
13:05:14.341168 IP 90.130.70.73.21 > 93.57.xxx.xxx.24479: tcp 51
13:05:14.341196 IP 93.57.xxx.xxx.24479 > 90.130.70.73.21: tcp 0
13:05:14.350410 IP 93.57.xxx.xxx.24479 > 90.130.70.73.21: tcp 6
13:05:14.395146 IP 90.130.70.73.20 > 93.57.xxx.xxx.54046: tcp 0
13:05:14.395513 IP 93.57.xxx.xxx.54046 > 90.130.70.73.20: tcp 0
13:05:14.436943 IP 90.130.70.73.21 > 93.57.xxx.xxx.24479: tcp 0
13:05:14.440036 IP 90.130.70.73.21 > 93.57.xxx.xxx.24479: tcp 37
13:05:14.440067 IP 93.57.xxx.xxx.24479 > 90.130.70.73.21: tcp 0

Thanks.