On 24/06/2019, 11:31, Michael McMahon wrote:
Hi Mark
On 23/06/2019, 13:53, mark sheppard wrote:
:
Since the socket is receiving something unexpected, I think I agree
that binding
to the multicast address could be worth doing as well. That would
filter out
packets that perhaps broadcast or just sent directly to the bound
port, independent
of the multicast group. I will try out that suggestion and if it works
okay,
I'll include it in the change.
It seems that trick doesn't work on Solaris or Windows. I don't think
it's worth complicating
the test further with more OS specific code. So, for now, I'm going to
push the change as it is.
Thanks,
Michael.
