Hi Ralph,
Thanks for the response. I suppose that I'm being a bit thick, but I'm not able
to understand
your instructions. In starting the gateway, I added the flag "-debug 50". I
cannot connect
from my remote machine 333.33.33.33; I've attempted caget with hopes that the
log file
on the gateway machine will show some attempt to connect, but to no avail. If
this is not
what you mean, would you please be more specific?
Thanks,
Pierrick
On 02/20/2013 11:27 AM, Ralph Lange wrote:
On 20.02.2013 18:09, Pierrick Hanlet wrote:
Hi all,
I'm running an epics gateway v2.0.4 on a linux box running SL with kernel
2.6.18 and is part of a LAN;
my EPICS version is 3.14.11. We have established an external connection to
this subnet with a DSL
connection with a public IP address and an ethernet cable from the DSL modem.
I have no name for
this public IP address.
So, my questions are:
1) How do I set up my gateway.access file?
2) On my remote node, how do I define my EPICS_CA_ADDR_LIST?
3) Can I even use an IP address in the access file?
Let's say that my host computer running the gateway is 111.11.11.11, the
public IP address is 222.22.22.22,
and my remote machine on which I want the EPICS data is 333.33.33.33.
I've tried a variety of things and I'm clearly missing something. On my other
uses of the gateway, I don't
have the intermediate hop over the AT&T provided public IP address.
Thanks,
Pierrick
Hi Pierrick,
I would say for the remote client
EPICS_CA_AUTO_ADDR_LIST=NO
EPICS_CA_NAME_SERVERS= 222.22.22.22
On the gateway, I would turn up debugging, connect from the remote client, and
check what it provides as user and host. These will be the values to use in
the Access Security configuration.
Good luck!
~Ralph
--
"Whether you think you can or think you can't, either way, you are correct" --
Henry Ford
_______________________________________________________________
*Pierrick Hanlet*
IIT/Fermilab
+1-630-840-5555 (FNAL)
+1-312-567-5745 (IIT)
+1-630-697-8758/+44-79-48-860-197 (US/UK mobile)