Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!usc!snorkelwacker.mit.edu!mintaka!spdcc!dyer
From: dyer@spdcc.COM (Steve Dyer)
Newsgroups: comp.protocols.appletalk
Subject: Re: RU-CAP: what should atlook and atlooklws return?
Summary: more bugs on ethernets without AT routers
Message-ID: <4886@spdcc.SPDCC.COM>
Date: 14 Nov 90 18:21:42 GMT
References: <4880@spdcc.SPDCC.COM>
Reply-To: dyer@ursa-major.spdcc.com (Steve Dyer)
Organization: S.P. Dyer Computer Consulting, Cambridge MA
Lines: 29

In article <4880@spdcc.SPDCC.COM> dyer@ursa-major.spdcc.com (Steve Dyer) writes:
>However, I can't seem to get papif to work.
>I thought I'd use "atlook" or "atlooklws" to tell me what's on the
>ethertalk net, and to give me an idea of what should be in the
>field for /etc/cap.printers.  However, both "atlook" and "atlooklws"
>simply sit there for a couple of seconds and then return nothing.
>Since there are three ethertalk agents on the net right now (the Mac
>IIfx, the EtherPrint box and the Sun), I'd think that "atlook" would
>return something!  What are typical outputs returned by these applications?
>Does anyoen know what I might be doing wrong such that these would
>not be returning anything?  Where should I look next?

This appears to be another problem with RU-CAP/Ethertalk on nets
without a router.  I suddenly realized that I *did* have a potential
Appletalk router on my network--my Cisco gateway!  I enabled Appletalk
routing on the Cisco (not that it would be routing to anywhere), *manually*
patched addresses in /etc/cap.ether.shared for the gateway and net addrs
using adb (it didn't just "come up" unfortunately).

Having done this, and then restarting all the CAP daemons, atlook and
atlooklws return everything that I'd expect.  It seems to work fine now.

I'm not sure what the answer is if you really DON'T have a router.
I haven't looked at the code to figure this out.

-- 
Steve Dyer
dyer@ursa-major.spdcc.com aka {ima,harvard,rayssd,linus,m2c}!spdcc!dyer
dyer@arktouros.mit.edu, dyer@hstbme.mit.edu