Return to BSD News archive
Path: sserve!newshost.anu.edu.au!harbinger.cc.monash.edu.au!simtel!news.kei.com!news.mathworks.com!zib-berlin.de!news.tu-chemnitz.de!irz401!narcisa.sax.de!not-for-mail
From: j@narcisa.sax.de (J Wunsch)
Newsgroups: comp.unix.bsd.freebsd.misc
Subject: Re: SLIPLOGIN Problem..
Date: 12 Jun 1995 13:44:02 +0200
Organization: Private U**x site, Dresden.
Lines: 27
Message-ID: <3rh9a2$mke@bonnie.tcd-dresden.de>
References: <3rcjh4$bs6@ucsbuxb.ucsb.edu>
Reply-To: joerg_wunsch@uriah.heep.sax.de
NNTP-Posting-Host: 192.109.108.139
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
Loren Koss <loren@beauty.ucsb.edu> wrote:
>I got the slip.hosts file to work and the slip.login file so that I can
>dial in and it claims that it is starting slip, however, I can only ping
>my machine t\and the host machine.. Nothing else. Do I somehow have to
>setup routing? I read that somewhere in the handbook.
Of course, you do! The simplest way is
route add default <remote-IP>
It assumes that <remote-IP> is willing to forward all packets to you,
and that the remote side has promoted the routing information for
<your-IP> to the outside world.
Don't forget to
route delete default
after shutting down the SLIP connection.
Of course, if you happen to have a local Ethernet or other stuff, it
will be more complicated.
--
cheers, J"org private: joerg_wunsch@uriah.heep.sax.de
http://www.sax.de/~joerg/
Never trust an operating system you don't have sources for. ;-)