HAOS Network related issues

AlDek · June 17, 2025, 3:58pm

I have HAOS installed on bare metal (mini PC Beelink EQ12).
Everything is working well, but I have strange and incomprehensible things about network services.

I have a host with two network adapters. The second adapter is disabled. But in the DNS logs, I constantly see the following messages:

[INFO] 172.30.32.1:32836 - 41593 "A IN enp2s0.local.hass.io. udp 38 false 512" NXDOMAIN qr,aa,rd 38 0.000100033s
[INFO] 172.30.32.1:60633 - 6726 "A IN enp2s0.local.hass.io. udp 38 false 512" NXDOMAIN qr,aa,rd 38 0.000365684s
[INFO] 172.30.32.1:33155 - 15446 "A IN enp2s0.local.hass.io. udp 38 false 512" NXDOMAIN qr,aa,rd 38 0.000096666s
[INFO] 172.30.32.1:43557 - 62536 "A IN enp2s0.local.hass.io. udp 38 false 512" NXDOMAIN qr,aa,rd 38 0.000102388s

I have IPv6 completely disabled. But in the system information, I see a lot of assigned V6 ips.

image994×1442 81 KB

This situation does not interfere with the work of “HA”, but I do not understand why this is happening.
Maybe someone knows and will explain whether this is correct or not and why it is so in general.
Thanks!

SJ20035 · June 18, 2025, 9:23am

Are you using the Samba Share addon?

github.com/home-assistant/plugin-dns

Samba Share generating UDP port 37 DNS queries for disabled host wifi network

opened 01:13PM - 01 Apr 25 UTC

ThisWayToo

