From owner-freebsd-hackers Sun Jan 12 22:51:42 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id WAA23052 for hackers-outgoing; Sun, 12 Jan 1997 22:51:42 -0800 (PST) Received: from hemi.com (hemi.com [204.132.158.10]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id WAA23046 for ; Sun, 12 Jan 1997 22:51:37 -0800 (PST) Received: (from mbarkah@localhost) by hemi.com (8.8.4/8.7.3) id XAA17894; Sun, 12 Jan 1997 23:50:57 -0700 (MST) From: Ade Barkah Message-Id: <199701130650.XAA17894@hemi.com> Subject: Re: bug in setsockopt()... ? To: eka@werty.wasantara.net.id (Eka Kelana) Date: Sun, 12 Jan 1997 23:50:55 -0700 (MST) Cc: freebsd-hackers@freebsd.org In-Reply-To: <1CA927E5D71@bandung.wasantara.net.id> from Eka Kelana at "Jan 11, 97 10:28:57 am" X-Mailer: ELM [version 2.4ME+ PL22 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Eka Kelana wrote: > I wonder if there is anyone here ever experience a bug in > setsockopt(). I did this when I found the bug: [...code showing getsockopt() before and after a connect() call deleted...] > The two getsockopt() above produced different value of socket buffer > size. ... the second getsockopt() would produce 17280 bytes. ... Eka, I've observed that in FreeBSD, after a connect(), the buffer size is adjusted according to the MTU of the connecting interface inde- pendent of the socket buffer high water mark. Perhaps the intent is to automatically reserve reasonable buffer sizes based on the interface MTU. You can set the buffer sizes after the connect(), but it wont affect the advertised window size. Regards, -Ade ------------------------------------------------------------------- Inet: mbarkah@hemi.com - HEMISPHERE ONLINE - -------------------------------------------------------------------