At 3:55 PM -0800 3/9/98, Bill Studenmund wrote:
>On Mon, 9 Mar 1998, Henry B. Hotz wrote:
>
>[atalk problems]
>
>> Any suggestions for how to debug this situation?
>
>Do you have access to a copy of EtherPeek? Probably not if you're snubbing
>the Net.gods. :-) It'd be a good thing to see what's up. Also, try running
>tcpdump. I don't know how to configure it, but it supposedly can do
>appletalk.

Well it's listed in JPL's software catalog at $630.01.  At that price I
think I'll give tcpdump a try first.  No, I won't because the man page says
it only supports kip-encapsulated ddp, not native ethertalk packets.

Backup:  there is an Appletalk-aware version of Solaris snoop on
playground.sun.com, but I need to move my Solaris machine to the same
subnet first.  Since this subnet uses switched repeaters I may need to
temporarily install my own passive repeater as well (and hope the Net.gods
don't notice and charge me $1500 for it).  *sigh*
>

>> The NetBSD box registers itself as a printer and printing to it from mc0
>> results in printout on the ae0-connected HP (and an error message about no
>> .ppd file).  I have no config files for the printer daemons anywhere.
>
>You should be able to get .ppd's from Adobe.

Are they the same as the ones used by LaserWriter 8?  Probably I should
just  disable papd.  I'd rather run a router than a gateway.  Except for
the performance issue, of course.
>

>> atalkd.conf file gets trashed.  (Seems like -seed information should not be
>> changed by atalkd.)
>
>I'll try to look into this, though atalkd is not my friend. :-(

Thanks.

Repeating my comment in private email:  Making atalkd.conf read-only makes
some sense since the machine is on all the time, but it may be required to
change the node assignment on the primary interface and a read-only config
file would probably prevent that.
>
>> Separate Issue
>>
>> What was the fix for the boot hang while setting ttyflags?  This one only
>> bites me occasionally, but it's the number 2 reason my machine won't boot
>> itself.
>
>I can send you patches to try in private EMail. It's not fully fixed yet.
>Basically we end up enabling interrupts which shouldn't be enabled, and
>the open inputs end up ringing.

That fits.  I was hoping there was a workaround like disabling something or
setting the baud rate way low.  Would it help to monkey with the booter
settings, or is the problem too late in the process for that to help?

Better yet can you suggest a loopback wiring for the serial plug that will
hold all the relevant signals in place?  Ready signals may strobe as the
interface is configured.  Perhaps wiring Tx data + or - to all the input
lines?

I can help you test patches as long as 1-week turnaround is OK.  Otherwise
I'd rather get a hardware solution that works.

Signature failed Preliminary Design Review.
Feasibility of a new signature is currently being evaluated.
h.b.hotz@jpl.nasa.gov, or hbhotz@oxy.edu