Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Path: utzoo!utgpu!water!watmath!clyde!cbosgd!ucbvax!JESSICA.STANFORD.EDU!khanna From: khanna@JESSICA.STANFORD.EDU.UUCP Newsgroups: comp.protocols.tcp-ip.ibmpc Subject: Re: SLIP for IBM-PC Message-ID: <8711251829.aa07126@Louie.UDEL.EDU> Date: Wed, 25-Nov-87 18:22:00 EST Article-I.D.: Louie.8711251829.aa07126 Posted: Wed Nov 25 18:22:00 1987 Date-Received: Sun, 29-Nov-87 06:01:26 EST References:<8711251748.aa06663@Louie.UDEL.EDU> Sender: daemon@ucbvax.BERKELEY.EDU Distribution: world Organization: The ARPA Internet Lines: 19 At Stanford we are planning to add SLIP facility to our SU-PC/IP package. POP client for PCs already exists and it would definiteley be supported over SLIP. We have looked at many SLIP implementations and my concern is that most implementations require PCs to have IP addresses in the custom file. From my experience with PCs on ethernet, I have realized that, no matter what you do, people are going to make copies of PC/IP diskettes and ignore to change IP address. This results in multiple machines with same IP address. This was the reason for resorting to RARP and BOOTP for allocating IP addresses to PCs. Does anyone else share my concern? I am looking for a scheme in which an IP address would be dedicated to each line on the server. During the handshake this address could be assigned to the PC for the duration of the session. I plan to raise this issue at the Interoperability meeting. raman khanna