In my development phase, I noticed that I received many requests on my dynamic IP (from my ISP). After checking what kind of requests were, I wanted to stop them. Many of these requests are bots from giant companies scouring the web. But so many hackers who do not make valid requests but try to break into the server.
## Whitelist
IP addresses from the whitelist are allowed to connect. All other addresses that are not noted will be blocked.
Whitelist
You can switch to the whitelist with a tab. In a list you see all IPs that are whitelisted. In the second column you can see when and how often a query was started from this IP.
{% hint style="info" %}
Only IPs that are whitelisted can make a request. All other IPs are automatically blacklisted.
{% endhint %}
## Blacklist
Blacklist imports
1. **Tab for Blacklist:** There are more tabs under the blacklist.
2. **Tab for Own/Imports:** Here you have two lists. Once the list of self-entered IPs that are blocked. Or the imported list.
3. **Entry of import blacklisting:** Here you can see the information about what is known under the IP and when it last tried to access it. The list is sorted by the last accesses.
{% hint style="info" %}
IP addresses that are in the blacklist will be blocked. What is special about the blacklist is that it is compared with a public blacklist every 24 hours.
{% endhint %}
;)
## Add IP to White-/Black-list
Buttons for add Black/White-Rule.
The dialog for the blacklist and whitelist are identical.
Dialog
1. **IP**: IP to block or allow through.
2. **Disable this ip block**: Disables the rule if the rule should not be deleted.
3. **Description**: A description can be given of what is known about the IP.
---
# Agent Instructions: 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:
```
GET https://flying-fish.gitbook.io/flyingfish/index/configurations/listen/ip-access.md?ask=
```
The question should be specific, self-contained, and written in natural language.
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.