Mailing List Archive: 49091 messages
  • Home
  • Script library
  • AltME Archive
  • Mailing list
  • Articles Index
  • Site search

[REBOL] Re: how to properly set-up proxy for ftp?

From: gjones05:mail:orion at: 20-Jun-2001 13:46

Hi, Petr, Again, I am probably amongst the least qualified to really answer these questions, but no one else has taken the bait, so I'll give it a try. From: "Petr Krenzelok"
> what is also strange, I can't "open" remote > ftp connection and do "insert"?
I don't know, but I do know that if you did, many of the returns come back on the sub-port specification, so it wouldn't get you very far.
> How do I manually command ftp port?
Very tough directly through REBOL, because, again, commands are sent over the port specifications, and most info returns on the sub-port. You can also experiment with telnet but you won't get much more than what trace/net is showing you. AR posted an interactive ftp scheme last week, but he said it does not support proxy servers.
> Net-log: { FTP server (Version wu-2.6.0(1) Fri Jun 23 > 09:17:44 EDT 2000) ready.} > Net-log: {230 User can logged in. Access restrictions apply.}
I could easily be wrong, but this line suggests to me that you are only now at the point of being ready to log on to the correct ftp server. The proxy port on dumped you into that account, but didn't pass on the user:pass stuff. Just a guess.
> Net-log: [ > "PASV" "227"] > Net-log: "227 Entering Passive Mode (194,196,81,131,6,255)"
This sequence shows that the the ftp server itself can accept passive mode. The 6 and 255 at the end of the 6 numeral tuple are the suggested sub-port (6 x 256 + 255). This number may change each time. When your network admin said that ftp also uses port 20, that is the port used by the active mode. In this mode the server attempts to hook up to the client; note that in this case the client *is* the server. This method is potentially not secure, so many configure firewalls/proxies to only accept passive mode, in which the server suggests another port, to which the client may connect as a client only.
> Uh, I need a break probably :-)
Yes, this is probably the case. It can be sooooo frustrating trying to get some thing to work. Here is what I think may be going on. I apologize in advance if I overlooked this information earlier in the thread. I think what you need to do is set up REBOL to work through a proxy (set-net stuff). This may be the same port used for http, but I do not know. Check the following to be sure that REBOL/Core is set-up correctly: You may need to specifically specify passive mode, as explained here: Then I believe you will be able to directly use the following: ftp://can:[pass-here--moon--rebol--cz]/ The proxy should then know to forward you to the correct ftp server, where your user:pass will log you in. I hope I am not misleading you. Good luck (timewise it looks like you'll have to wait until tomorrow;). --Scott Jones