Return to BSD News archive
Xref: sserve comp.os.386bsd.questions:13266 alt.winsock:10246
Path: sserve!newshost.anu.edu.au!harbinger.cc.monash.edu.au!msuinfo!agate!howland.reston.ans.net!news.sprintlink.net!indirect.com!bslnet.com!tsimes
From: tsimes@bslnet.com (Thomas D. Simes)
Newsgroups: comp.os.386bsd.questions,alt.winsock
Subject: Routing Problem
Date: 19 Sep 1994 15:32:34 GMT
Organization: Internet Direct, Inc.
Lines: 33
Message-ID: <35kaui$ph9@herald.indirect.com>
NNTP-Posting-Host: 165.247.36.10
X-Newsreader: TIN [version 1.2 PL2]
Hello all!
We are having a puzzling routing problem at our site - at least I
think that it is a routing problem. Here is the situation:
We are running a 386bsd 1.1.5.1 box as an Internet node with
modems attached for dial-in service. This bsd box is attached
to the net using a router and CSU/DSU running frame relay to
our provider. Both the router and bsd box can ping each
other and the net without a problem. The problem comes
when I SLIP into the bsd machine using Trumpet winsock 1.0a.
While the SLIP'd machine and the bsd box it is attached to can
ping each other, the SLIP'd machine cannot see our router or
the rest of the net (naturally). So far I have tried the
following to no avail.
1. Switched from static table routing to RIP w/ routed
2. Set the gateway in winsock to the bsd box, our router,
our provider's gateway - no luck.
3. Set routed flag to -s to force route broadcasting
4. Set up the router as passive and then active in /etc/gateways
5. Danced around box while waving magic voodo chicken
Just kidding about the chicken - but if it would help! ;)
Anyway, if this sounds familiar to anyone out there, I sure
would appreciate a hint! (So would our provider as I have
been driving them crazy with this since Fri)
--
====================================================================
Thomas D. Simes "There can't be a crisis now, my schedule is full"
tsimes@bslnet.com -Henry Kissinger