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
- Replies:
- Re: Binding an IOC to a single network interface Ralph Lange
- References:
- Binding an IOC to a single network interface freddie.akeroyd
- Navigate by Date:
- Prev:
iocLog Vikram Bhagat
- Next:
RE: iocLog michael.abbott
- Index:
1994
1995
1996
1997
1998
1999
2000
2001
2002
2003
2004
2005
2006
2007
2008
2009
2010
2011
2012
2013
<2014>
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
- Navigate by Thread:
- Prev:
Binding an IOC to a single network interface freddie.akeroyd
- Next:
Re: Binding an IOC to a single network interface Ralph Lange
- Index:
1994
1995
1996
1997
1998
1999
2000
2001
2002
2003
2004
2005
2006
2007
2008
2009
2010
2011
2012
2013
<2014>
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
|