EPICS Controls 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  2020  2021  2022  2023  2024  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  2020  2021  2022  2023  2024 
<== Date ==> <== Thread ==>

Subject: Re: Binding an IOC to a single network interface
From: Ralph Lange <[email protected]>
Cc: EPICS Tech-Talk <[email protected]>
Date: Wed, 29 Jan 2014 10:15:55 +0100
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


Replies:
RE: Binding an IOC to a single network interface Hill, Jeff
Re: Binding an IOC to a single network interface Andrew Johnson
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: EDM XY Graph Trace N Field Alan Greer
Next: RE: EPICS driver for CAEN NIM8304 or N1471 tom.cobb
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  2020  2021  2022  2023  2024 
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 Hill, Jeff
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  2020  2021  2022  2023  2024 
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 ·