I am setting up a cagateway system to allow for PV access to our
lab net from the general "office net".
The gateway process is run as:
cagateway -cip cagw -cport 5066 -sport 5064 -log
epica_gateway.log -archive -no_cache -server -ro
Connecting to the host cagw on port 5066 providing access to the
PV's seen there
(this is also a cagateway instance running with -sport 5066)
This all works nicely, and as I understand it is ok to live
without access to the beacon signals on the outer office net.
However, my problem is that the network people does not like that
cagateway process tries to connect back to the cagw host on port
I do not understand this behaviour.
* It is a very regular pattern with connection attempts every 15
* I do not understand why the cagateway process "client side"
would try to make direct connections to the 5065 port
on the "server".
Can anyone explain?