Path: utzoo!attcan!uunet!aplcen!uakari.primate.wisc.edu!zaphod.mps.ohio-state.edu!think!snorkelwacker!apple!amdahl!rtech!wrs!hwajin From: hwajin@ganges.wrs.com (Hwa Jin Bae) Newsgroups: comp.protocols.tcp-ip Subject: Re: UDP bind question Message-ID: Date: 7 Feb 90 22:54:35 GMT References: <7391@b11.ingr.com> Sender: news@wrs.wrs.com Organization: Wind River Systems, Emeryville, CA Lines: 19 In-reply-to: heller@b11.ingr.com's message of 7 Feb 90 00:26:50 GMT In article <7391@b11.ingr.com> heller@b11.ingr.com (Anne Heller) writes: I have a question regarding binding to ports in UDP. Is it generally acceptable to allow binding more than once to a given port? (I know about the SO_REUSEADDR option in sockets, but we have a STREAMS implementation which complies with the AT&T Transport Provider Interface (TPI) standard, so not everyone is accessing UDP through sockets.) It doesn't really matter whether you use sockets or TLI interface to access the UDP/IP. The system calls (whether you use bind() or t_bind()) get turned into STREAMS messages as they pass through the STREAM heads with types that TPI multiplexor module understands (in case of bind request it would be T_BIND_REQ type). Upon receiving such messages TPI multiplexor module will call protocol specific bind routine to handle the bind request and return the result of such binding. This sequence of kernel events is identical for both TLI and socket based requests. -- Hwa Jin Bae, Wind River Systems, 1351 Ocean Avenue, Emeryville, CA 94606, USA hwajin@wrs.com (uunet!wrs!hwajin) "Omnibus ex nihil ducendis sufficit unum."