AdguardTeam / AdguardTeam/AdGuardHome

v0.106.1 udpWrite returned error + overflow unpacking uint16 -> IPv6

オープン
#3,071 コメント 5 件 リアクション 0 件 担当者 0 名 GitHub で見る
bug needs investigation P4: Low
主要言語
TypeScript
スター
36.9k
フォーク
2.5k
PR マージ指標
30日以内にマージされた PR はありません

説明

* **Version of AdGuard Home server:**
* v0106.1
* **How did you install AdGuard Home:**
* Portainer (Docker) custom network macvlan
* **How did you setup DNS configuration:**
* PI 4 +Portainer (Docker) + UDM Pro
* **If it's a router or IoT, please write device model:**
* PI 4 B
* **CPU architecture:**
* ARM
* **Operating system and version:**
* Raspbian latest

### Expected Behavior
No Log Spam with udpWrite() and or overflow

### Actual Behavior
[info] error while responding to a dns request: udpWrite() returned error, cause: write udp [::]:53->[2003:c1::]:50165: sendmsg: invalid argument (i shortened the IPv6 for privacy)
[info] error handling TCP packet: dns: overflow unpacking uint16

### Screenshots
Will provide them later, if i'm on PC.

Screenshot:
![Screenshot_20210502-143157_Chrome](https://user-images.githubusercontent.com/553212/117033743-f8c2fc00-ad02-11eb-8061-56293ab14222.jpg)

Screenshot2:
![Screenshot_20210502-143258_Chrome](https://user-images.githubusercontent.com/553212/117033849-13957080-ad03-11eb-949e-5c17de10dac4.jpg)

Screenshot3:
Log-04 05 21

### Additional Information
As you can see on the Screenshot, the Config Assistant is showing the public IPv6, shouldn't it also show the local IPv6? And if you setup Adguard Home for the first time, you only have the option for one IP-Adress or all, but there's also no local IPv6 showing.

If i could, i would configure Adguard Home to only respond on IPv4 + IPv6 from local network, i don't want him to listen on public IPv6 😉

Hopefully this is no duplicate of an open issue.

コントリビューションガイド

コントリビューションガイドを開く

評価

この issue はまだ評価されていません。

新しい issue をメールで受け取る

初心者向けの GitHub issue を短くまとめたダイジェスト。