Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!swrinde!ucsd!ucbvax!duc220.uni-duisburg.de!hj412fr
From: hj412fr@duc220.uni-duisburg.de (Martin Anantharaman)
Newsgroups: comp.sys.apollo
Subject: Re:  Routed (Still)
Message-ID: <9011020740.AA15690@duc220.uni-duisburg.de>
Date: 2 Nov 90 07:40:55 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: The Internet
Lines: 35


	I got a lot of responses back on my last routed query saying that it was
	not working because I had /etc/routed -f -h instead of /etc/routed -f.
	Actually, my -h was a temporary hack, in an attempt to do anything:) to
	get the thing to work.  Right now, I have it back with the correct
	/etc/routed -f and it still dies regularly.  (Note: when I say die, the
	routed process is still up, but it does nothing in the way of routing.  If
	it is restarted at this point, it works fine.)  One person out there said
	that the routed for 10.2 was just bad, and that I should get the tape
	with the latest patch on it.  In the meantime, does anyone have a temporary
	fix so that I can keep my non-gateway machines on the net while we are
	waiting for the patch?
	
	Shannon Appel
	
Now, I did not really read the postings thta led up to this, BUT as I
am successfully running a ATR gatewayed to a subdomain of the Internet,
here are a couple of things that helped me:

1) Run routed interactively with -t to see what your routeds are up to.

2) Pay attention to your subnet-masks: When I did 1) I found that the
routeds were basically ignoring the gateway routed, because they did
not think it was on the same net.

3) Maybe use the -g flag on the gateway routed so it keeps offering its
routes.

Martin Anantharaman

FB7, FG7 (Mechanik)		Work:	+49 (203) 379-3336
Universitaet -GH- Duisburg	Home:	+49 (203) 37 65 89
Lotharstr. 1			FAX:	+49 (203) 379-3052
4100 Duisburg 1			E-Mail: hj412fr@duc220.uni-duisburg.de
West Germany