SSL WAN IP Feature Request
SSL WAN IP Feature Request
Two NAT routers. Would it be possible to include an option whereby a router's WAN address could be stored as a setting so it could be encrypted and sent to the FTP/SSL server instead of the machine's LAN address? I have been able to connect to the server with all the clients I've tried that support SSL including this one, but the server tries to connect a data channel to a port at the 192.168.1.* address that was given while encrypted so the server's router couldn't translate which of course never gets a response.
-
- Site Admin
- Posts: 1004
- Joined: Mon Mar 24, 2003 4:37 am
Yes it works but you have to enter the public internet IP address in plain (ie 213.223.215.101).
For dynamic public IP address you have to find out the current public IP address of the remote site (e.g by means of a ping towards your dyndns.org address).
Then you have to manually configure coreFTP :
advanced -> connections -> use IP/Nat address
with your current IP address (it can change every day)
=> this is not convenient.
why not allow configuration of the external IP address by means of the dyndns.org url (or any url) in the field :
advanced -> connections -> use IP/Nat address
=> no manual configuration would be needed anymore it would be convenient.
N.B this results in having to ask for a DNS resolution a second time, but that's no big deal (Filezilla is able to do that though in the end FTP/SSL doesn't work with filezilla for me)
For dynamic public IP address you have to find out the current public IP address of the remote site (e.g by means of a ping towards your dyndns.org address).
Then you have to manually configure coreFTP :
advanced -> connections -> use IP/Nat address
with your current IP address (it can change every day)
=> this is not convenient.

advanced -> connections -> use IP/Nat address
=> no manual configuration would be needed anymore it would be convenient.
N.B this results in having to ask for a DNS resolution a second time, but that's no big deal (Filezilla is able to do that though in the end FTP/SSL doesn't work with filezilla for me)

The need to enter manually the public internet IP address in plain (ie 213.223.215.101) that may change every day (depending on ISP) implies that there is no point to upgrade to coreFTP PRO to benefit from scheduled FTP sessions.
For what is the point of have scheduled FTP session (intended at being not attended) if you have to manually figure out the current public IP address and manually configure it into coreFTP !

You were not clear in your description of the problem. Someone has mentioned this in another forum (perhaps that was you, if it was you were much more clear there) and this will, hopefully, be added later on.
There is no need to get upset here, when you didn't clearly define the problem originally.
P.S. - I do not work for CoreFTP, so you're more than welcome to get mad with me all you want but it was rediculous of you to go crazy with the bold text and emoticons as you did here.
There is no need to get upset here, when you didn't clearly define the problem originally.
P.S. - I do not work for CoreFTP, so you're more than welcome to get mad with me all you want but it was rediculous of you to go crazy with the bold text and emoticons as you did here.
Brendon, there is no need to be defensive.
I hold nothing against anybody.
I realised that no answer was brought to my post because people thought it was too long (due to my desire to be precise enough).
As a result I put in bold items for people interested only in a synthesis, and left in no bold the details for others.
It is not getting mad about anybody, it is only in an attempt to put in a single post the details for those who want to dig the issue and in bold the synthesis words for a faster reading.
I'll sorry if you felt at all agressed that was absolutely not my purpose.
I hope I'm understood now
I hold nothing against anybody.
I realised that no answer was brought to my post because people thought it was too long (due to my desire to be precise enough).
As a result I put in bold items for people interested only in a synthesis, and left in no bold the details for others.
It is not getting mad about anybody, it is only in an attempt to put in a single post the details for those who want to dig the issue and in bold the synthesis words for a faster reading.
I'll sorry if you felt at all agressed that was absolutely not my purpose.
I hope I'm understood now

I'm afraid not :
Error loading directory...
the private IP address behind the remote router is used instead.
It acts as if I did not use the fiel "use NAT/IP/address"
- though I used it and used the same url as in the connection
Last edited by thibault on Wed Nov 01, 2006 10:31 am, edited 1 time in total.
for debugging purpose, I made the same test but filling the plain IP address in the field "use NAT IP/address"
it works
=> what was working still works, using url in use NAT/IP address" does not work yet
it works
=> what was working still works, using url in use NAT/IP address" does not work yet
Last edited by thibault on Wed Nov 01, 2006 10:30 am, edited 1 time in total.
I've just tried 1474 build from 25th october.CP wrote:it wasn't added for passive (PASV) connections. A fix will be in the next build (1472 and greater)...
we are moving forward.
Now connection is ok, the change of directory and directory listing is ok.
but transfer in binary does not work (i tried with default to binary : does not work either).
Last edited by thibault on Wed Nov 01, 2006 10:29 am, edited 2 times in total.
I made then the same test but putting the IP address in plain in "advanced" , "use NAT IP/address" instead of url.
the connection is ok and the transfer in binary is ok
the connection is ok and the transfer in binary is ok
Last edited by thibault on Wed Nov 01, 2006 10:28 am, edited 1 time in total.