Experimental Physics and
| |||||||||||||||||
|
There is an environment variable (affecting the server side of the Gateway) to mask out single IP addresses so that the Gateway will just ignore name resolution requests from those addresses. That is normally used to prevent loops in a multi-Gateway environment by making Gateways ignore requests from other Gateways. For the client-side configuration it's either complete subnets or single IP numbers, correct. I'm not sure if this will work on a single NIC machine, though. You might be running into a situation, where the Gateway (on its server side) while being perfectly configured for a -sip in network A still sees name resolution requests coming form network B since it uses the same NIC. For that case I'm not sure what has to be configured in which way. For Chris' original description - wasn't the Gateway sitting on a third, separate network anyway? So that clients that want to see the Gateway have to add its IP explicitly to their EPICS_CA_ADDR_LIST anyway? In that case I don't see that there should be a problem for clients on the IOC side network (e.g. the IOCs themselves), as they also would have to explicitly add the Gateway IP to EPICS_CA_ADDR_LIST to have their name resolution requests directed to it. Broadcast requests from clients (empty EPICS_CA_ADDR_LIST) will usually stay within the network. (Only advanced switch/router configuration can change this.) Cheers, Ralph Dayle Kotturi wrote: Hi Chris,
| ||||||||||||||||
ANJ, 02 Sep 2010 |
·
Home
·
News
·
About
·
Base
·
Modules
·
Extensions
·
Distributions
·
Download
·
· Search · EPICS V4 · IRMIS · Talk · Bugs · Documents · Links · Licensing · |