Proxmox 7 > 8 / ftp passive mode not working

michaelj

Renowned Member
Jun 30, 2016
57
0
71
38
Hi,

I have just upgraded my proxmox 7 to 8 latest server, I notice that the passive FTP mode from a container no longer seems to work without forcing it once the connection is established compared to version 7 which worked with the same configuration.
on proxmox 7 :

Code:
ftp ftp.xxx.com
Connected to ftp.xxx.com.
220 Microsoft FTP Service
Name (ftp.xxx.com:xxxx): ******
331 Password required
Password:
230 User logged in.
Remote system type is Windows_NT.
ftp> ls
200 PORT command successful.
125 Data connection already open; Transfer starting.
07-19-24  01:15PM       <DIR>          *****
07-19-24  01:15PM       <DIR>          ******
07-19-24  01:15PM       <DIR>          ******
226 Transfer complete.

on proxmox 8 :
Code:
ftp ftp.xxx.com
Connected to ftp.xxx.com.
220 Microsoft FTP Service
Name (ftp.xxx.com:xxx): ****
331 Password required
Password:
230 User logged in.
Remote system type is Windows_NT.
ftp> ls
501 Server cannot accept argument.
ftp: bind: Address already in use


but if i set to passive mode, it works

ftp> passive
Passive mode on.
ftp> ls
227 Entering Passive Mode (2,32,162,135,242,133).
150 Opening ASCII mode data connection.
07-19-24  01:15PM       <DIR>          ****

I have this activated on both versions 7 and 8, but only works in v7 :
cat /etc/modules
Code:
# /etc/modules: kernel modules to load at boot time.
#
# This file contains the names of kernel modules that should be loaded
# at boot time, one per line. Lines beginning with "#" are ignored.
# Parameters can be specified after the module name.

xt_state
ip_conntrack
nf_conntrack_ftp
nf_nat_ftp
ip_conntrack_ftp

#IPVS modules
ip_vs
ip_vs_dh
ip_vs_ftp
ip_vs_lblc
ip_vs_lblcr
ip_vs_lc
ip_vs_nq
ip_vs_rr
ip_vs_sed
ip_vs_sh
ip_vs_wlc
ip_vs_wrr

on v8 :
Code:
lsmod |grep nf_conntrack_ftp
nf_conntrack_ftp       24576  1 nf_nat_ftp
nf_conntrack          196608  7 xt_conntrack,nf_nat,nf_nat_ftp,xt_state,xt_nat,nf_conntrack_ftp,ip_vs

I would like to point out that the containers do not have a public IP and go out to the internet using the host's IP.

Do you have an idea ?

Regards.
 
Last edited: