🚀 go-pugleaf

RetroBBS NetNews Server

Inspired by RockSolid Light RIP Retro Guy

Article View: comp.sys.next.sysadmin
Article #1908

Re: Question regarding SLIP for 3.0

#1908
From: Derek Taubert
Date: Sat, 21 Nov 1992 04:18
48 lines
2554 bytes
> Okay I give up.  I'm using the SLIP_920904 slip and I'm running into 
> some problems which I can't seem to get around.  Here is the scenario.
> I've got a slipclient and a sliphost, and I can dial the sliphost from the
> slipclient easily, but I can't seem to convince the slipclient that there
> is a network route to all the other hosts on the network.

First off, your default routing for slipclient should be to sliphost over the
SLIP interface.  Got that?  I thought so.

> The network looks something like this
> 
>     (sliphost)--------network A--------(Sun running routed)----network B----.
>       |
>       modem------network C-------modem--slipclient
> 
> Network A, B, and C all have different class C network addresses.  All
> hosts on A and B know how to get to each other.  But from the slipclient
> I can't get to anybody except the sliphosts.  I've tried running routed
> on both the slipclient and the sliphost, but when I run routed in sliphost
> after some time the entry in the routing table (of sliphost) for the route 
> to slipclient will be deleted by routed and so the slipclient will just
> hang.

Now, I'm going to complain about you using routed.  From what you've
drawn here, there is NO reason that you should be using dynamic routing.
Static entries in the machines routing tables will do you just fine, as there
is only one possible path per machine pair.

The default routing for the sliphost should be network A, the Sun should have
an entry for routing to network A, and ick...  Why does the SLIP interface have
to have a different netid?  Make that sucker network A, and your life will be
much easier.  Course, I suppose you could also add an entry for network C on
the Sun (gateway = sliphost), but I would opt for changing network C if at all
possible.

Summary:
slipclient
	route add default sliphost 0
sliphost
	route add default Sun 0
	route add slipclient slipclient 0
Sun
	route add net networkA sliphost 0
	route add net networkC sliphost 1

That should do the trick (I think).

Derek Taubert
Technical Details
Message-ID: <1992Nov21.041801.9539@slab.slip.uiuc.edu>
Path: arc1-ca.pugleaf.net!sparky!uunet!europa.asd.contel.com!emory!sol.ctr.columbia.edu!news.unomaha.edu!slab.slip.uiuc.edu!derek
References: <By07Cs.Ao@oceania.com>

Show Full Headers
Complete Article Headers
Newsgroups: comp.sys.next.sysadmin
Path: arc1-ca.pugleaf.net!sparky!uunet!europa.asd.contel.com!emory!sol.ctr.columbia.edu!news.unomaha.edu!slab.slip.uiuc.edu!derek
From: derek@slab.slip.uiuc.edu (Derek Taubert)
Subject: Re: Question regarding SLIP for 3.0
Message-ID: <1992Nov21.041801.9539@slab.slip.uiuc.edu>
Reply-To: derek@slab.slip.uiuc.edu (Derek Taubert)
Organization: Damage, inc.
References: <By07Cs.Ao@oceania.com>
Date: Sat, 21 Nov 1992 04:18:01 GMT
Lines: 48