Argonne National Laboratory

Experimental Physics and
Industrial Control System

1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  <20142015  2016  2017  2018  2019  Index 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  <20142015  2016  2017  2018  2019 
<== Date ==> <== Thread ==>

Subject: Re: Binding an IOC to a single network interface
From: Andrew Johnson <anj@aps.anl.gov>
To: "J. Lewis Muir" <jlmuir@imca-cat.org>
Cc: tech-talk@aps.anl.gov
Date: Mon, 6 Oct 2014 16:24:26 -0500
Hi Lewis,

http://bazaar.launchpad.net/~epics-core/epics-base/3.15/revision/12508

This was a reimplementation of Freddie's patch, making use of the
address-list parsing code that was already in Base. If the env var
contains more than one interface IP it will only use the first one and
print a warning message (as Freddie's code did).

The CA repeater is part of the CA client library, it is not related to
either CA server at all. There can only be one CA repeater running on
any system, and since all clients running on the system need to connect
to that single instance irrespective of which interfaces they will be
searching through, it does not need the same kind of configuration variable.

I would warn people *not* to apply your patch, it could break their
control systems in subtle ways that would not be immediately obvious.

- Andrew


On 10/06/2014 03:42 PM, J. Lewis Muir wrote:
> On 1/22/14 8:30 AM, freddie.akeroyd@stfc.ac.uk 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
> 
> Below is an adaptation of the patch for caRepeater to let it play too.
> 
> I'm unclear on whether caRepeater is considered part of CAS.  It
> gets started by the IOC automatically if it's not already running,
> so I considered it part of CAS.  Hence, it uses the same environment
> variable.  But if it's not considered part of CAS, then I guess it
> should get its own environment variable.
> 
> Andrew, I don't think you've committed Freddie's patch to the 3.15 tree,
> so I'm just posting this additional patch in the hope that it could go
> in with Freddie's patch when you get around to it.

Replies:
Re: Binding an IOC to a single network interface J. Lewis Muir
References:
Binding an IOC to a single network interface freddie.akeroyd
Re: Binding an IOC to a single network interface J. Lewis Muir

Navigate by Date:
Prev: Re: Binding an IOC to a single network interface J. Lewis Muir
Next: Re: [EPICS] Support for Staged Installs ? J. Lewis Muir
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  <20142015  2016  2017  2018  2019 
Navigate by Thread:
Prev: Re: Binding an IOC to a single network interface J. Lewis Muir
Next: Re: Binding an IOC to a single network interface J. Lewis Muir
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  <20142015  2016  2017  2018  2019 
ANJ, 17 Dec 2015 Valid HTML 4.01! · Home · News · About · Base · Modules · Extensions · Distributions · Download ·
· Search · EPICS V4 · IRMIS · Talk · Bugs · Documents · Links · Licensing ·