EPICS Home

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  2014  2015  2016  <20172018  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  2014  2015  2016  <20172018  2019  2020  2021  2022  2023  2024 
<== Date ==> <== Thread ==>

Subject: Re: Channel access blocking
From: Mark Rivers <[email protected]>
To: Mark Engbretson <[email protected]>, "'Hidas, Dean'" <[email protected]>, "[email protected]" <[email protected]>
Date: Fri, 1 Dec 2017 14:53:29 +0000
> You could use
> EPICS_CA_ADDR_LIST


That only works for CA clients.  The IOC server will still serve the PVs on all interfaces.

There is another environment variable that applies to CA servers.  This is from the 3-14 Channel Access Reference Manual.

Binding a Server to a Limited Set of Network Interfaces

The parameter EPICS_CAS_INTF_ADDR_LIST allows a ca server to bind itself to, and therefore accept messages only over, a limited set of the local host's network interfaces (each specified by it's IP address). On UNIX systems type "netstat -i" (type "ipconfig" on windows) to see a list of the local host's network interfaces. Specifically, UDP search messages addressed to both the IP addresses in EPICS_CAS_INTF_ADDR_LIST and also to the broadcast addresses of the corresponding LAN interfaces will be accepted by the server. By default, the CA server is accessible from all network interfaces configured into its host. In R3.14 and previous releases the CA server employed by iocCore does not implemet this feature.


Note that in 3.14 this does not work for the IOC server.  I am not sure if it is implemented in 3.15. or 3.16?

Mark


________________________________
From: [email protected] <[email protected]> on behalf of Mark Engbretson <[email protected]>
Sent: Friday, December 1, 2017 8:42 AM
To: 'Hidas, Dean'; [email protected]
Subject: RE: Channel access blocking

You could use

EPICS_CA_ADDR_LIST

And set it to the broadcast address(s) of the interface(s) that you want to
use and set

EPICS_CA_AUTO_ADDR_LIST=NO
So that EPICS will not try to use ever Ethernet adapter that it detects.


-----Original Message-----
From: [email protected] [mailto:[email protected]]
On Behalf Of Hidas, Dean
Sent: Friday, December 1, 2017 7:27 AM
To: [email protected]
Subject: Channel access blocking

Hi,

I'm using EPICS R3.14.12.3-8.  I have a (many) PC with 2 ethernet ports
connected to different networks.  Is there a simple way to completely block
channel access from 1 of them? ie, make all PVs, beacons, etc unavailable to
that interface?

Thanks for your help,

-Dean Hidas=


Replies:
Re: Channel access blocking Williams Jr., Ernest L.
References:
Channel access blocking Hidas, Dean
RE: Channel access blocking Mark Engbretson

Navigate by Date:
Prev: dbGetLink question Mark Rivers
Next: Re: Channel access blocking Williams Jr., Ernest L.
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  <20172018  2019  2020  2021  2022  2023  2024 
Navigate by Thread:
Prev: RE: Channel access blocking Mark Engbretson
Next: Re: Channel access blocking Williams Jr., Ernest L.
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  <20172018  2019  2020  2021  2022  2023  2024