search

home-assistant / core

:house_with_garden: Open source home automation that puts local control and privacy first.
https://www.home-assistant.io
Apache License 2.0
73.61k stars 30.77k forks source link

AdGuard filters Docker-Network #94185

Closed kenhoppla closed 1 year ago

kenhoppla commented 1 year ago

The problem

I'm hosting AdGuard in my HomeAssistantOS and just noticed that AdGuard is filtering the IP 172.30.32.3 which I think is my internal Docker-Network. All the traffic in HAOS is filtered right now. How can I turn it off?

What version of Home Assistant Core has the issue?

2023.06.1

What was the last working version of Home Assistant Core?

2023.06.0

What type of installation are you running?

Home Assistant OS

Integration causing the issue

AdGuard

Link to integration documentation on our website

https://www.home-assistant.io/integrations/adguard/

Diagnostics information

No response

Example YAML snippet

No response

Anything in the logs that might be useful for us?

s6-rc: info: service s6rc-oneshot-runner: starting
s6-rc: info: service s6rc-oneshot-runner successfully started
s6-rc: info: service base-addon-banner: starting
-----------------------------------------------------------
 Add-on: AdGuard Home
 Network-wide ads & trackers blocking DNS server
-----------------------------------------------------------
 Add-on version: 4.8.7
 You are running the latest version of this add-on.
 System: Home Assistant OS 10.2  (aarch64 / raspberrypi4-64)
 Home Assistant Core: 2023.5.4
 Home Assistant Supervisor: 2023.06.1
-----------------------------------------------------------
 Please, share the above information when looking for help
 or support in, e.g., GitHub, forums or the Discord chat.
