🚀 go-pugleaf

This is one of the things I ran into here at rutgers last year...
We had exceeded the number of characters allocated for zone name
space since we used long zone names. I got around the problem
by generating a new KIP gw.srec which supports 128 routes, 64 zones,
and has a 1024 character buffer size for zone names. We are currently
using about 60 network numbers, and 22 zones. This gateway code works
on our KFPS-3s and KFPS-4s. K* supposedly uses dynamically allocated
tables, so it should be fine, however I haven't tested it since I am
awaiting the new version that supports the NIC assigned UDP ports.
There are however may be some side effects. This may not be due to the
gateway code, but with atalkad running under SunOS 4.0, however it is 
worth mentioning anyway. Atalkad may hang all the Kboxes if you
attempt to push around the configuration and routing info using 
"atalkad boot". You can get a kbox to re-take the config info by
either powercycling it or using the fastpath manager and using the 
"restart" option.

I am hoping it will be possible to get around the limitations of KIP
by switching to using Ethertalk routing using our Cisco gateways.
I haven't has a chance to test this out yet since I am still awaiting
the new K* code. Maybe I need to make 20 phone calls in one day to get
someone there to ship it immediately :-)  Anyone else tried it yet?



Rakesh Patel.