Path: utzoo!utgpu!watmath!clyde!att!osu-cis!tut.cis.ohio-state.edu!rutgers!ucsd!sdcsvax!ucsdhub!esosun!seismo!uunet!hsi!stevens
From: stevens@hsi.UUCP (Richard Stevens)
Newsgroups: comp.unix.wizards
Subject: 4.3 BSD networking bugs
Message-ID: <204@hsi86.hsi.UUCP>
Date: 27 Nov 88 19:14:46 GMT
Organization: Health Systems Intl., New Haven, CT
Lines: 25

I've encountered two "problems" with the 4.3 BSD networking code
that I'm wondering if anyone has previously found and fixed.
I've checked the vanilla 4.3 sources against the updated UCB
networking code that was posted in April 88, and didn't see any
changes that might affect these problems.

(1) When using UNIX domain datagrams, only the first 14 bytes of
	the sender's socket address are passed with the datagram.
	It looks like sbappendaddr() in sys/uipc_socket2.c is doing
	this, as it assumes everything fits into a "struct sockaddr".
	The socket with the longer-than-14-byte path name is created
	just fine, but it's entire name isn't sent along with the datagram.

(2) When using XNS datagrams (IDP protocol) you have to explicitly
	call bind() to assign an address to yourself, if you want
	the other end to be able to respond to you, otherwise an all
	zero address gets sent along with the datagram.  This problem
	doesn't happen with UDP datagrams.  In looking at netns/ns_pcb.c
	it looks like a local address should be automatically assigned,
	but this isn't happening.

		Richard Stevens
		Health Systems International, New Haven, CT
		   stevens@hsi.uu.net
       		   ... { uunet | yale } ! hsi ! stevens