Hi,
I found a corner case, where it might not work even if you set them:
pasv_min_port=1
pasv_max_port=9000
(Notice that min an max was mixed up)
In this case the server does start (not yielding a config error) but the
configuration is ignored. This is clearly a bug. I could accept both
** Changed in: vsftpd (Ubuntu)
Status: Invalid = New
--
pasv_min_port,pasv_max_port does not work if client uses PASV
https://bugs.launchpad.net/bugs/130682
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to vsftpd in ubuntu.
--
Same problem on Ubuntu 10.04 server with vsftpd. I'm using a Cisco 1811
router with ports 20 and 21 statically NATed and a NAT pool for the PASV
ports. This works fine in standard FTP mode, but when I switch to PASV
mode in FTPES, it uses a port outside the range specified by the min/max
port
Whoops. Found a flaw in my .conf file. I had copied the pasv_min_port
to a different spot while troubleshooting another issue, and had two
values for min, with no value for max. Works fine now in both modes.
Setting status back the way I found it.
** Changed in: vsftpd (Ubuntu)
Status:
Same issue here with a TP-Link WR340GD router.
It too requires only setting up the 21 port forward, but beware, do not
alter the pasv_address ! it has to come from the local ip address,
otherwise the router magic gets confused and it doesn't work.
Cheers.
--
pasv_min_port,pasv_max_port does
I'm using Ubuntu 9.10 with vsftpd 2.2.0-1ubuntu1
The explanation Carsten Menke does not apply to my situation.
With:
pasv_min_port=65000
pasv_max_port=65535
I connected with lftp (version 3.6.1-1). Looking in vsftpd.log (I put
x where IP numbers go) I see:
Wed Jan 13 16:48:38 2010 [pid
