TRX/GeyserWebsite
1
0 Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Document new network configuration (#257)

Browse Source 
Signed-off-by: Joshua Castle <26531652+Kas-tle@users.noreply.github.com>
This commit is contained in:
Kas-tle authored and GitHub committed 2024-03-31 21:42:40 -07:00
1 parent fe4cf89fa5
commit ed24c94876
2 files changed
+9 -1
Download Patch File Download Diff File Expand all files Collapse all files

No files matched your search

_docs/geyser/geyser-command-line-arguments-and-system-properties.md
+8
View File
@@ -48,6 +48,14 @@ You may disable some warnings that may be printed to the console by using the fo
- `-DGeyser.AddTeamSuggestions=true`
- Allows you to turn off suggestions for teams in the scoreboard command. This is enabled by default, disabling this can help with performance if there are a lot of teams defined.
Setting "command-suggestions" to false in the config will also disable this.
- `-DGeyser.RakPacketLimit=120`
- Sets RakNet's per-ip per-tick (10ms) post-connection packet limit.
- `-DGeyser.RakOfflinePacketLimit=10`
- Sets RakNet's per-ip per-second pre-connection packet limit.
- `-DGeyser.RakGlobalPacketLimit=100000`
- Sets RakNet's per-tick (10ms) overall packet limit.
- `-DGeyser.RakRateLimitingDisabled=true`
- Completely disable RakNet's post-connection rate limiter. This should not be disabled unless initial RakNet connections are being handled by a reverse proxy.
## Geyser-Standalone specific options:
_docs/geyser/understanding-the-config.md
+1 -1
View File
@@ -23,7 +23,7 @@ The options for Geyser on the Bedrock-facing end. Mostly contains options for ho
**`enable-proxy-protocol`**: Whether to enable PROXY protocol or not for clients. You DO NOT WANT this feature unless you run UDP reverse proxy in front of your Geyser instance. You do NOT need this for BungeeCord (and forks), Velocity, or Waterfall.
**`proxy-protocol-whitelisted-ips`**: Disabled by default, and only enable this if you use "enable-proxy-protocol". A list of allowed PROXY protocol speaking proxy IP addresses/subnets. Should really only be used when you are not able to use a proper firewall (usually true with shared hosting providers etc.). Keeping this list empty means there is no IP address whitelist. Both IP addresses and subnets are supported.
**`proxy-protocol-whitelisted-ips`**: Disabled by default, and only enable this if you use "enable-proxy-protocol". A list of allowed PROXY protocol speaking proxy IP addresses/subnets. Should really only be used when you are not able to use a proper firewall (usually true with shared hosting providers etc.). Keeping this list empty means there is no IP address whitelist. IP addresses, subnets, and links to plain text files containing either are supported.
## Remote Section
Options for the remote (Java) server.