Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!utgpu!water!watmath!clyde!rutgers!ucla-cs!ames!ucbcad!ucbvax!HARVARD.HARVARD.EDU!elvy%mbcrr
From: elvy%mbcrr@HARVARD.HARVARD.EDU.UUCP
Newsgroups: comp.protocols.tcp-ip
Subject: dialup tcp
Message-ID: <8705111920.AA14597@ucbvax.Berkeley.EDU>
Date: Mon, 11-May-87 13:36:54 EDT
Article-I.D.: ucbvax.8705111920.AA14597
Posted: Mon May 11 13:36:54 1987
Date-Received: Wed, 13-May-87 04:38:37 EDT
Sender: daemon@ucbvax.BERKELEY.EDU
Distribution: world
Organization: The ARPA Internet
Lines: 19

We have had TCP/IP running over telephone lines for some time, now, but
it doesn't exactly conform to your specs.  A server runs on each end of
the telephone line, alternately (randomly) waiting for a call or attempting
to make one.  Once a connection is established, another process is run.
When that process finishes, or when the connection is lost, the server
hangs up the phone and attempts to re-establish the connection.

As the "process", we use a program that keeps the line open (the server
sets stdin and stdout to be the telephone line before execing the new process)
and keeps it in SERIAL TCP line discipline (see kernel mods I sent to
this mailing list in January 1984).  In addition, we ifconfig the serial
interface and route packets over it.

Crude in concept, perhaps, but we have had a reliable Internet connection
running more-or-less all the time for the past year over a distance that
precludes normal cable connections and for a fraction of the cost of
leased lines.

Marc (elvy@mbcrr.harvard.edu)