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  2014  2015  2016  2017  <20182019  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  <20182019 
<== Date ==> <== Thread ==>

Subject: Re: Beacon like connection attempts from caGateway
From: Bo Jakobsen <lister@f77.dk>
To: Ralph Lange <ralph.lange@gmx.de>, EPICS Tech Talk <tech-talk@aps.anl.gov>
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:
Hello Bo,

You are right: port 5065/udp traffic are CA beacon messages, which are sent every 15 seconds (unless configured otherwise).

What is the server IP address (-sip <addr>) of your Gateway? If you don't configure a CA server to bind to an explicit IP, it will bind to all available network interfaces, including the one that the Gateway uses to connect to its clients (the machine called "cagw" in your case). Obviously, the CA server will also send beacons on all interfaces it binds to.
I.e., not setting the server IP of a Gateway would explain the behavior you are seeing.

Cheers,
~Ralph



References:
Beacon like connection attempts from caGateway Bo Jakobsen
Re: Beacon like connection attempts from caGateway Ralph Lange

Navigate by Date:
Prev: Re: Status of caml&webCA Kasemir, Kay via Tech-talk
Next: Re: Status of caml&webCA Gibbs, Matt via Tech-talk
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  <20182019 
Navigate by Thread:
Prev: Re: Beacon like connection attempts from caGateway Ralph Lange
Next: segmentation error pvdata -> libc Heinz Junkes
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  <20182019 
ANJ, 29 Oct 2018 Valid HTML 4.01! · Home · News · About · Base · Modules · Extensions · Distributions · Download ·
· Search · EPICS V4 · IRMIS · Talk · Bugs · Documents · Links · Licensing ·