Date: Wed, 01 Aug 2007 15:34:32 +0100 From: "Bruce M. Simpson" <bms@incunabulum.net> To: "Christian S.J. Peron" <csjp@FreeBSD.org> Cc: freebsd-net@freebsd.org, rwatson@freebsd.org, Julian Elischer <julian@elischer.org> Subject: Re: divert and deadlock issues Message-ID: <46B099F8.5040301@incunabulum.net> In-Reply-To: <20070801001908.GA8822@sub> References: <20070731162515.GA3684@sub> <46AF7E57.5020209@incunabulum.net> <20070731204156.GA7614@sub> <46AFB6C9.20401@incunabulum.net> <46AFC441.2070502@elischer.org> <20070801001908.GA8822@sub>
next in thread | previous in thread | raw e-mail | index | archive | help
Christian S.J. Peron wrote: > Well, it's still the intent to keep the ability to divert and re-inject > multicast packets. This change would basically say: "You cant specify > multicast options via the divert socket". Which in practice doesn't > happen anyway (where I looked). > > I dont think we should be specifying multicast options on divert sockets. > It's not the right place to be manipulating multicast parameters. Multicast > parameters should be set on the sockets that originally transmitted or > received the packets. I dont think divert falls into this category. > Correct. The definition of what a divert socket is and does, falls outside the definition of what a multicast socket endpoint is. Divert sockets exist to munge packets as they flow up or down the stack. If the additional complexity of treating divert sockets as multicast endpoints causes locking issues in the stack, common sense suggests we should deprecate that behaviour. BMS
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?46B099F8.5040301>