Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Path: utzoo!mnetor!uunet!seismo!ll-xn!ames!sdcsvax!sdcc6!bparent From: bparent@sdcc6.ucsd.EDU (Brian Parent) Newsgroups: comp.unix.wizards Subject: Re: sun-3 client from sun-2 server, followup Message-ID: <3256@sdcc6.ucsd.EDU> Date: Wed, 15-Jul-87 17:39:22 EDT Article-I.D.: sdcc6.3256 Posted: Wed Jul 15 17:39:22 1987 Date-Received: Sat, 18-Jul-87 01:33:46 EDT References: <3255@sdcc6.ucsd.EDU> <13315@topaz.rutgers.edu> Reply-To: bparent@sdcc6.ucsd.edu.UUCP (Brian Parent) Organization: University of California, San Diego Lines: 13 Keywords: sun nd client server In article <13315@topaz.rutgers.edu> hedrick@topaz.rutgers.edu (Charles Hedrick) writes: >I thought that in current releases of Sun OS, the max packet size is >set in /etc/nd.local. It's an extra argument that can go at the end >of the line. Clearly it's better to do it just for the one host that >needs it. I didn't think you needed to patch the kernel. Am I wrong? Yes, the max packet size can be set for the *server's* kernel using /etc/nd.local. However, this is not enough to keep the faster sun-3 client from drowning the sun-2's 3comm controller. (It doesn't work like hardware flow control as I also assumed at the start of my problem.) You definitely need to patch the *client's* kernel so that it doesn't send too many packets too quickly.