Since I do not have permissions to reopen a closed bug report, I am creating thi…s one. This is a description of new findings for the issue previously reported in: [https://github.com/home-assistant/plugin-dns/issues/110](url) Just like in that report, I am seeing UDP port 37 queries in the DNS logging for a disabled WLAN network adapter. `[INFO] 172.30.32.1:47933 - 30815 "A IN wlan0.local.hass.io. udp 37 false 512" NXDOMAIN qr,aa,rd 37 0.000271927s` The messages start as soon as the I start the Samba Share Add-on, and then stop as soon as I stop Samba Share. I can toggle the behavior on and off that way. While the messages seem pretty harmless, they are being generated at around a 2x per minute rate, so a not insignificant amount of log data being generated for network adapter that is not even active. This was tested in OS 15.1 on a RPi 4.

WallyR · June 18, 2025, 9:29am

IPv6 is disabled in HA, but not in Docker, so other addon/containers might have IPv6 enabled.

AlDek · June 21, 2025, 8:15am

But what’s the point of having addresses if the adapters are disabled?
The disabled adapter does not have ipv4 assigned, however it has IPv6 assigned.

And why :
IPv6 addresses: enp1s0 (fe80::5925:132d:8997:d7bf/64)
Announce addresses: 192.168.2.43, fe80::5925:132d:8997:d7bf

Finally: enp1s0 is physical adapter (interface) connected to LAN announces IPv6…

In this case, I don’t understand at all what the “Disable IPv6” option is for.

WallyR · June 21, 2025, 8:17am

Fe80 is an auto assigned address for all IPv6 interfaces.
It is used to configure the interface with other settings.

AlDek · June 21, 2025, 8:24am

Yep.
Absolutely the same behavior.
Every 30 seconds.
But I have the Ethernet adapter enp2s0 (second adapter) disabled, not the WiFi.

AlDek · June 25, 2025, 7:21am

Yes!
With the SAMBA 12.5.2 update, the binding to disabled network interfaces has disappeared.
But some strange reverse DNS (PTR) lookups are in the logs.
It looks like scanning (by UDP ports 54, 55, 65, 66) of the entire 192.168.2.0/24 network, but in some strange way…

[INFO] 127.0.0.1:35217 - 63171 "PTR IN 4.2.168.192.in-addr.arpa. udp 65 false 1232" NXDOMAIN qr,rd,ra 42 0.10123161s
[INFO] 172.30.32.1:41630 - 1911 "PTR IN 4.2.168.192.in-addr.arpa. udp 65 false 1232" NXDOMAIN qr,rd,ra 42 0.116052183s
[INFO] 127.0.0.1:50624 - 12224 "PTR IN 8.2.168.192.in-addr.arpa. udp 65 false 1232" NXDOMAIN qr,rd,ra 42 0.095410942s
[INFO] 172.30.32.1:41630 - 8455 "PTR IN 8.2.168.192.in-addr.arpa. udp 65 false 1232" NXDOMAIN qr,rd,ra 42 0.115510662s
[INFO] 127.0.0.1:36173 - 500 "PTR IN 3.2.168.192.in-addr.arpa. udp 65 false 1232" NXDOMAIN qr,rd,ra 42 0.101773465s
[INFO] 172.30.32.1:41630 - 43866 "PTR IN 3.2.168.192.in-addr.arpa. udp 65 false 1232" NXDOMAIN qr,rd,ra 42 0.11775756s
[INFO] 172.30.32.1:41630 - 38658 "PTR IN 1.2.168.192.in-addr.arpa. udp 65 false 1232" NXDOMAIN qr,rd,ra 42 0.118258178s
[INFO] 127.0.0.1:37176 - 11862 "PTR IN 1.2.168.192.in-addr.arpa. udp 65 false 1232" NXDOMAIN qr,rd,ra 42 0.099927322s
[INFO] 127.0.0.1:39964 - 49207 "PTR IN 7.2.168.192.in-addr.arpa. udp 65 false 1232" NXDOMAIN qr,rd,ra 42 0.097741682s
[INFO] 172.30.32.1:41630 - 63434 "PTR IN 7.2.168.192.in-addr.arpa. udp 65 false 1232" NXDOMAIN qr,rd,ra 42 0.116997604s
...
[INFO] 127.0.0.1:33967 - 9038 "PTR IN 9.2.168.192.in-addr.arpa. udp 65 false 1232" NXDOMAIN qr,rd,ra 42 0.095730855s
[INFO] 172.30.32.1:41630 - 20709 "PTR IN 9.2.168.192.in-addr.arpa. udp 65 false 1232" NXDOMAIN qr,rd,ra 42 0.117815174s
[INFO] 127.0.0.1:40679 - 17825 "PTR IN 14.2.168.192.in-addr.arpa. udp 66 false 1232" NXDOMAIN qr,rd,ra 43 0.095064136s
[INFO] 172.30.32.1:41630 - 43894 "PTR IN 14.2.168.192.in-addr.arpa. udp 66 false 1232" NXDOMAIN qr,rd,ra 43 0.116830174s
[INFO] 127.0.0.1:39944 - 50913 "PTR IN 5.2.168.192.in-addr.arpa. udp 65 false 1232" NXDOMAIN qr,rd,ra 42 0.100374701s
[INFO] 172.30.32.1:41630 - 29489 "PTR IN 5.2.168.192.in-addr.arpa. udp 65 false 1232" NXDOMAIN qr,rd,ra 42 0.119467884s
...
[INFO] 172.30.32.1:59957 - 43750 "PTR IN 115.2.168.192.in-addr.arpa. udp 55 false 1232" NXDOMAIN qr,rd,ra 44 0.039726475s
[INFO] 127.0.0.1:55855 - 2180 "PTR IN 120.2.168.192.in-addr.arpa. udp 55 false 1232" NXDOMAIN qr,rd,ra 44 0.022020955s
[INFO] 172.30.32.1:59957 - 15705 "PTR IN 120.2.168.192.in-addr.arpa. udp 55 false 1232" NXDOMAIN qr,rd,ra 44 0.039922109s
[INFO] 127.0.0.1:44254 - 26058 "PTR IN 84.2.168.192.in-addr.arpa. udp 54 false 1232" NXDOMAIN qr,rd,ra 43 0.022756162s
[INFO] 127.0.0.1:58867 - 42189 "PTR IN 93.2.168.192.in-addr.arpa. udp 54 false 1232" NXDOMAIN qr,rd,ra 43 0.023314085s
[INFO] 127.0.0.1:60717 - 59755 "PTR IN 83.2.168.192.in-addr.arpa. udp 54 false 1232" NXDOMAIN qr,rd,ra 43 0.023849284s
[INFO] 172.30.32.1:59957 - 65126 "PTR IN 84.2.168.192.in-addr.arpa. udp 54 false 1232" NXDOMAIN qr,rd,ra 43 0.042201526s
[INFO] 172.30.32.1:59957 - 19221 "PTR IN 83.2.168.192.in-addr.arpa. udp 54 false 1232" NXDOMAIN qr,rd,ra 43 0.042250049s
[INFO] 172.30.32.1:59957 - 47628 "PTR IN 93.2.168.192.in-addr.arpa. udp 54 false 1232" NXDOMAIN qr,rd,ra 43 0.04171157s
[INFO] 127.0.0.1:57704 - 3766 "PTR IN 106.2.168.192.in-addr.arpa. udp 55 false 1232" NXDOMAIN qr,rd,ra 44 0.023488301s
...
[INFO] 172.30.32.1:59957 - 57919 "PTR IN 68.2.168.192.in-addr.arpa. udp 54 false 1232" NXDOMAIN qr,rd,ra 43 0.043694409s
[INFO] 127.0.0.1:55771 - 8672 "PTR IN 66.2.168.192.in-addr.arpa. udp 54 false 1232" NXDOMAIN qr,rd,ra 43 0.022671431s
[INFO] 172.30.32.1:59957 - 54756 "PTR IN 66.2.168.192.in-addr.arpa. udp 54 false 1232" NXDOMAIN qr,rd,ra 43 0.043825026s
[INFO] 127.0.0.1:59475 - 42948 "PTR IN 126.2.168.192.in-addr.arpa. udp 55 false 1232" NXDOMAIN qr,rd,ra 44 0.021970401s
[INFO] 172.30.32.1:59957 - 183 "PTR IN 126.2.168.192.in-addr.arpa. udp 55 false 1232" NXDOMAIN qr,rd,ra 44 0.040965385s
[INFO] 127.0.0.1:33967 - 16038 "PTR IN 94.2.168.192.in-addr.arpa. udp 54 false 1232" NXDOMAIN qr,rd,ra 43 0.021092276s
[INFO] 172.30.32.1:59957 - 40413 "PTR IN 94.2.168.192.in-addr.arpa. udp 54 false 1232" NXDOMAIN qr,rd,ra 43 0.042890708s

WallyR · June 25, 2025, 3:59pm

Ports makes no sense in DNS lookups.

AlDek · June 25, 2025, 8:31pm

Yes - THESE port “make no sense in DNS lookup”.
So I wrote that there are strange requests…
Maybe the author of the code will decipher the log - what does 55, 54, 65, 66 mean?
I have > 7600 requests/log lines from last HA restart 13 hours ago.
1 request per 6 seconds average…
Why is this done?
And a log without a timestamp is somehow not good… IMHO

WallyR · June 26, 2025, 7:10am

It is probably just a discovery protocol that are doing lookups.