On 2008-11-27, Dorian B|ttner <[EMAIL PROTECTED]> wrote:
> further investigation makes me assume that it would not be a real
> [EMAIL PROTECTED], though.
> Might also be a bad ftp-server on the other side? Error also occurs
> using command-line ftp:
works here if I retry a few times, and works every time if I disable
EPSV, they probably have half-broken firewall rules.
$ FETCH_CMD="/usr/bin/ftp -EVm" make fetch
> I can also ftp into the directory, but when issuing an ls, it garbles
> the screen with special chars.
Sounds like unicode :-D It will have the same problem with EPSV
not working correctly, but special chars sounds a bit odd (I don't
see it here, but maybe something was broken when you tried and
since fixed).
If it continues please try with and without the ethernet driver
diff (and then again with it to make sure it didn't just go away
anyway), but it's most unlikely to be caused by that.
> On the other side, I can use Windows/firefox to browse the ftp
> directory and get the file.
Firefox probably doesn't use EPSV/EPRT.
> Anyone an idea what's going on here? I have running a somewhate current
> with the ethernet driver cleanup patches recently posted on undeadly.
