Opened 22 years ago
Last modified 20 years ago
#330 closed Bug report
Server: Custom PASV Options ignored
Reported by: | anonymous | Owned by: | |
---|---|---|---|
Priority: | normal | Component: | Other |
Keywords: | Cc: | twelvebaud, Tim Kosse | |
Component version: | Operating system type: | ||
Operating system version: |
Description
I'm running FZ server (0.8.3) behind a router and cant
get it to give out correct ip:port for pasv, no matter
what I options I enter.
Dynip support would be nice too ;)
teilzeitprofi@…
Change History (3)
comment:1 by , 22 years ago
comment:2 by , 22 years ago
ahem... pardon me while I take my foot out of my mouth...
I read the docs again and apparantly I missed something.
Then I looked at your source code, then the docs once more,
and went "... Oh."
The implementation is in fact correct. Close this bug report...
comment:3 by , 20 years ago
This bug report has been closed due to inactivity and has possibly
already been solved.
You can reopen this report if the issue still exists in the
latest version of FileZilla (Server).
I have noticed this with every server out there.
RFC0959, aka STD0009, aka the Sacred FTP Text, states
that the passive command is
--> PASV
<-- 227 Entering Passive Mode (A1,A2,A3,A4,a1,a2)
where A1-A4 are the four IP address segments and a1 and a2
are the bounds of the port range.
I recently asked my friend to try to log in, using passive mode
to traverse our NATs, and the FileZilla log shows that it got
the A1, A2, A3, and A4 parts right but that the ports were 86-
156, despite my explicit setting of 40022-40025. Naturally the
transfer failed due to a timeout.
I'm using FileZilla Server version 0.8.3a on Windows NT 5.2
on a Dell Dimension 2100.
picaune[at]hotmail.com