🚀 go-pugleaf

Can anyone send me a Koto workaround to fix its poor IP implementation ?

I've couple of D-machines which are on the same local ethernet segment as my
Suns (a mix of Sparc's and mc68020, all under SunOS 4.0.x).  And whenever my
Sun generates UDP broadcasts where the broadcast packet is all 1's (i.e. 0xff)
then the \10MBWATCHER breaks, saying illegal address class is -1.

A BT! displays this order :-

	\IPNETADDRESS  [ADDRESS bounded to -1]
	\IP.LEGAL.ADDRESS  [ADDRESS bounded to -1]
	\IP.LOCAL.DESTINATION
	\HANDLE.RAW.IP
	\HANDLE.RAW.PACKET
	10MBWATCHER

All you need to do is 'nslookup -l <servername>' on your Sun.  Apparently,
nslookup generates an UDP broadcasts if you want to use another nameserver
other than the default.

You can "look at" the packet by doing this

	etherfind -v -src voodoo1 -broadcast -byte 1=0xff   

		OR if you want to be pedantic

	etherfind -v -src voodoo1 -broadcast -byte 1=0xff 2=0xff 3=0xff

on another Sun while on your own Sun (voodoo1 in this case), you do 
'nslookup -l anotherserver'.

Well, I'll be interested in hearing any workaround on this.

(We've a Class C net, subnetted from the campus Class B net and the netmask is
0xfffffc00 but I don't think that really matters).
--

Eric Ho  
Princeton University
eho@clarity.princeton.edu