Experimental Physics and
| |||||||||||||||
|
Hi, Adam, On Tue, 7 Dec 2021 at 23:01, Manoussakis, Adamandios <manoussakis1 at llnl.gov> wrote:
Correct. It works on incoming name resolution requests and just patches the header information.
The best and easiest test is the initial problem: If you have multiple IOCs on the host, a CA client from a different machine doing a unicast name resolution request will see one IOC (rule is not active) or all IOCs (rule is active).
That's correct, but the client will also send broadcasts on all network interfaces (except loopback/localhost) unless EPICS_CA_AUTO_ADDR_LIST is set to NO. EPICS_CA_AUTO_ADDR_LIST is the switch for "broadcast on all interfaces". EPICS_CA_ADDR_LIST contains addresses that are used additionally, which may be unicast or broadcast addresses.
Yes, the caget will use unicasts to localhost - in addition to sending broadcasts on all network interfaces (according to EPICS_CA_AUTO_ADDR_LIST setting).
The firewall rule is server-side and only needed on hosts that run multiple servers (IOCs or Gateways). Nowhere else. If your gateway machine is running a single Gateway instance per network interface the Gateway binds to, it does not need to run the firewall rule.
These two things are not directly related as they are happening on two different machines. Your environment settings are for a CA client running on the client host, where the firewall rule does not run. The firewall rule is running on the server (IOC) host and affecting incoming name resolution requests. Also note that the firewall rule trick does not work for CA clients on the same host as the multiple IOCs. Cheers, ~Ralph
| ||||||||||||||
ANJ, 09 Dec 2021 |
·
Home
·
News
·
About
·
Base
·
Modules
·
Extensions
·
Distributions
·
Download
·
· Search · EPICS V4 · IRMIS · Talk · Bugs · Documents · Links · Licensing · |