Path: utzoo!utgpu!watserv1!watmath!att!linac!pacific.mps.ohio-state.edu!zaphod.mps.ohio-state.edu!swrinde!cs.utexas.edu!helios!mtecv2!josevela
From: josevela@mtecv2.mty.itesm.mx (Jose Angel Vela Avila)
Newsgroups: comp.protocols.tcp-ip.ibmpc
Subject: Re: NCSA Telnet and SLIP
Message-ID: <3477@mtecv2.mty.itesm.mx>
Date: 19 Jun 91 15:29:41 GMT
References: <1991Jun14.125410.2786@DMI.USherb.CA|> <NELSON.91Jun18145254@sun.clarkson.edu>
Organization: ITESM. Campus Monterrey
Lines: 28

nelson@sun.soe.clarkson.edu (Russ Nelson) writes:

|>In article <1991Jun14.125410.2786@DMI.USherb.CA> bussiere@DMI.USherb.CA (Luc Bussieres) writes:

|>   	When I have tested it, I used the packet driver configuration 
|>   and I install the slip8250 packet driver using the packet driver class
|>   to 1 ( this is the only one the NCSA Telnet seemed to recognize ). Is
|>   this a correct configuration?

|>Sounds like your copy of NCSA Telnet doesn't recognize type 6 (SLIP)
|>packet drivers.  Changing the class to 1 isn't going to work because that
|>will cause NCSA Telnet to generate Ethernet frames over your SLIP link.


 Try with NCSA version from Clarkson, called CUTCP, it is on 
 sun.soe.clarkson.edu I think....


 I've trying it with SLIP and Cisco and it works very well, after some minor
  problems relationes with MTU ( I set it to 256 on the PC and 1024 on the Cisco
  and then it works without fragmentation )


Jose A. Vela A.
josevela@mtecv2.mty.itesm.mx
   ITESM

C. Monterrey