AdguardTeam / AdguardTeam/AdGuardHome

Rate limiting allow list regression

Aperta
#8,349 2 commenti 1 reazione 1 assegnatario Rivendicata da @EugeneOne1 Vedi su GitHub
bug
Lingua principale
TypeScript
Stelle
36.9k
Fork
2.5k
Metriche di merge delle PR
Nessuna PR unita negli ultimi 30g

Descrizione

### Prerequisites

- [x] I have checked the [Wiki](https://github.com/AdguardTeam/AdGuardHome/wiki) and [Discussions](https://github.com/AdguardTeam/AdGuardHome/discussions/categories/q-a) and found no answer

- [x] I have searched other issues and found no duplicates

- [x] I want to report a bug and not [ask a question or ask for help](https://github.com/AdguardTeam/AdGuardHome/discussions/categories/q-a)

- [x] I have set up AdGuard Home correctly and [configured clients to use it](https://github.com/AdguardTeam/AdGuardHome/wiki/Clients). (Use the [Discussions](https://github.com/AdguardTeam/AdGuardHome/discussions/categories/q-a) for help with installing and configuring clients.)

### Platform (OS and CPU architecture)

FreeBSD, AMD64 (aka x86_64)

### Installation

Custom package (OpenWrt, HomeAssistant, etc; please mention in the description)

### Setup

On a router, DHCP is handled by the router

### AdGuard Home version

v0.107.74

### Action

```sh
for c in {0..31}; do dig example.com +short && echo; done
```

### Expected result

I expected to see 32 successfully resolved sets of IP addresses:

```
123.123.123.123
231.231.231.231
```
repeated 32 times.

### Actual result

I only see 20 sets of IP addresses (my rate limit is set to 20):
```
123.123.123.123
231.231.231.231
```
repeated 20 times.

### Additional information and/or screenshots

I have AdGuardHome installed on an OPNSense firewall and after the latest update, rate limiting allowlist seems to have stopped working.

With rate limit set to 20, AdGuardHome should only resolve 20 DNS requests per second, unless the client issuing the request is on the allow list. When the client is on the allow list, AdGuardHome shouldn't apply any rate limiting for that client.

Setting rate limit to `0` correctly disables rate limiting.

Guida per i contributori

Apri la guida per i contributori

Valutazione

Questa issue non è ancora stata valutata.

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.