ARCHIVE/xrpl-dev-portal
1
0
Fork 0
mirror of https://github.com/XRPLF/xrpl-dev-portal.git synced 2025-11-22 20:55:50 +00:00
Code Issues Packages Projects Releases Wiki Activity

Default port updates for v1.6.0

Browse Source
This commit is contained in:
mDuo13
2020-06-29 17:09:25 -07:00
parent 7a45ac940e
commit 96185b584e
6 changed files with 12 additions and 8 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
content/concepts/the-rippled-server/peer-protocol.md
View File

@@ -28,13 +28,13 @@ To participate in the XRP Ledger, `rippled` servers connect to arbitrary peers u
Ideally, the server should be able to send _and_ receive connections on the peer port. You should [forward the port used for the peer protocol through your firewall](forward-ports-for-peering.html) to the `rippled` server. Ideally, the server should be able to send _and_ receive connections on the peer port. You should [forward the port used for the peer protocol through your firewall](forward-ports-for-peering.html) to the `rippled` server.
The [default `rippled` config file](https://github.com/ripple/rippled/blob/master/cfg/rippled-example.cfg) listens for incoming peer protocol connections on port 51235 on all network interfaces. You can change the port used by editing the appropriate stanza in your `rippled.cfg` file. IANA [has assigned port **2459**](https://www.iana.org/assignments/service-names-port-numbers/service-names-port-numbers.xhtml?search=2459) for the XRP Ledger peer protocol, but for compatibility with legacy systems, the [default `rippled` config file](https://github.com/ripple/rippled/blob/master/cfg/rippled-example.cfg) listens for incoming peer protocol connections on **port 51235** on all network interfaces. If you run a server, you can configure which port(s) your server listens on using the `rippled.cfg` file.
Example: Example:
``` ```
[port_peer] [port_peer]
port = 51235 port = 2459
ip = 0.0.0.0 ip = 0.0.0.0
protocol = peer protocol = peer
``` ```

2
content/references/rippled-api/admin-rippled-methods/peer-management-methods/connect.ja.md
View File

@@ -49,7 +49,7 @@ rippled connect 192.170.145.88 51235
| `Field` | 型 | 説明 | | `Field` | 型 | 説明 |
|:--------|:-------|:----------------------------------------------------------| |:--------|:-------|:----------------------------------------------------------|
| `ip` | 文字列 | 接続するサーバーのIPアドレス。 | | `ip` | 文字列 | 接続するサーバーのIPアドレス。 |
| `port` | 数値 | _（省略可）_ 接続時に使用するポート番号。デフォルトでは6561です。 | | `port` | 数値 | _（省略可）_ 接続時に使用するポート番号。デフォルトでは**2459**です。 [新規: rippled 1.6.0][] |
### 応答フォーマット ### 応答フォーマット

2
content/references/rippled-api/admin-rippled-methods/peer-management-methods/connect.md
View File

@@ -49,7 +49,7 @@ The request includes the following parameters:
| `Field` | Type | Description | | `Field` | Type | Description |
|:--------|:-------|:----------------------------------------------------------| |:--------|:-------|:----------------------------------------------------------|
| `ip` | String | IP address of the server to connect to | | `ip` | String | IP address of the server to connect to |
| `port` | Number | _(Optional)_ Port number to use when connecting. Defaults to 6561. | | `port` | Number | _(Optional)_ Port number to use when connecting. The default is **2459**. [Updated in: rippled 1.6.0][] |
### Response Format ### Response Format

2
content/tutorials/manage-the-rippled-server/configure-peering/cluster-rippled-servers.md
View File

@@ -33,6 +33,8 @@ If you run multiple [`rippled` servers](the-rippled-server.html) in the same dat
This defines specific peer servers to which this server should always attempt to maintain a direct peer-to-peer connection. This defines specific peer servers to which this server should always attempt to maintain a direct peer-to-peer connection.
**Note:** If you omit the port number, the server uses port 2459, the IANA-assigned port for the XRP Ledger protocol. [New in: rippled 1.6.0][]
2. In the `[node_seed]` section, set the server's node seed to one of the `validation_seed` values you generated using the [validation_create method][] in step 2. Each server must use a unique node seed. For example: 2. In the `[node_seed]` section, set the server's node seed to one of the `validation_seed` values you generated using the [validation_create method][] in step 2. Each server must use a unique node seed. For example:
[node_seed] [node_seed]

2
content/tutorials/manage-the-rippled-server/configure-peering/configure-a-private-server.md
View File

@@ -44,6 +44,8 @@ To set up a specific server as a private peer, complete the following steps:
192.168.0.1 51235 192.168.0.1 51235
192.168.0.2 51235 192.168.0.2 51235
**Note:** If you omit the port number, the server uses port 2459, the IANA-assigned port for the XRP Ledger protocol. [New in: rippled 1.6.0][]
4. If using proxies, cluster them with your private peer and each other. 4. If using proxies, cluster them with your private peer and each other.
If you are using public hubs, skip this step. If you are using public hubs, skip this step.

2
content/tutorials/manage-the-rippled-server/configure-peering/manually-connect-to-a-specific-peer.md
View File

@@ -8,7 +8,7 @@ Use these steps to manually connect your server to a specific [peer](peer-protoc
## Prerequisites ## Prerequisites
- You must know the IP address of the peer you want to connect to. - You must know the IP address of the peer you want to connect to.
- You must know what port the peer you want to connect to uses for the XRP Ledger [peer protocol](peer-protocol.html). By default, this is port 51235. - You must know what port the peer you want to connect to uses for the XRP Ledger [peer protocol](peer-protocol.html). The default config file uses port 51235.
- You must have a network connection from your server to the peer. For example, the peer server must [forward the apppropriate port through its firewall](forward-ports-for-peering.html). - You must have a network connection from your server to the peer. For example, the peer server must [forward the apppropriate port through its firewall](forward-ports-for-peering.html).
- The peer server must have available peer slots. If the peer is already at its maximum number of peers, you can ask the peer server's operator to add a [peer reservation](use-a-peer-reservation.html) for your server. - The peer server must have available peer slots. If the peer is already at its maximum number of peers, you can ask the peer server's operator to add a [peer reservation](use-a-peer-reservation.html) for your server.