Ftp server to server transport

[marioth1]

Hi again,

I'm missing some functionality I know for example
from Filezilla Server where I can allow server to server
transport.
I just changed the target of my portforwardings (21 and the passive
range 5000-5100) from my pc to my SPD8020 (and configured the passive
ports there) but transfer doesn't start.
Can I somehow use the 'Additional settings file' option
to enable that?

best regards
Mario

[fvdw]

what do you exactly mean with "server to server " transport
Normally you connect with a client to the ftp server...

[marioth1]

thx for fast response

http://www.proftpd.org/docs/howto/FXP.html

A client connects to two servers and forces them to talk with each other to avoid using your own bandwidth.

So one of the servers needs to be in active mode, the other one in passive mode.
I can only set my SPD8020 to use passive mode.
So the client sends a PASV command to my SPD8020 which should then return a PORT answer including
IP-Adress and Portnumber.
And here is the problem, the SPD8020 answers with the IP-address from inside my LAN (10.0.0.5) which the
other server can't connect to (because it is somewhere on the internet).
When doing such a FXP transfer from an outside FTP-Server to my Computer in my LAN running Filezilla Server, Filezilla Server answers with the external IP-Adress of my router.
Since I have your great new firmware for my SPD8020 I want to do a FXP transfer from an outside FTP-Server to my NAS without having my computer running.

I have added to screenshots:
The first one shows the NONWORKING transfer from outside FTP-Server to SPD8020 running fvdw. (PASV => 10.0.0.5,19,209) where the first 4 numbers are the internal ip ([L] answer from SPD8020).

The second one shows a WORKING transfer from outside FTP-Server to my Computer (PASV => 91.115.122.3,19,139) where the first 4 numbers are my external ip ([L] answer from Filezilla Server on my PC)


So the problem is, that the SPD8020 answers with its internal IP to the PASV command instead of the external IP-Adress.

best regards

[fvdw]

ok I understand

not so easy to solve as the ftp server runiing on the spd8020 doesn't know the WAN ip address of your router.
We use proftpd
I never tried it but the -S option seems to be a possibility to specify a server address
After configuring your ftp server and stating it once and stop it. This should write the ftp configuration file to disk
Now start it from the linux command line (using ssh access)

Code: Select all

proftpd -S ip-wan

Of course replace ip-wan by actual wan ip address of your router
If that solves your problem you can use that as a temporary work around. To add the -S option in starting the server via webinterface will require adaptation of the firmware scripts.

[Jocko]

Hi marioth

I am still not at home for several days and I can't do some tests
If I remenber well this feature is not fully implemented.
So maybe some additional directives should be added and in this case you can use theadditional conf file to do it.
But at least the Ip address is marqueraded (so the server know your WAN IP).
You must also allow the IP address of the 2d FTP server

[marioth1]

Hi,

I've already got it working by shooting in a config-file that contains the following two lines

MasqueradeAddress MyWANDNSEntry
AllowForeignAddress on

Black/White List Auth was already deactivated.

But now the problem is, that proftpd ALWAYS responses with the external IP so I can't connect
to the ftp-server from a device from within my LAN. It seems that Filezilla Server for example
detects automatically which is the right address to response with.
However, I can live with the way it works now :-)

Maybe you can tweak around this problem in one of the next releases.

best regards

[Jocko]

Two notes:

- if you use active mode from your lan you should be able to connect again.
- your masquerade directive is useless if you use as server name your wanDNS. The server updates the related Wan IP every 2 hours.

[marioth1]

1) Yes thats true, but as far as I know at least one of the two servers must be in passive mode. That means I must
force the other server to passive mode, which is in my cases not always possible -> PASV denied.

2) Do the 2 hours regard to fvdws DDNS client? I use the DDNS from my router/modem. The DNS-entry
is updated "immediately" every time the IP-address changes.

[Jocko]

About masquerade address updating it is just the FTP server checks every two hours if the WAN IP that it uses must be updated. So it is not the DDNS feature

[marioth1]

Ah ok, thanks for that info.
Is the same intervall relevant for the -s option fvdw mentioned?

My router is online 24/7 so I believe that although I have dynamic IP I receive the same IP
everytime my router reconnects after the provider-forced 8 hour disconnect.