Experimental Physics and
Industrial Control System

"Brian McAllister" <[email protected]> · Wed, 26 Jun 2013 20:18:36 -0400

>>> On 6/26/2013 at 17:20:27 CDT, Andrew Johnson wrote:

  > Do you have EPICS_CA_ADDR_LIST and/or EPICS_CA_AUTO_ADDR_LIST set in
  > the environment that's running caget?  If so, what are they set to?

They were not set.  I vaguely recall having to use them for some special
case in the past, but generally have not, including on dual-NIC systems.
In that case, there was no IOC on the host, rather all were on one of the
two networks.

I have now tried

	setenv EPICS_CA_AUTO_ADDR_LIST NO

with either

	setenv EPICS_CA_ADDR_LIST "172.18.0.255"
or
	setenv EPICS_CA_ADDR_LIST "18.229.255.255"

and caget still just times out.  I made sure to kill caRepeater in case its
environment matters.

Also, can you explain what this socket is for ?

epicsdev   10u  IPv4 136864      0t0    UDP asym.mit.edu:33586->172.18.0.255:ca-2

For completeness, ifconfig:

eth0      Link encap:Ethernet  HWaddr 00:0C:F1:A1:C9:44
          inet addr:18.229.0.31  Bcast:18.229.255.255  Mask:255.255.0.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1

eth1      Link encap:Ethernet  HWaddr 00:A0:C9:CC:F2:FC
          inet addr:172.18.0.100  Bcast:172.18.0.255  Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1

-------

BTW, the documentation on these variables is rather lacking.  The
AppDevGuide refers to the CA Ref Manual, which lists them without really
explaining what they do or how to use them in any detail.

There are more detailed descriptions of a few in base/config/CONFIG_ENV but
why would someone look there, as that file is not intended to be modified ?
The descriptions of the EPICS_CA_* variables there are also not much more
enlightening than the manuals.

- brian

Experimental Physics and Industrial Control System

Experimental Physics and
Industrial Control System