mirror of
https://github.com/AdguardTeam/AdGuardHome.git
synced 2026-03-04 00:01:12 -05:00
Client shows 0.0.0.0 #1234
Labels
No labels
P1: Critical
P2: High
P3: Medium
P4: Low
UI
bug
cannot reproduce
compatibility
dependencies
docker
documentation
duplicate
enhancement
enhancement
external libs
feature request
good first issue
help wanted
infrastructure
invalid
localization
needs investigation
performance
potential-duplicate
question
recurrent
research
snap
waiting for data
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/AdGuardHome#1234
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @cruunnerr on GitHub (Jan 4, 2020).
Originally assigned to: @szolin on GitHub.
Hi guys,
I use the actual Version of AdGuard Home. Since i updated last time I have multiple Query logs show "0.0.0.0" as Client address.
I captured the NIC of my Router to see what happens there... So the client with the IP "10.10.20.203" sends DNS request to my AdGuard Home Server (10.10.10.10).
Adguard sends to the client the IP "0.0.0.0" and in the Web Interface AdGuard shows me, that the Client-Address would be "0.0.0.0"....
I don't understand that.... Sorry guys. Not the best IT-specialist ^^
Edit:
Oh, and it's just a normal Filter-List:
https://raw.githubusercontent.com/cruunnerr/Adguard/master/Blocklist.txt
@nelox commented on GitHub (Jan 6, 2020):
I observe the same behaviour (AdGuardHome v0.100.8):
Filter list:
https://raw.githubusercontent.com/StevenBlack/hosts/master/hosts
@htjain commented on GitHub (Jan 6, 2020):
+1
@Mosney commented on GitHub (Jan 7, 2020):
ditto, rule is https://cdn.jsdelivr.net/gh/neoFelhz/neohosts@gh-pages/full/hosts.txt

@szolin commented on GitHub (Jan 9, 2020):
Yes, thank you!
A quick fix is coming...
A normal fix will be in #882 where we will stop using "Result"{} json object in logs.