From owner-freebsd-current  Tue Nov 25 18:36:08 1997
Return-Path: <owner-freebsd-current>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.7/8.8.7) id SAA04362
          for current-outgoing; Tue, 25 Nov 1997 18:36:08 -0800 (PST)
          (envelope-from owner-freebsd-current)
Received: from word.smith.net.au (vh1.gsoft.com.au [203.38.152.122])
          by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id SAA04283
          for <current@freefall.FreeBSD.org>; Tue, 25 Nov 1997 18:36:01 -0800 (PST)
          (envelope-from mike@word.smith.net.au)
Received: from word (localhost [127.0.0.1])
	by word.smith.net.au (8.8.7/8.8.5) with ESMTP id NAA01935;
	Wed, 26 Nov 1997 13:01:19 +1030 (CST)
Message-Id: <199711260231.NAA01935@word.smith.net.au>
X-Mailer: exmh version 2.0zeta 7/24/97
To: Mike Smith <mike@smith.net.au>
cc: Archie Cobbs <archie@whistle.com>, hasty@rah.star-gate.com (Amancio Hasty),
        current@freefall.FreeBSD.org
Subject: Re: tcp/ip buglet ? 
In-reply-to: Your message of "Wed, 26 Nov 1997 11:11:23 +1030."
             <199711260041.LAA01518@word.smith.net.au> 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Wed, 26 Nov 1997 13:01:19 +1030
From: Mike Smith <mike@smith.net.au>
Sender: owner-freebsd-current@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

> > Not sure what the problem is here. However, I remember a similar
> > situation once a long time ago and the fix was to make sure that
> > the struct sockaddr_in was completely zeroed and the sa_len field
> > was properly set before doing the bind.

Speaking of this problem, I can characterise it some more:

If you are binding to an address that is not INADDR_ANY (ie. not 0), 
*all* of the sin_zero bytes must be zero.

To me, this is kinda silly.  It sounds as though there is some code 
somewhere that is not using the sin_len/sa_len field, although I can't 
find it.

Anyone have any ideas?

mike