Experimental Physics and
Industrial Control System

"Hill, Jeff" <[email protected]> · Thu, 30 Jan 2014 02:24:47 +0000

I also haven't seen the patch so I can't comment.

For some years now, I have implemented this feature in the portable-server-library (i.e. cas), and also in a 3rd generation CA server library which has also been integrated into the IOC, and has many additional new features, but unfortunately these changes have not been merged into any EPICS production release at this time.

Jeff

> -----Original Message-----
> From: [email protected] [mailto:tech-talk-
> [email protected]] On Behalf Of Ralph Lange
> Sent: Wednesday, January 29, 2014 2:16 AM
> Cc: EPICS Tech-Talk
> Subject: Re: Binding an IOC to a single network interface
> 
> On 28.01.2014 23:28, J. Lewis Muir wrote:
> > On 1/22/14, 8:30 AM, [email protected] wrote:
> >> Hi,
> >>
> >> we are looking to run a set of IOCs that bind channel access to just
> >> the loopback interface on the computer; however I saw from the 3.14
> >> docs that EPICS_CAS_INTF_ADDR_LIST is not currently implemented in the
> >> iocCore CA Server. I had a look at the code in base/src/rsrv and the
> >> attached diff (against 3.14.12.2) seems to work for us with:
> >>
> >> EPICS_CAS_INTF_ADDR_LIST=127.0.0.1
> >> EPICS_CAS_BEACON_ADDR_LIST=127.255.255.255
> >>
> >> I was just wondering if these additions are sufficient, or have I
> >> missed something elsewhere that either needs changing too or might
> >> cause issues later on?
> >>
> >> Thanks,
> >>
> >> Freddie
> > Hi, Andrew.
> >
> > Have you had a chance to consider the patch sent by Freddie?  You seem
> > open to reviewing and accepting such a patch in the following Tech-Talk
> > post:
> >
> >    http://www.aps.anl.gov/epics/tech-talk/2013/msg01493.php
> >
> > I haven't looked at the patch, but the ability to specify the addresses
> > on which the IOC CA server listens has been a feature I've wished for
> > for a long time.
> >
> > Thanks!
> >
> > Lewis
> 
> My 2cts...
> 
> At first glance, this patch looks fine and should cover almost all use
> cases. That feature has been on the wish list for a long time, I know.
> However, I would prefer a slightly more elaborate implementation that
> makes the server side environment variables work the same on both CAS
> and rsrv. (This will also minimize the necessary changes in the
> documentation.)
> 
> But, again, I would say for nearly all real-world use cases applying
> this patch will do.
> 
> Cheers,
> ~Ralph

Experimental Physics and Industrial Control System

Experimental Physics and
Industrial Control System