From owner-freebsd-current Mon Aug 7 12:36:51 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.11/8.6.6) id MAA27236 for current-outgoing; Mon, 7 Aug 1995 12:36:51 -0700 Received: from halloran-eldar.lcs.mit.edu (halloran-eldar.lcs.mit.edu [18.26.0.159]) by freefall.cdrom.com (8.6.11/8.6.6) with SMTP id MAA27229 for ; Mon, 7 Aug 1995 12:36:50 -0700 Received: by halloran-eldar.lcs.mit.edu; (5.65/1.1.3.6) id AA01253; Mon, 7 Aug 1995 15:36:33 -0400 Date: Mon, 7 Aug 1995 15:36:33 -0400 From: Garrett Wollman Message-Id: <9508071936.AA01253@halloran-eldar.lcs.mit.edu> To: terry@cs.weber.edu (Terry Lambert) Cc: current@FREEBSD.org Subject: Re: workaround for talk's address problem In-Reply-To: <9508071918.AA26511@cs.weber.edu> References: <199508071909.MAA09580@puffin.pelican.com> <9508071918.AA26511@cs.weber.edu> Sender: current-owner@FREEBSD.org Precedence: bulk < I can think of one simple and obvious fix, but it fails with SO_REUSEADDR > and/or SO_REUSEPORT. > On a reused port, are incoming packets treated as multicast (that is > routed to each of the listeners)? When SO_REUSEADDR or SO_REUSEPORT is in effect (or even when not, for that matter), packets are routed to the socket whose binding most specifically matches the socket. Multiple identical active bindings are only permitted for broadcast and multicast local addresses. -GAWollman -- Garrett A. Wollman | Shashish is simple, it's discreet, it's brief. ... wollman@lcs.mit.edu | Shashish is the bonding of hearts in spite of distance. Opinions not those of| It is a bond more powerful than absence. We like people MIT, LCS, ANA, or NSA| who like Shashish. - Claude McKenzie + Florent Vollant