> For the complete documentation index, see [llms.txt](https://docs.vibeshost.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.vibeshost.com/g/rust/how-to-protect-your-rust-server.md).

# How to protect your Rust server

***

### Opening game-port(s)

There are a few ports (by default) that we will need to whitelist to allow users to connect to your server through our firewall.

Head to the **Firewall Rules** page, and open **UDP Port 28015** this is the default rust game-port and will allow regular game traffic through to your server.

<figure><img src="/files/0NcSHuZOaIntzkILbpEz" alt="" width="375"><figcaption></figcaption></figure>

### BattleMetrics (Optional)

You may need to whitelist RCON solely for BattleMetric IP's as listed below

BattleMetric IP's as of 04/2021

&#x20;   51.79.45.167

&#x20;   142.44.175.123

&#x20;   167.114.219.233

&#x20;   51.222.127.205

&#x20;   51.222.127.206&#x20;

&#x20;   51.222.127.207&#x20;

&#x20;

You can do this by creating a rule similar to the image below (allow rule with strict source ip):

<figure><img src="/files/zMPheVc4XFGfe9A1iFpD" alt="" width="380"><figcaption></figcaption></figure>

### Applying the filters

Once you have verified that your server is responding on port 28015/UDP and the game-server is functional we can go ahead and apply the application specific filter to fine-tune the protection for your server.

Proceed to head over to the **Filters** page on the left hand side of the portal page.

You should be directed to a page that looks similar to below:

<figure><img src="/files/VksZE0DK2M4pSEYq2APo" alt=""><figcaption></figcaption></figure>

<figure><img src="/files/Tfk9cCIxMmNq5xHh4kpg" alt=""><figcaption></figcaption></figure>

Your Rust server is ready to go and is setup to best defend from attacks. If you have any issues or concerns with this setup feel free to reach out to us via the support!


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.vibeshost.com/g/rust/how-to-protect-your-rust-server.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.