[netatalk-admins] Using netatalk in a large, mission-critical environment


Subject: [netatalk-admins] Using netatalk in a large, mission-critical environment
From: Sean A. Snyder (ssnyder@cecom.com)
Date: Thu Sep 24 1998 - 11:13:39 EDT


Greetings!

I'm writing to find out if anyone on this list is using netatalk in a large
environment (larger than 300 users per server) that is 24x7, or nearly 24x7?

I'm in a situation where with a product similar to Netatalk where I find
myself limited to 127 appletalk connections to my file server. Apparently,
this limitation is based upon the 8-bit socket identification number in older
versions of the Appletalk stack. According to section 4-5 of Apple's "Inside
Appletalk" book (copywrite 1990), sockets 1-127 are reserved for
statically-assigned sockets (SAS's), leaving sockets 128-254 for use by our
AppleShare clients, hence we get errors when we try to make that 128th
connection to the server.

Does anyone know if Netatalk is also subject to this 8-bit
socket-identification number issue, or has a workaround been found or been
created in newer versions of Appletalk? Will using the asun IP patches get me
around this limitation if it exists (i.e. unlimited number of IP connections)?

Lastly, in the readmes for the 1.4b2+asun2.0a18.2 version that I downloaded,
it mentions that the STREAMS module is buggy on Solaris, and that I'd want to
get a beta of the new STEAMS module from umich. How would I go about
obtaining that for Solaris 2.6 (don't see it on the umich web site)?

Thanks!
Sean

--
Sean Snyder (ssnyder@cecom.com)| 
Systems and Network Engineer   |   Every new beginning comes from some
Campbell-Ewald Advertising and |         other beginning's end....
C-E Communications             |		
#include <std_disclaimer.h>    |



This archive was generated by hypermail 2b28 : Sat Dec 18 1999 - 16:33:18 EST