<HTML ><HEAD ><TITLE > On the client side </TITLE ><META NAME="GENERATOR" CONTENT="Modular DocBook HTML Stylesheet Version 1.63 "><LINK REL="HOME" TITLE=" Serial Laplink HOWTO " HREF="index.html"><LINK REL="PREVIOUS" TITLE=" On the server side " HREF="x24.html"><LINK REL="NEXT" TITLE=" Connecting... " HREF="x157.html"></HEAD ><BODY CLASS="SECT1" BGCOLOR="#FFFFFF" TEXT="#000000" LINK="#0000FF" VLINK="#840084" ALINK="#0000FF" ><DIV CLASS="NAVHEADER" ><TABLE WIDTH="100%" BORDER="0" CELLPADDING="0" CELLSPACING="0" ><TR ><TH COLSPAN="3" ALIGN="center" >Serial Laplink HOWTO</TH ></TR ><TR ><TD WIDTH="10%" ALIGN="left" VALIGN="bottom" ><A HREF="x24.html" >Prev</A ></TD ><TD WIDTH="80%" ALIGN="center" VALIGN="bottom" ></TD ><TD WIDTH="10%" ALIGN="right" VALIGN="bottom" ><A HREF="x157.html" >Next</A ></TD ></TR ></TABLE ><HR ALIGN="LEFT" WIDTH="100%"></DIV ><DIV CLASS="SECT1" ><H1 CLASS="SECT1" ><A NAME="AEN116" >3. On the client side</A ></H1 ><P > After having configured the server, the client is easy. The <SPAN CLASS="QUOTE" >"/etc/ppp/options"</SPAN > file has a single entry: </P ><TABLE BORDER="0" BGCOLOR="#E0E0E0" WIDTH="100%" ><TR ><TD ><FONT COLOR="#000000" ><PRE CLASS="PROGRAMLISTING" >#/etc/ppp/options lock </PRE ></FONT ></TD ></TR ></TABLE ><P > The serial port on my client is <SPAN CLASS="QUOTE" >"/dev/ttyS0"</SPAN > (COM1), so I also have to create a <SPAN CLASS="QUOTE" >"/etc/ppp/options.ttyS0"</SPAN > file: </P ><TABLE BORDER="0" BGCOLOR="#E0E0E0" WIDTH="100%" ><TR ><TD ><FONT COLOR="#000000" ><PRE CLASS="PROGRAMLISTING" >#/etc/ppp/options.ttyS0 115200 crtscts local user zaphod noauth </PRE ></FONT ></TD ></TR ></TABLE ><P > Only a few new options in this file. Note that the speed on server and client has to be the same (here it is 115200). With <SPAN CLASS="QUOTE" >"user zaphod"</SPAN > the client user name is specified. This user name has to correspond to an entry in the <SPAN CLASS="QUOTE" >"/etc/ppp/pap-secrets"</SPAN > file of the client and has to be a valid user name on the server. The <SPAN CLASS="QUOTE" >"noauth"</SPAN > option specifies that the peer (server) does not have to authenticate itself to the client. </P ><P > The last bit: setting the client name (user name) and its secret (password) in the <SPAN CLASS="QUOTE" >"/etc/ppp/pap-secrets"</SPAN > file: </P ><TABLE BORDER="0" BGCOLOR="#E0E0E0" WIDTH="100%" ><TR ><TD ><FONT COLOR="#000000" ><PRE CLASS="PROGRAMLISTING" >#/etc/ppp/pap-secrets # Secrets for authentication using PAP # client server secret IP addresses zaphod * gargleBlaster </PRE ></FONT ></TD ></TR ></TABLE ><P > So user <SPAN CLASS="QUOTE" >"zaphod"</SPAN > uses a password <SPAN CLASS="QUOTE" >"gargleBlaster"</SPAN >, which should get him into the system. Note that these files contain sensitive information, make sure you set the permissions on them correctly. </P ><DIV CLASS="SECT2" ><H2 CLASS="SECT2" ><A NAME="AEN135" >3.1. Start the client</A ></H2 ><P > On the command line, type: </P ><TABLE BORDER="0" BGCOLOR="#E0E0E0" WIDTH="100%" ><TR ><TD ><FONT COLOR="#000000" ><PRE CLASS="PROGRAMLISTING" >/usr/sbin/pppd /dev/ttyS0 nodetach </PRE ></FONT ></TD ></TR ></TABLE ></DIV ><DIV CLASS="SECT2" ><H2 CLASS="SECT2" ><A NAME="AEN139" >3.2. Connecting to an MS Windows server</A ></H2 ><P > What if you want to make a connection to a Windows server? Again we'll need the <SPAN CLASS="QUOTE" >"connect"</SPAN > option and a chat script. Add the following line to your <SPAN CLASS="QUOTE" >"/etc/ppp/options.ttyS0"</SPAN > file: </P ><TABLE BORDER="0" BGCOLOR="#E0E0E0" WIDTH="100%" ><TR ><TD ><FONT COLOR="#000000" ><PRE CLASS="PROGRAMLISTING" >connect chat -v -f /etc/ppp/scripts/winserver.chat </PRE ></FONT ></TD ></TR ></TABLE ><P > Also create the chat script <SPAN CLASS="QUOTE" >"/etc/ppp/script/winserver.chat"</SPAN >: </P ><TABLE BORDER="0" BGCOLOR="#E0E0E0" WIDTH="100%" ><TR ><TD ><FONT COLOR="#000000" ><PRE CLASS="PROGRAMLISTING" >TIMEOUT 10 '' CLIENT\c </PRE ></FONT ></TD ></TR ></TABLE ><P > This makes the client send the <SPAN CLASS="QUOTE" >"CLIENT"</SPAN > string before trying to start the PPP connection. </P ></DIV ><DIV CLASS="SECT2" ><H2 CLASS="SECT2" ><A NAME="AEN150" >3.3. Setting up an MS Windows (95) client</A ></H2 ><P > To connect to the server using windows, you use the Direct Cable Connection program, and set it up as <SPAN CLASS="QUOTE" >"guest"</SPAN >. In order for the windows client to connect at full speed (or at all), you will have to change the communication speed of direct cable connection. To do this, go to Control Panel->System->Device Manager->Modems and select the serial cable. Proceed to the 'modem' option and select a maximum speed of 115200 or whatever your linux computer is set to. Now, it is important that you reboot at this stage, or it WILL NOT WORK (at least with Microsoft windows 95 version A), I am not sure about others. </P ></DIV ><DIV CLASS="SECT2" ><H2 CLASS="SECT2" ><A NAME="AEN154" >3.4. Oddly enough...</A ></H2 ><P > Oddly enough I created a Linux server that has to connect to both Linux and Windows computers, so I found myself with the odd situation of having to setup both Linux systems such that they would connect to Windows servers and clients! </P ></DIV ></DIV ><DIV CLASS="NAVFOOTER" ><HR ALIGN="LEFT" WIDTH="100%"><TABLE WIDTH="100%" BORDER="0" CELLPADDING="0" CELLSPACING="0" ><TR ><TD WIDTH="33%" ALIGN="left" VALIGN="top" ><A HREF="x24.html" >Prev</A ></TD ><TD WIDTH="34%" ALIGN="center" VALIGN="top" ><A HREF="index.html" >Home</A ></TD ><TD WIDTH="33%" ALIGN="right" VALIGN="top" ><A HREF="x157.html" >Next</A ></TD ></TR ><TR ><TD WIDTH="33%" ALIGN="left" VALIGN="top" >On the server side</TD ><TD WIDTH="34%" ALIGN="center" VALIGN="top" > </TD ><TD WIDTH="33%" ALIGN="right" VALIGN="top" >Connecting...</TD ></TR ></TABLE ></DIV ></BODY ></HTML >