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 | 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 |
<== Date ==> | <== Thread ==> |
---|
Subject: | PVAccess equivalent to EPICS_CAS_INTF_ADDR_LIST environment variable question |
From: | "Wlodek, Jakub via Tech-talk" <tech-talk at aps.anl.gov> |
To: | "tech-talk at aps.anl.gov" <tech-talk at aps.anl.gov> |
Cc: | "Hanwell, Marcus" <mhanwell at bnl.gov> |
Date: | Wed, 19 May 2021 19:50:18 +0000 |
Hello all,
We have an interesting issue with some of our IOCs, specifically ones that are running a PVA server. We have a Cybersecurity network scanner that scans all open ports on our main network, but it does not affect the EPICS network. We use the EPICS environment
variable EPICS_CAS_INTF_ADDR_LIST to ensure Channel Access only binds to the network interface that has been configured on the EPICS network. For our camera IOCs, where we use PVA for our image displays, we are still seeing the scanner showing up in our IOC
logs, dumping unrelated data to the opened ports (IP address removed):
2021-05-18T05:33:19.976 Invalid header received from the client : SCANNER_IP:40692 00000016 disconnecting...
2021-05-18T05:33:25.980 Invalid header received from the client : SCANNER_IP:42908 49000000 disconnecting...
2021-05-18T05:33:32.010 Invalid header received from the client : SCANNER_IP:49886 47455420 disconnecting...
2021-05-18T05:33:38.010 Error fetching socket remote address: Transport endpoint is not connected.
<unknown>:0: Unable to set RX timeout: 9
These messages are repeated several times. Our guess is this is because of PVA not locked to binding to the EPICS network interface. Is there an equivalent environment variable for PVA that will have it only bind to the specified interface?
Thanks,
Jakub Wlodek
|