Return to BSD News archive
Xref: sserve comp.os.386bsd.questions:7387 comp.os.386bsd.misc:1711 Newsgroups: comp.os.386bsd.questions,comp.os.386bsd.misc Path: sserve!newshost.anu.edu.au!munnari.oz.au!news.Hawaii.Edu!ames!elroy.jpl.nasa.gov!decwrl!netcomsv!netcom.com!hasty From: hasty@netcom.com (Amancio Hasty Jr) Subject: Re: FreeBSD - please help me setup SLIP Message-ID: <hastyCHs80x.71n@netcom.com> Organization: Netcom Online Communications Services (408-241-9760 login: guest) References: <CHn76t.921@interlan.Interlan.COM> <hastyCHovxK.9wG@netcom.com> <36697@ksr.com> Date: Thu, 9 Dec 1993 19:12:32 GMT Lines: 26 In article <36697@ksr.com> jfw@ksr.com (John F. Woods) writes: >While we're on the topic, I have a SLIP configuration question of my own >(actually for NetBSD, but I suspect it's generic to all BSDs). > >I had two SLIP lines, one running to a Macintosh, the other used to connect >to the place I work via modem. Neither SLIP interface was in use all the >time, and therein (probably) lies the problem. I was finding that since >slattach just grabs a random sl unit, either sl0 or sl1 could get bound to >a given SLIP line, but the routes weren't getting torn down when each line >was taken down, so about half the time I wound up being unable to route >packets correctly. Is there some particular way that one is supposed to >arrange a situation like this? Or is the only solution what I eventually >did -- get a pair of ethernet boards so I only need one SLIP line :-). Just do route flush, then re-specify your routes. dirty but this should do the trick Amancio -- This message brought to you by the letters X and S and the number 3 Amancio Hasty | Home: (415) 495-3046 | ftp-site depository of all my work: e-mail hasty@netcom.com | sunvis.rtpnc.epa.gov:/pub/386bsd/X