onyx_online/q3rcon-proxy
1
0
Fork 0
mirror of https://github.com/onyx-and-iris/q3rcon-proxy.git synced 2025-01-18 00:30:54 +00:00
Code Issues Packages Projects Releases Wiki Activity

Update README.md

Browse Source 
expand readme
This commit is contained in:
Onyx and Iris 2024-01-28 03:34:28 +00:00 committed by GitHub
parent a3219e63c2
commit 561b1ca654
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
1 changed files with 4 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
README.md
View File

@ -12,13 +12,13 @@ for example:
export Q3RCON_PROXY="20000:28960;20001:28961;20002:28962"
```
This would run 3 proxy servers listening on ports `20000`, `20001` and `20002` that redirect rcon requests to game servers on ports `28960`, `28961` and `28962` respectively.
This would configure q3rcon-proxy to run 3 proxy servers listening on ports `20000`, `20001` and `20002` that redirect rcon requests to game servers on ports `28960`, `28961` and `28962` respectively.
Then just run the binary which you can compile yourself, download from `Releases` or use the included Dockerfile.
### Why
Avoid sending plaintext rcon requests (that include the password) to public ports. Instead send them to whitelisted ports.
Gives you the option to disable remote rcon entirely and have the server accept requests only from localhost.
Avoid sending plaintext rcon commands to the public game server port. In general I would advise anyone using rcon remotely to use a secured connection but perhaps you've passed rcon to a clan friend who doesn't know about secured connections. Now you can instruct them to use rcon only through a whitelisted port.
### Special Thanks