Experimental Physics and
Industrial Control System

Andrew Johnson <[email protected]> · Thu, 4 Nov 2010 11:51:37 -0500

On Thursday 04 November 2010 11:25:52 Eric Norum wrote:
> Thanks.  That does it.
> Here's what I now have.
>
> -A RH-Firewall-1-INPUT -s 128.3.128.0/22 -p udp --dport 5064 -j ACCEPT
> -A RH-Firewall-1-INPUT -s 128.3.128.0/22 -p udp --dport 5065 -j ACCEPT
> -A RH-Firewall-1-INPUT -s 128.3.128.0/22 -p tcp --dport 5064 -j ACCEPT
> -A RH-Firewall-1-INPUT -s 128.3.128.0/22 -p tcp --dport 5065 -j ACCEPT
> -A RH-Firewall-1-INPUT -s 128.3.128.0/22 -p udp --sport 5064 -j ACCEPT
>
>
> Maybe this needs to go in either the application developer's guide or the
> release notes.

Since this is a Channel Access issue I think it makes more sense to put it in 
the CA Reference Manual.  Note that the "RH-Firewall-1-INPUT" part is probably 
distribution-specific (I suspect the "RH" stands for Red Hat), and there's 
also a subnet-specific part to those commands.

Are *all* of those lines really necessary though?  It would be nice to have 
something that says "CA clients need ...", "a soft IOC needs ..." etc.

- Andrew
-- 
If a man is offered a fact which goes against his instincts, he will
scrutinize it closely, and unless the evidence is overwhelming, he will
refuse to believe it.  If, on the other hand, he is offered something
which affords a reason for acting in accordance to his instincts, he
will accept it even on the slightest evidence.  -- Bertrand Russell

Experimental Physics and Industrial Control System

Experimental Physics and
Industrial Control System