Re: RTEMS: rsrv: failed to set mcast loopback in src/ioc/rsrv/caservertask.c

[Andrew Johnson <anj@aps.anl.gov>]

On 04/20/2017 10:19 AM, Michael Davidsaver wrote:
> I see that linux (circa 3.16) will accept either 'int' or 'char' for
> IP_MULTICAST_LOOP.  Also for most other integer flags.
> 
> I find references which suggest that winsock wants BOOL (which I assume
> is 'char').
> 
> However, vxworks 5.5 clearly spec's 'int'.
> 
> http://www.vxdev.com/docs/vx55man/vxworks/ref/sockLib.html

But as long as we're talking about Base-3.16 we don't have to support
VxWorks 5.5 at all. Wind River completely replaced the network stack in
VxWorks 6.x, and the newer stack looks like it will support either int
or char (there's code in setsockopt() for IP_MULTICAST_LOOP which
appears to handle both sizes, although they haven't updated the docs to
actually say that).

> Seems like the IP_MULTI* socket options need unit-test coverage.  (maybe
> add to blockingSocketTest.cpp ?)

Agreed, and that seems like the right place for it.

- Andrew

-- 
Arguing for surveillance because you have nothing to hide is no
different than making the claim, "I don't care about freedom of
speech because I have nothing to say." -- Edward Snowdon