FTP Synchronization / Multiple IP Addresses For ftp.box.com
We are attempting to use Box.com as an intermediary between public and private servers. In this use case we are uploading files from one host and promptly downloading them from another using ftps. While performing this action we have observed odd behavior. Is there a flaw in our usage? Is there an issue or delay synchronizing between Box.com servers?
In particular it appears that ftp.box.com resolves to two IP address, 107.152.26.220 and 107.152.27.220, which are not synchronized in a timely manner. When scanning for files to download on one IP address, files uploaded to the other IP address my be missed.
Here is a specific example. Note how depending on which server we connect to there is either 2 (. and ..) or 290 results.
| lftp -d
lftp :~> open -p 990 ftps://user:password @ ftp.box.com
---- Resolving host address...
---- 2 addresses found: 107.152.26.220, 107.152.27.220
lftp -d
lftp :~> set ssl:verify-certificate no
lftp :~> open -p 990 ftps://user:password @ ftp.box.com
---- Resolving host address...
---- 1 address found: 107.152.26.220
lftp ftps://user:password @ ftp.box.com:~> cd ExternalUpload/camo_cho/data/ && ls | wc -l
2
# lftp -d
lftp :~> set ssl:verify-certificate no
lftp :~> open -p 990 ftps://user:password @ ftp.box.com
---- Resolving host address...
---- 1 address found: 107.152.27.220
lftp ftps://user:password @ ftp.box.com:~> cd ExternalUpload/camo_cho/data/ && ls | wc -l
290
A workaround appears to be hardcoding the IP address to ensure that uploads and downloads occur on the same server. Is this a reasonable approach? Can I assume that the IP addresses are fixed?
Please sign in to leave a comment.
Comments
0 comments