Argonne National Laboratory

Experimental Physics and
Industrial Control System

2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  <2017 Index 2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  <2017
<== Date ==> <== Thread ==>

Subject: RE: RTEMS: rsrv: failed to set mcast loopback in src/ioc/rsrv/caservertask.c
From: "Williams Jr., Ernest L." <ernesto@slac.stanford.edu>
To: Andrew Johnson <anj@aps.anl.gov>, Michael Davidsaver <mdavidsaver@gmail.com>, Heinz Junkes <junkes@fhi-berlin.mpg.de>, "core-talk@aps.anl.gov" <core-talk@aps.anl.gov>
Cc: "Slepicka, Hugo Henrique" <slepicka@slac.stanford.edu>
Date: Sat, 19 Aug 2017 03:30:39 +0000
Hi Guys,

I am experiencing the same issue with EPICS R3.15.5 and RTEMS version "4.9.4"

Can you add the patch to the KnownProblems page?
http://www.aps.anl.gov/epics/base/R3-15/5-docs/KnownProblems.html


Cheers,

Ernest Williams
Dept. Head, Advanced Control Systems
Advanced Instrumentation Research, Technology Innovation Directorate
SLAC National Laboratory, Stanford University
________________________________________
From: core-talk-bounces@aps.anl.gov [core-talk-bounces@aps.anl.gov] on behalf of Andrew Johnson [anj@aps.anl.gov]
Sent: Thursday, April 20, 2017 9:21 AM
To: Michael Davidsaver; Heinz Junkes; core-talk@aps.anl.gov
Subject: Re: RTEMS: rsrv: failed to set mcast loopback in       src/ioc/rsrv/caservertask.c

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

Replies:
Re: RTEMS: rsrv: failed to set mcast loopback in src/ioc/rsrv/caservertask.c Andrew Johnson
References:
RTEMS: rsrv: failed to set mcast loopback in src/ioc/rsrv/caservertask.c Heinz Junkes
Re: RTEMS: rsrv: failed to set mcast loopback in src/ioc/rsrv/caservertask.c Heinz Junkes
Re: RTEMS: rsrv: failed to set mcast loopback in src/ioc/rsrv/caservertask.c Michael Davidsaver
Re: RTEMS: rsrv: failed to set mcast loopback in src/ioc/rsrv/caservertask.c Andrew Johnson

Navigate by Date:
Prev: RE: epicsStackTrace on WIN32 freddie.akeroyd
Next: Add optimization switch to compiler dependencies Ralph Lange
Index: 2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  <2017
Navigate by Thread:
Prev: Re: RTEMS: rsrv: failed to set mcast loopback in src/ioc/rsrv/caservertask.c Andrew Johnson
Next: Re: RTEMS: rsrv: failed to set mcast loopback in src/ioc/rsrv/caservertask.c Andrew Johnson
Index: 2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  <2017
ANJ, 22 Aug 2017 Valid HTML 4.01! · Home · News · About · Base · Modules · Extensions · Distributions · Download ·
· EPICS V4 · IRMIS · Talk · Bugs · Documents · Links · Licensing ·