greg@dekalb.UUCP (Greg Philmon) (04/12/89)
Since we don't have FTP access, I am looking for a program that allows FTP
from a PC. Does such a thing exist? I already have UUPC, but that is not
what is needed.
Greg Philmon
...gatech!dekalb!greghpchang@tiger.waterloo.edu (I'm a Wild One) (04/13/89)
Is there any software to perform FTP functions from within DOS. I have UUPC but it's not enough.
palowoda@megatest.UUCP (Bob Palowoda) (04/14/89)
From article <13275@watdragon.waterloo.edu>, by hpchang@tiger.waterloo.edu (I'm a Wild One): > > Is there any software to perform FTP functions from within DOS. I have UUPC > but it's not enough. Try KAQ9 version 4 or higher. It's in the 'msdos_comm' files area of my bbs. Use Zmodem or Kermit to download it, I'm haveing problems with X and Y modem at speeds less than 9600. I should have this fixed in a couple of days. ---Bob -- Bob Palowoda Work: {sun,decwrl,pyramid}!megatest!palowoda Home: {sun}ys2!fiver!palowoda BBS: (415)796-3686 2400/1200 Voice:(415)745-7749
rpw3@amdcad.AMD.COM (Rob Warnock) (04/21/89)
In article <42300011@uicsrd.csrd.uiuc.edu> kai@uicsrd.csrd.uiuc.edu writes: +--------------- | >/* Written by greg@dekalb.UUCP in uicsrd.csrd.uiuc.edu:comp.mail.uucp */ | >Since we don't have FTP access, I am looking for a program that allows FTP | >from a PC. Does such a thing exist? | Yes, such programs exist, as long as you have an ethernet card, and a well | connected ethernet network to connect your PC to. You will not be able to | FTP from your PC at home. +--------------- Not quite true. If you have an account on an Ethernet host which supports SLIP (Serial Line IP), you can dial it up and "become" a net node yourself. I do this on occasion [with an older version of KA9Q], and have found that on a Telebit modem, FTP over SLIP can give up to 10% greater throughput (disk-to-disk) than UUCP, EVEN IF THE TELEBIT IS USING UUCP "SPOOFING". [To get this, you need a large "window" size. I use MSS=512, WIN=4096.] The Clarkson packet-driver archives include a SLIP packet driver, which can be used (I am told) by either NCSA Telnet or Phil Karn's newest KA9Q package. I'm not quite ready to replace my UUCP mail links with dial-up SLIP + SMTP mail... but someday, someday... Rob Warnock Systems Architecture Consultant UUCP: {amdcad,fortune,sun}!redwood!rpw3 DDD: (415)572-2607 USPS: 627 26th Ave, San Mateo, CA 94403
plocher%sally@Sun.COM (John Plocher) (04/21/89)
>SLIP (Serial Line IP), you can dial it up and "become" a net node yourself.
For those who have done it:
Consider a company which has an internal internet (i.e., lots of machines
on lots of networks all gatewayed together). For discussion, let's call
this company Sun :-)
Consider the person who would like his machine at home to be on said
network using some method over dialup phone lines. For discussion, let's
call this person me :-)
Also assume that there are many others who would like to do the same
thing.
The question is: "How do you set it all up?"
That's cheating - there are really many questions:
What methods are there to allow one to dial in to a TCP connection.
What software do I need?
What measures does the Company need to take to facilitate this?
Does my home machine have to be on it's own subnet?
Most people I've talked to (who have not DONE it) say that it is simple -
just set up a SLIP connection and have fun. The people I know who have
tried it all tell me that they didn't get it working and that it
definitely is NOT simple.
Thanks,
-John Plocher
plocher@sun.comrpw3@amdcad.AMD.COM (Rob Warnock) (04/25/89)
In article <100285@sun.Eng.Sun.COM> plocher@sun.COM (John Plocher) writes: +--------------- | >SLIP (Serial Line IP), you can dial it up and "become" a net node yourself. | For those who have done it: ... The question is: "How do you set it all up?" | ...Most people I've talked to (who have not DONE it) say that it is simple - | just set up a SLIP connection and have fun. The people I know who have | tried it all tell me that they didn't get it working and that it | definitely is NOT simple. Thanks, -John Plocher | plocher@sun.com +--------------- I have done it [the line you quoted was mine]. There was indeed a little bit of hacking involved, but more-or-less straightforward (*if* you are already a kernel/network hacker). It wasn't particularly clean, and I can't really ship code at present, but can talk about it a little. Let's see, what was done...? 0. Environment: Main host is a VAX-11/780 running a (nearly) "stock" 4.3bsd. Remote host is an IBM PC running Phil Karn's "KA9Q" software. Both sides have Telebit modems with interfaces locked to 9600 baud [*don't* ask!]. 1. Small change to the 4.3 SLIP driver "if_sl.c" (and to the TTY line discipline switch table "linesw") to add modem control (basically paralleling that in normal TTY driver), as the original SLIP driver had none. Now, when a SLIP'd line drops, the SLIP controller program [see below] gets a SIGHUP. 2. Similar small change to "if_sl.c" to allow user program to "poll" the state of carrier [not really needed, but was a nice safety net]. 3. Wrote a new user program which parallels the function of "slattach", to solve a race condition, and some other stuff. The race condition was in the previous method of setting up a SLIP line: a. Do a "netstat" to see what SLIP ports are in use. b. Do an "ifconfig" on the lowest unused SLIP port, with the desired IP address. c. Do an "slattach" to cause the chosen TTY port to get that SLIP port, and hence, that IP address. The race should be obvious: What happens if *two* people do this at once? Solution: New program "duslip", which *first* does the (equivalent of) "slattach", which gets a SLIP port number for the TTY, *then* does the "ifconfig" knowing for sure what SLIP port it got. "Duslip" then hangs on the TTY line waiting for carrier to drop, whereupon it un-SLIPs the line and hangs it up (sending a SIGHUP to its parent *if* it's not "init"). 4. Since "duslip" has to be setuid root (to do the "ifconfig"), it checks for the user running it to be in group "slip", and to have an entry in a protected configuration file containing the range of allowed IP addresses for that user. 5. "Duslip" also creates a lock file [really an "in use" file] for the SLIP port, owned by the *user*, which if deleted causes "duslip" to un-SLIP the line. This lets you drop back to a normal shell, if you like. So what happens is that a user dials in, logs in as usual (note: this is the main security provided), runs "duslip" with either no args (accepting the default remote IP address) or an IP address arg (which must be in the allowable range), and *boom* is on the net. BUG: I still haven't fixed the bug in 4.3 "routed" that causes it to fail to see newly enabled point-to-point links (even if GATEWAY is defined), so sometimes a manual "route add" is needed to get other hosts on the net to see you. Now with standard KA9Q, I found the easiest way to get dialed in was to run Kermit on the PC and use it to dial the net host and log in as a notmal user. Then after running "duslip", execute KA9Q from beneath Kermit with a "!" command. That way, if you want (for any reason) to drop out of your SLIP session, you delete the lock file created by "duslip", exit from KA9Q, and there you are back in Kermit talking to a normal shell on the other end. Like I said, not at all clean, and certainly not as "automatic" as some people would like it, but it works. Rob Warnock Systems Architecture Consultant UUCP: {amdcad,fortune,sun}!redwood!rpw3 DDD: (415)572-2607 USPS: 627 26th Ave, San Mateo, CA 94403