Thanks for the input.
I did find similar information in a "bug report" on the gateway:
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 :
before starting the cagateway process will stop the beacon signals
Can you see any reason why this is a bad idea?
On 2018-10-27 22:30, Ralph Lange wrote:
You are right: port 5065/udp traffic are CA beacon
messages, which are sent every 15 seconds (unless configured
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
I.e., not setting the server IP of a Gateway would explain
the behavior you are seeing.