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: | Re: Beacon like connection attempts from caGateway |
From: | Bo Jakobsen <[email protected]> |
To: | Ralph Lange <[email protected]>, EPICS Tech Talk <[email protected]> |
Date: | Mon, 29 Oct 2018 13:52:55 +0100 |
Hello Ralph
Thanks for the input. I did find similar information in a "bug report" on the gateway: https://github.com/epics-extensions/ca-gateway/issues/13 As the network setup is based on vlan's and firewall/router roules I can not use the "on IP number based distinction" to only get beacon signals on the server side. However, I found the following hack : Setting the variables : export EPICS_CAS_AUTO_BEACON_ADDR_LIST=no export EPICS_CAS_BEACON_ADDR_LIST=localhost before starting the cagateway process will stop the beacon signals altogether. Can you see any reason why this is a bad idea? Best Bo On 2018-10-27 22:30, Ralph Lange wrote:
|