Path: utzoo!utgpu!watserv1!watmath!att!pacbell.com!mips!swrinde!zaphod.mps.ohio-state.edu!samsung!uunet!apctrc!zjat02 From: zjat02@trc.amoco.com (Jon A. Tankersley) Newsgroups: comp.protocols.tcp-ip Subject: SLIP implementation questions Message-ID: <2486@apctrc.UUCP> Date: 27 Dec 90 06:22:45 GMT Sender: news@trc.amoco.com Organization: Amoco Production Company Lines: 35 X-Checksum-Snefru: 148fd62f 22ca474c 828c7442 a1d4be11 We're looking at SLIP for connecting remote PC systems with our UNIX boxes and I've got some questions on implementation: Setting up the UNIX hosts with sliplogin (from slip4.0) is not a big problem, but SunOS 4.0.3 doesn't allow it easily from ttytab. This isn't a big problem either, but I have a limited number of ports to connect to via slip. Has anyone tried to implement sliplogin as part of the cycle on the getty baud rate cycle? I was thinking of having sliplogin first, then break for the different speeds of getty. On a PC, in this case with an MNP modem (19200/9600/...) running PC/TCP software, starting up slip, how do I get the modem to dial the proper number? I also have some special commands and passwords to get through some security to set up the connection. Is that possible? I tried using procomm to call, then try and connect, but either dropping or not dropping procomm didn't let slip work. And none of the PC/TCP utilities work without a connection in place. Any ideas? Is there any way to assign the SLIP IP addresses on the fly for the remote connections. We're going to have N PC's and only M connections (M /* nobody knows the trouble I .... */ tank@apctrc.trc.amoco.com ..!uunet!apctrc!tank