wu-ftpd-2.6.1 gives a "425 can't build data connection" on "ls" cmd in the client. Interestingly enough, most clients fail the 'ls' cmd (Win32 and Unix alike), with the exception of the ftp client installed on RH7 intel platform. I have a hunch that all non-passive clients fail, and that the absence of the August 29 wu-ftpd patch (ftp://ftp.wu-ftpd.org/pub/wu- ftpd/patches/apply_to_current/pasv-port-allow-correction.patch) for 2.6.1 is what causes the problems I'm experiencing with the new wu-ftpd. Another point of interest is that your wu-ftpd-2.6.0-14x works OK for all the clients I tried.
The clients are broken. See http://www.wu-ftpd.org/wu-ftpd-faq.html for more information on the problem.
If the clients are the faulty party, why can I do 'ls' on intel RH7, but not on alpha RH7 from same "broken" client?
I have verified this problem, also. I did an identical install of RH7.0 on an Alpha system and an Intel system. I am able to execute an "ls" under ftp without any problems on the Intel system. However, if I try the same thing from the same client connected to an Alpha system, I receive: ftp> ls 200 PORT command successful. 425 Can't build data connection: Connection refused. ftp>
This problem appears to be fixed in: wu-ftpd-2.6.1-8-alpha.html You can get a copy from http://rpmfind.net
The newer version of wu-ftp does fix the problem. However, the RH7 Alpha updates page should be updated to include this.
Fixed in the current version