-----------------------------------------------------------
s6-rc: info: service base-addon-banner successfully started
s6-rc: info: service fix-attrs: starting
s6-rc: info: service base-addon-log-level: starting
s6-rc: info: service fix-attrs successfully started
s6-rc: info: service base-addon-log-level successfully started
s6-rc: info: service legacy-cont-init: starting
s6-rc: info: service legacy-cont-init successfully started
s6-rc: info: service init-nginx: starting
s6-rc: info: service init-adguard: starting
s6-rc: info: service init-nginx successfully started
s6-rc: info: service init-adguard successfully started
s6-rc: info: service adguard: starting
s6-rc: info: service adguard successfully started
s6-rc: info: service discovery: starting
s6-rc: info: service nginx: starting
s6-rc: info: service nginx successfully started
[17:32:13] INFO: Starting AdGuard Home server...
2023/06/07 17:32:13.417751 [info] AdGuard Home, version v0.107.29
2023/06/07 17:32:13.418081 [info] AdGuard Home updates are disabled
2023/06/07 17:32:13.428055 [info] tls: using default ciphers
2023/06/07 17:32:13.438731 [info] safesearch default: disabled
2023/06/07 17:32:13.451664 [info] Initializing auth module: /data/adguard/data/sessions.db
2023/06/07 17:32:13.454228 [info] auth: initialized.  users:0  sessions:0
2023/06/07 17:32:13.454497 [info] web: initializing
2023/06/07 17:32:13.664713 [info] dnsproxy: cache: enabled, size 4096 b
2023/06/07 17:32:13.664773 [info] MaxGoroutines is set to 300
2023/06/07 17:32:13.665000 [info] AdGuard Home is available at the following addresses:
2023/06/07 17:32:13.665086 [info] go to http://127.0.0.1:45158
[17:32:13] INFO: Starting NGinx...
[17:32:16] INFO: Successfully send discovery information to Home Assistant.
s6-rc: info: service discovery successfully started
s6-rc: info: service legacy-services: starting
s6-rc: info: service legacy-services successfully started
2023/06/07 17:32:16.737203 [info] Starting the DNS proxy server
2023/06/07 17:32:16.737254 [info] Ratelimit is enabled and set to 20 rps
2023/06/07 17:32:16.737266 [info] The server is configured to refuse ANY requests
2023/06/07 17:32:16.737277 [info] dnsproxy: cache: enabled, size 4194304 b
2023/06/07 17:32:16.737296 [info] MaxGoroutines is set to 300
2023/06/07 17:32:16.737327 [info] Creating the UDP server socket
2023/06/07 17:32:16.739132 [info] Listening to udp://192.168.178.30:53
2023/06/07 17:32:16.739168 [info] Creating the UDP server socket
2023/06/07 17:32:16.740195 [info] Listening to udp://172.30.32.1:53
2023/06/07 17:32:16.740232 [info] Creating the UDP server socket
2023/06/07 17:32:16.740470 [info] Listening to udp://127.0.0.1:53
2023/06/07 17:32:16.740492 [info] Creating the UDP server socket
2023/06/07 17:32:16.741857 [info] Listening to udp://[::1]:53
2023/06/07 17:32:16.741894 [info] Creating a TCP server socket
2023/06/07 17:32:16.742080 [info] Listening to tcp://192.168.178.30:53
2023/06/07 17:32:16.742100 [info] Creating a TCP server socket
2023/06/07 17:32:16.742830 [info] Listening to tcp://172.30.32.1:53
2023/06/07 17:32:16.742866 [info] Creating a TCP server socket
2023/06/07 17:32:16.743178 [info] Listening to tcp://127.0.0.1:53
2023/06/07 17:32:16.743197 [info] Creating a TCP server socket
2023/06/07 17:32:16.743914 [info] Listening to tcp://[::1]:53
2023/06/07 17:32:16.744170 [info] Entering the UDP listener loop on 172.30.32.1:53
2023/06/07 17:32:16.744453 [info] Entering the UDP listener loop on 192.168.178.30:53
2023/06/07 17:32:16.744698 [info] Entering the tcp listener loop on [::1]:53
2023/06/07 17:32:16.744822 [info] Entering the tcp listener loop on 192.168.178.30:53
2023/06/07 17:32:16.744890 [info] Entering the tcp listener loop on 172.30.32.1:53
2023/06/07 17:32:16.744957 [info] Entering the tcp listener loop on 127.0.0.1:53
2023/06/07 17:32:16.745108 [info] Entering the UDP listener loop on 127.0.0.1:53
2023/06/07 17:32:16.745788 [info] Entering the UDP listener loop on [::1]:53
2023/06/07 20:32:17.634364 [info] saving contents of filter #1 into /data/adguard/data/filters/1.txt
2023/06/07 20:32:17.636996 [info] updated filter 1: 1053516 bytes, 53213 rules
2023/06/07 20:32:18.158468 [info] saving contents of filter #1679860731 into /data/adguard/data/filters/1679860731.txt
2023/06/07 20:32:18.160051 [info] updated filter 1679860731: 226086 bytes, 4807 rules
2023/06/07 20:32:19.136906 [info] saving contents of filter #1679861224 into /data/adguard/data/filters/1679861224.txt
2023/06/07 20:32:19.140261 [info] updated filter 1679861224: 1452678 bytes, 43874 rules
2023/06/07 20:32:19.780457 [info] saving contents of filter #1679861225 into /data/adguard/data/filters/1679861225.txt
2023/06/07 20:32:19.782667 [info] updated filter 1679861225: 853199 bytes, 34240 rules
2023/06/07 20:32:19.782712 [info] Updated filter #1.  Rules: 53170 -> 53213
2023/06/07 20:32:19.782726 [info] Updated filter #1679860731.  Rules: 4806 -> 4807
2023/06/07 20:32:19.782737 [info] Updated filter #1679861224.  Rules: 43799 -> 43874
2023/06/07 20:32:19.782746 [info] Updated filter #1679861225.  Rules: 34237 -> 34240

Additional information

No response

home-assistant[bot] commented 1 year ago

Hey there @frenck, mind taking a look at this issue as it has been labeled with an integration (adguard) you are listed as a code owner for? Thanks!

Code owner commands Code owners of `adguard` can trigger bot actions by commenting: - `@home-assistant close` Closes the issue. - `@home-assistant rename Awesome new title` Renames the issue. - `@home-assistant reopen` Reopen the issue. - `@home-assistant unassign adguard` Removes the current integration label and assignees on the issue, add the integration domain after the command.

(message by CodeOwnersMention)

adguard documentation adguard source (message by IssueLinks)

frenck commented 1 year ago

Hi there @kenhoppla 👋

It seems like you want to report an issue with the use of an third-party add-on: AdGuard Home.

However, the Home Assistant project does not support third-party add-ons or integrations. Please check the third-party project on where to report issues or get support.

Thanks 👍

../Frenck