Return to BSD News archive
Path: sserve!newshost.anu.edu.au!harbinger.cc.monash.edu.au!bunyip.cc.uq.oz.au!munnari.oz.au!constellation!news.ysu.edu!usenet.ins.cwru.edu!howland.reston.ans.net!news.sprintlink.net!news.clark.net!rwatson From: rwatson@clark.net (Robert Watson) Newsgroups: comp.os.386bsd.bugs Subject: Re: Slattach?! Date: 3 Feb 1995 13:56:11 GMT Organization: The Star-Lit BBS, Bethesda, Maryland, USA Lines: 30 Distribution: world Message-ID: <3gtclr$e9e@clarknet.clark.net> References: <3gsafv$g35@giga.bga.com> NNTP-Posting-Host: clark.net Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-Newsreader: TIN [version 1.2 PL2] Our solution to this has always been to stored the PID of the slattach session in /var/run, then run a cron script every ten minutes that pings the remote host. If there is a route to the remote host, then it works. If not, kill slattach and start a new one. This is a cludge. You can also define a redial command using -c (I believe) -- check the man pages. What we'd really like to see is a way to get slattach to raise DTR even after carrier is lost. Or maybe on a timed delay. Our modem autodials if its disconnected and DTR is raised, so what we used to do (when routing under BSDI) was stty -f /dev/tty00 which had the side effect of raising DTR, causing a redial. being able to kill -HUP PID slattach and having it flash DTR would be really nice ;). Clint Todish (ctodish@levelone.com) wrote: : I've recently upgraded a SLIP -> Ethernet routing machine that was running FreeBSD 1.1 to FreeBSD 2.0. Besides having some : problems with routing, I've not been able to get slattach to work properly. It worked fine in the previous release, but now it won't : release /dev/tty when there's no carrier. My dialer just sits there and reports 'device in use' or something similar. Has anyone : experienced anything like this? What can I do? This has left my routing machine alone and suspect to sudden death, considering : that it won't reconnect if a connection is lost. : Regarding my routing problems - when I try to enter a static route to another macine on my ether, I get a rude error message : stating 'arpresolve: can't allocate llinfo'. It only happens when I use the -interface option. (Which, again, worked under 1.1) : thanks for any info! : C