Well, I see nothing that should be blocking passive ports. Do one more thing, just to be sure: add "pasv_enable=YES" to vsftpd.conf. That inexplicably fixed another fellow's problem last week.

By the way, if you ever get a /var/log/vsftpd.log file created (odd that it isn't already), the following command produces a nicely formatted list of vsftpd activity.

logwatch --service vsftpd --print --range Today

Change Today to Yesterday if you want yesterday's activity. Running the command with "--range Help" will show all available options for the range parameter.

If setting pasv_enable doesn't work, you're going to have to run a packet capture (using ethereal) to find out why your passive mode transfers aren't working.