When JetPatch application communicates with endpoints in the environment it by default first tries to communicate to the first IP in the list.
You can change this with the following properties (default settings are below)
fileops.ips.order.enabled=false
fileops.ips.order.cidr=192.168.0.0/16,172.16.0.0/12,10.0.0.0/8
fileops.ips.order.use-not-listed=true
fileops.ips.black-list.cidr=
Note: “fileops.ips.order.enabled” must be set to true to enable changes.
- If you set “fileops.ips.order.use-not-listed” to false it will communicate only to those IPs (In this case it’s a real whitelist with priorities).
- If you set “fileops.ips.order.use-not-listed” to true it will communicate first to those IPs and in case of a failure in communicating those IPs (or if they do not exist), they will search for other IPs not listed.
|
Enable IP (fileops.ips.order. |
Prioritization (fileops.ips. |
Allow not listed IP (fileops.ips.order |
Blacklist CIDR (fileops.ips.black-list.cidr) |
Endpoint IPs |
The first IP to communicate |
|---|---|---|---|---|---|
|
False |
N/A |
N/A |
N/A |
Does not matter |
the first in the existing list |
|
True |
30.30.0.0/24, 172.16.0.0/16 |
N/A |
N/A |
30.30.0.114 |
30.30.0.114 |
|
True |
30.30.0.0/24, 172.16.0.0/16 |
False |
N/A |
192.168.0.1 |
no communication |
|
True |
30.30.0.0/24, 172.16.0.0/16 |
True |
N/A |
192.168.0.1 |
192.168.0.1 |
|
True |
Empty |
True/False |
30.30.0.0/24 |
30.30.0.114 |
172.16.0.28 |
|
True |
Empty |
True/False |
30.30.0.0/24 |
30.30.0.114 |
no communication |
|
True |
Empty |
True/False |
Empty |
Not relevant for UC |
the first in the existing list |
Comments
0 comments
Please sign in to leave a comment.