Experimental Physics and
Industrial Control System

Andrew Johnson <[email protected]> · Fri, 17 Oct 2014 15:05:36 -0500

Hi Lewis,

On 10/06/2014 05:03 PM, J. Lewis Muir wrote:
>> 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.
> 
> For my use case, I still wish for it.  I have a development machine, and
> I want everything to be listening on the loopback interface--nothing
> else.  I wish for an easy way to do that.  caRepeater listens on all
> interfaces; I just want it to bind to the loopback interface; that's it.

In that particular circumstance I would suggest setting up a firewall to
deny access to ports 5064 and 5065, or that running your tests on a VM
with no external network access would make more sense. You can of course
use your modified version of the CA Repeater on your development machine
without having to get it included in EPICS Base as long as you start it
by hand before any CA client; the standard client library will still
connect to it normally.

I would be wary of adding a variable like this which could very easily
break operational systems in subtle and hard-to-trace ways. Unless there
is support for it from other people in the EPICS community I don't think
your patch or anything equivalent will be viable.

Sorry,

- Andrew
-- 
People everywhere confuse what they read in newspapers with news.
-- A. J. Liebling

Experimental Physics and Industrial Control System

Experimental Physics and
Industrial Control System