From owner-freebsd-net Tue Nov 10 17:11:58 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA16844 for freebsd-net-outgoing; Tue, 10 Nov 1998 17:11:58 -0800 (PST) (envelope-from owner-freebsd-net@FreeBSD.ORG) Received: from khavrinen.lcs.mit.edu (khavrinen.lcs.mit.edu [18.24.4.193]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA16837 for ; Tue, 10 Nov 1998 17:11:54 -0800 (PST) (envelope-from wollman@khavrinen.lcs.mit.edu) Received: (from wollman@localhost) by khavrinen.lcs.mit.edu (8.9.1/8.9.1) id UAA22828; Tue, 10 Nov 1998 20:11:20 -0500 (EST) (envelope-from wollman) Date: Tue, 10 Nov 1998 20:11:20 -0500 (EST) From: Garrett Wollman Message-Id: <199811110111.UAA22828@khavrinen.lcs.mit.edu> To: Stefan Bethke Cc: a sun , freebsd-net@FreeBSD.ORG Subject: Re: multicast handling in FreeBSD In-Reply-To: References: <199811102210.OAA11742@saul9.u.washington.edu> Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org < quoted some unnamed individual who said: >> i was wondering why you folks decided to change multicast handling in >> the current FreeBSD. Because the Old Way was never properly integrated with the ability in 4.4 to specify multiple network addresses on a single network interface -- this caused problems when (unicast) addresses were added and removed. >> least, argues that you keep the old interface around. from the >> application level, the new interface looks slightly more complicated >> and somewhat arbitrary. >From the application level there is absolutely no difference -- other than the requirement to actually construct a valid sockaddr. -GAWollman -- Garrett A. Wollman | O Siem / We are all family / O Siem / We're all the same wollman@lcs.mit.edu | O Siem / The fires of freedom Opinions not those of| Dance in the burning flame MIT, LCS, CRS, or NSA| - Susan Aglukark and Chad Irschick To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message