diff options
| author | Rémi Verschelde <rverschelde@gmail.com> | 2024-05-08 10:04:47 +0200 |
|---|---|---|
| committer | Rémi Verschelde <rverschelde@gmail.com> | 2024-05-08 10:12:46 +0200 |
| commit | 7d03b1de0b7a2f7a7972716a40277c7aa231f542 (patch) | |
| tree | b281f3e370dfa5339f7275e407bd9e5682435f2e /modules/enet | |
| parent | 17a81260cb92a321a0d752e369ef911055178c7b (diff) | |
| download | redot-engine-7d03b1de0b7a2f7a7972716a40277c7aa231f542.tar.gz | |
Style: Trim trailing whitespace and ensure newline at EOF
Found by apply the file_format checks again via #91597.
Diffstat (limited to 'modules/enet')
| -rw-r--r-- | modules/enet/doc_classes/ENetConnection.xml | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/modules/enet/doc_classes/ENetConnection.xml b/modules/enet/doc_classes/ENetConnection.xml index 5ca1ec2228..5795dd8976 100644 --- a/modules/enet/doc_classes/ENetConnection.xml +++ b/modules/enet/doc_classes/ENetConnection.xml @@ -151,7 +151,7 @@ <param index="1" name="destination_port" type="int" /> <param index="2" name="packet" type="PackedByteArray" /> <description> - Sends a [param packet] toward a destination from the address and port currently bound by this ENetConnection instance. + Sends a [param packet] toward a destination from the address and port currently bound by this ENetConnection instance. This is useful as it serves to establish entries in NAT routing tables on all devices between this bound instance and the public facing internet, allowing a prospective client's connection packets to be routed backward through the NAT device(s) between the public internet and this host. This requires forward knowledge of a prospective client's address and communication port as seen by the public internet - after any NAT devices have handled their connection request. This information can be obtained by a [url=https://en.wikipedia.org/wiki/STUN]STUN[/url] service, and must be handed off to your host by an entity that is not the prospective client. This will never work for a client behind a Symmetric NAT due to the nature of the Symmetric NAT routing algorithm, as their IP and Port cannot be known beforehand. </description> |