Enhanced feature about IPv6 and NAT support #34
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This was referenced Dec 19, 2019
ggtakec
added a commit
that referenced
this pull request
Oct 10, 2024
Enhanced feature about IPv6 and NAT support
ggtakec
added a commit
that referenced
this pull request
Oct 10, 2024
Enhanced feature about IPv6 and NAT support
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Relevant Issue (if applicable)
n/a
Details
Enhanced the communication part between CHMPX Server / Slave.
(1) Enhanced support for IPv6 addresses
(2) Supports cluster construction via NAT (gateway, bridge, etc.)
(3) Configuration change in accordance with (2) above
The following items were added while maintaining backward compatibility.
CHMPXIDTYPE
This item is specified in the global section and can be omitted.
This is a value that specifies the SEED used to generate the CHMPXID.
For the value, specify NAME (default), CUK, CTLENDPOINTS, or CUSTOM.
For NAME, use the node's HOSTNAME and control port number. This is the same generation method as before.
For CUK, use the value of CUK, and for CTLENDPOINTS, use the value of CTLENDPOINTS.
CUSTOM uses the value of CUSTOM_ID_SEED.
SELFCUK
This item is specified in the global section and can be omitted.
When building a cluster with CUK, specify the value of your own CUK.
Same use as SELFCTLPORT.
CUK
It is an item to be specified in the section of each node and can be omitted.
When specifying CUK, set the value.
ENDPOINTS
It is an item to be specified in the section of each node and can be omitted.
When providing services through NAT, enumerate HOSTANME (IP address) and ports at the NAT entrance to access the ports from the outside.
CTLENDPOINTS
It is an item to be specified in the section of each node and can be omitted.
When providing services through NAT, enumerate HOSTANME (IP address) and ports at the NAT entrance to access the control port from the outside.
FORWARD_PEERS
When passing through NAT or Gateway, list HOSTANME (IP address) of Peer connected to other nodes.
REVERSE_PEERS
When passing through NAT or Gateway, list HOSTANME (IP address) of Peer connected from other nodes.
CUSTOM_ID_SEED
It is an item specified in the section of each node, and the value is an arbitrary character string.
This item must be set to all nodes when CUSTOM is specified for CHMPXIDTYPE.
Otherwise it must not be specified.
(4) Fixed bugs