Date: Thu, 17 Aug 1995 16:42:07 +0930 (CST) From: Michael Smith <msmith@atrad.adelaide.edu.au> To: doc@freebsd.org Subject: SLIP FAQ, a quick hint for whoever is updating... Message-ID: <199508170712.QAA01150@genesis.atrad.adelaide.edu.au>
next in thread | raw e-mail | index | archive | help
Just to pass along a useful result I've achieved maintaining a dialout SLIP link, for the use of whomever may be maintaining/updating the SLIP FAQ. So far, every solution I've seen for maintaining a SLIP link has involved kermit, which just doesn't get along at all well with SLIP lines. A much simpler, and easily as functional, approach is to make use of slattach's ability to detect carrier, and its redial-command feature. If we assume a 'standard' login process involving a "login:" and "password:" prompt, and a Hayes-compatible modem appropriately configured, we can use the chat program to automate dialling. We prepare a chat script to do the work : /root/chat.script : ABORT BUSY ABORT 'NO CARRIER' TIMEOUT 60 '' ATZ OK-ATZ-OK ATDTxxx-xxxx ogin:--ogin: <username> ssword: <password> And a shell script as a wrapper to avoid redialling endlessly due to a line or modem fault : /root/slipdial : #!/bin/sh until chat -f /root/chat.script; do sleep 300; done (remember to chmod +x /root/slipdial) Now invoke slattach as : slattach -ahs 38400 -r /root/slipdial /dev/cuaa0 (Replace cuaa0 with whatever your serial port is) -- ]] Mike Smith, Software Engineer msmith@atrad.adelaide.edu.au [[ ]] Genesis Software genesis@atrad.adelaide.edu.au [[ ]] High-speed data acquisition and [[ ]] realtime instrument control (ph/fax) +61-8-267-3039 [[ ]] My car has "demand start" -Terry Lambert UNIX: live FreeBSD or die! [[
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199508170712.QAA01150>