Path: utzoo!utgpu!watmath!clyde!att!osu-cis!tut.cis.ohio-state.edu!rutgers!deimos!uxc!tank!mimsy!chris From: chris@mimsy.UUCP (Chris Torek) Newsgroups: comp.unix.wizards Subject: Re: 4.3 BSD networking bugs Message-ID: <14759@mimsy.UUCP> Date: 30 Nov 88 13:18:09 GMT References: <204@hsi86.hsi.UUCP> Organization: U of Maryland, Dept. of Computer Science, Coll. Pk., MD 20742 Lines: 21 In article <204@hsi86.hsi.UUCP> stevens@hsi.UUCP (Richard Stevens) writes: >(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() ... Yep. Fixed in 4.4BSD? (4.4 will have variable length socket addresses, which are required by various ISO protocols.) >(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. spp_usrreq calls ns_pcbbind with a null `nam', telling it to choose a local port. ns_pcbbind defers choosing a local host address, however, until send time, just like the TCP code. Alas, ns_output does not contain the `#ifndef notdef' (=~ `if true') code that appears in ip_output.... -- In-Real-Life: Chris Torek, Univ of MD Comp Sci Dept (+1 301 454 7163) Domain: chris@mimsy.umd.edu Path: uunet!mimsy!chris