> For the complete documentation index, see [llms.txt](https://guides.engels.zip/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://guides.engels.zip/pterodactyl-setup/03-setup-of-the-panel/03d-ip-and-port-allocation.md).

# 03d) IP and Port allocation

The IP and Port allocation is where you specify which Public IPv4 addresses the game servers should connect to and which ports they can use. You may also be able to use hostnames or local IP addresses, but I haven't tested that.

### IP and Port allocation

1. You're now in the Allocation menu after selecting the Create Node (<img src="https://i.imgur.com/WfdMcBv.png" alt="" data-size="line">) option in the previous step.
2. Another box with the title **Assign New Allocations** can be found to the right.
3. Enter your public IPv4 address in the IP Address field. It is in my case `89.33.85.247`.
4. If you want, you can enter an **IP Alias**. This is mostly useful if you have multiple IPv4s connected to your system/network and need to tell them apart. I'm going to leave mine blank, since I don't really care.
5. You should select a range of ports that are not currently in use for the **Ports** option. I usually use ports in the `35000` range. You can always add more and remove the allocated ports later if you want.
6. For now, I'll stick with `35001-35020`. This will give me 19 ports that I can use for game servers.

<figure><img src="https://i.imgur.com/QxRQIxg.gif" alt=""><figcaption></figcaption></figure>

7. Select the **Submit** button: <img src="https://i.imgur.com/2zVZiU7.png" alt="" data-size="line">
8. It'll give you a list of the IPv4 + the ports alllocated. Now we can continue!

### On to the next step!


---

# 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://guides.engels.zip/pterodactyl-setup/03-setup-of-the-panel/03d-ip-and-port-allocation.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.
