Thread View: comp.sys.next.sysadmin
2 messages
2 total messages
Started by Kambiz Aghaiepour
Fri, 20 Nov 1992 07:26
Question regarding SLIP for 3.0
Author: Kambiz Aghaiepour
Date: Fri, 20 Nov 1992 07:26
Date: Fri, 20 Nov 1992 07:26
31 lines
1919 bytes
1919 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.
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.
What am I doing wrong? Could someone please give me the rundown on
what needs to be in place to get the above network to be happy.
Thanks in advance.
--Kambiz
--
\o__O o Kambiz Aghaiepour - | kambiz@oceania.com o o
\_ /|\ Oceania Health Care Systems |\- netcom!oceania!kambiz //\ //\
|\ |\ 325 Lytton Ave, Suite 400 | | FAX: (415) 322-0142 // //
/ / |/ Palo Alto, CA 94301 | Voice: (415) 322-0127 |\ ||
Re: Question regarding SLIP for 3.0
Author: Derek Taubert
Date: Sat, 21 Nov 1992 04:18
Date: Sat, 21 Nov 1992 04:18
48 lines
2554 bytes
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
Thread Navigation
This is a paginated view of messages in the thread with full content displayed inline.
Messages are displayed in chronological order, with the original post highlighted in green.
Use pagination controls to navigate through all messages in large threads.
Back to All Threads