Filter
Top Products
Chapter 2. Implementation planning 71
Table 2-6 RC ports for bidirectional communication with Relay
Comments:
1. This port could be fixed in the rc_def_ports RC Policy
2. This default port could be changed using the proxy_port parameter in the
[rcproxy] section of the Parent rcproxy.cfg file, in this case the RC Target
Proxy configuration file. This port must be the same as defined in the
rc_def_proxy RC Policy.
3. This port or port range could be fixed by configuring the local-port-range
parameter in the [children-cm-info] section of the Parent rcproxy.cfg file,
in this case the RC Target Proxy configuration file.
Source Destination Protocol Description
Type
(Service)
Port
(Single /
Range)
Type
(Service)
Port
(Single /
Range)
Controller
(eqnrsmai)
random or
defined
1
(single)
Target Proxy
(rcproxy)
9494
2
(single)
TCP Started at request.
Communication in the
same network zone.
No firewall rule needed.
Target Proxy
(rcproxy)
random or
defined
3
(single or
range)
Relay
(Relay)
defined
4
(single)
TCP Started at service time.
Communication between
two network zones.
Firewall rule needed.
Relay
(Relay)
random or
defined
5
(single or
range)
Target Proxy
(rcproxy)
defined
6
(single)
TCP Started at service time.
Communication between
two network zones.
Firewall rule needed.
Relay
(Relay)
random or
defined
7
(single or
range)
Controller
Proxy
(rcproxy)
defined
8
(single)
TCP Started at service time.
Communication between
two network zones.
Firewall rule needed.
Controller
Proxy
(rcproxy)
random or
defined
9
(single or
range)
Relay
(Relay)
defined
10
(single)
TCP Started at service time.
Communication between
two network zones.
Firewall rule needed.
Controller
Proxy
(rcproxy)
random
(single)
Target
(eqnrcmai)
2501
11
(single)
TCP Started at request.
Communication in the
same network zone.
No firewall rule needed.