Date: Tue, 31 Jul 2007 23:25:13 +0100 From: "Bruce M. Simpson" <bms@incunabulum.net> To: "Christian S.J. Peron" <csjp@FreeBSD.org> Cc: freebsd-net@freebsd.org, rwatson@freebsd.org Subject: Re: divert and deadlock issues Message-ID: <46AFB6C9.20401@incunabulum.net> In-Reply-To: <20070731204156.GA7614@sub> References: <20070731162515.GA3684@sub> <46AF7E57.5020209@incunabulum.net> <20070731204156.GA7614@sub>
next in thread | previous in thread | raw e-mail | index | archive | help
Christian S.J. Peron wrote: >> I can't think of a reason why a user would wish to supply any multicast >> socket options to a divert socket, other than the 'small' ones, i.e. >> IP_MULTICAST_TTL/IF/LOOP/VIF. >> > > Why would these options ever be set on the divert socket itself though? > To me it would make sense if these options were set on the network > socket that originally sent the multicast packet itself. > They shouldn't be necessary, however I can foresee situations where someone might well want to redirect multicast datagrams traversing an IPPROTO_DIVERT socket, by using these socket options. [Recall that FreeBSD's IPv4 stack currently uses the destination address as the sole primary key for lookups in the forwarding information base's radix trie.] This is however very unlikely, so my last suggestion, that multicast options be deprecated or forbidden for IPPROTO_DIVERT sockets, stands. Kind regards BMS
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?46AFB6C9.20401>