divert and deadlock issues

[Bruce M. Simpson]

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