Re: Channel Access not connecting

[Bruce Hill <bhill@slac.stanford.edu>]

On 05/17/2011 08:47 AM, Jeff Hill wrote:

oops, yes I said that backwards, its typically broadcasts that are received
by all servers (on the same host), and unicasts that are received by only by
one of multiple servers (on the same host).
  

I'm running with defaults for the EPICS_CA* and EPICS_CAS* env
variables, but have also played with EPICS_CA_ADDR_LIST,
EPICS_CA_AUTO_ADDR_LIST, and EPICS_CA_INTF_ADDR_LIST with no success.
    

The IOC's server is not yet impacted by the EPICS_CA_INTF_ADDR_LIST
configuration.
  

How about the caget client?

I've been having trouble with one linux machine where my IOC's
appear to be running correctly, dbgf works from iocsh, but caget
from another window on the same machine fails to connect.
    

Sounds like a routing level issue. The output from "netstat -r" might be
interesting.

Jeff

Here's netstat -nr output:
Kernel IP routing table
Destination     Gateway         Genmask         Flags   MSS Window  irtt Iface
192.168.254.0   0.0.0.0         255.255.255.0   U         0 0          0 eth2
134.79.32.0     0.0.0.0         255.255.252.0   U         0 0          0 eth0
169.254.0.0     0.0.0.0         255.255.0.0     U         0 0          0 eth2
0.0.0.0         134.79.35.1     0.0.0.0         UG        0 0          0 eth0

Mark suggested a firewall issue.   I'm looking into that now.   This
isn't our normal deployment system.   It's for an experimental chamber that's
currently in a different building at SLAC that wanted to run the same EPICS
motor control as they do when their chamber is installed in the hutch.   That
machine is visible from the internet, and I don't administer it, so I'll need
to find the sysadmin for this machine before making any changes.

This system, kernel 2.6.26.3-29.fc9.x86_64, does have a package called system-config-firewall
installed that says the firewall is enabled.   iptables shows:
# /sbin/iptables -L
Chain INPUT (policy ACCEPT)
target     prot opt source               destination        
ACCEPT     all  --  anywhere             anywhere            state RELATED,ESTABLISHED
ACCEPT     icmp --  anywhere             anywhere           
ACCEPT     all  --  anywhere             anywhere           
ACCEPT     tcp  --  anywhere             anywhere            state NEW tcp dpt:ssh
ACCEPT     tcp  --  anywhere             anywhere            state NEW tcp dpt:mysql
REJECT     all  --  anywhere             anywhere            reject-with icmp-host-prohibited

Chain FORWARD (policy ACCEPT)
target     prot opt source               destination        
REJECT     all  --  anywhere             anywhere            reject-with icmp-host-prohibited

Chain OUTPUT (policy ACCEPT)
target     prot opt source               destination        


Thanks,
- Bruce