LE making 10000s of network requests to my NAS

Hi,

Since the upgrade to the latest newest version of LE I noticed that my network requests went through the roof. I can see that in Pi-hole otherwise I wouldn't even have noticed it. I have no problems though.

I use sql library which is stored on my Nas

As you can see it made 22 requests within the same second.

I 'think' its mostly when it updates the library but not everything.

When I run kodi on my windows pc and do a lirbrary update I don't see this kind of spam.

Quote from mglae

synologynas is likely a local hostname to be resolved.

Unfortunately resolving host names via nmblookup was dropped from kodi 20, now DNS lookups are finally used.

You can try to enable WS-Discovery via Settings->Services->SMB Client.

Yes, it's local hostname of my NAS.

I do see that the 'mediasources.xml' is using

  <mediasources>
<network>
<location id="1">smb://USER:PASSWORD@SynologyNAS/</location>
</network>
</mediasources>

Along with passwords.xml

<passwords>
<path>
<from pathversion="1">smb://SynologyNAS/SynologyNAS</from>
<to pathversion="1">smb://USER:PASSWORD@SynologyNAS/SynologyNAS/Movies/</to>
</path>
</passwords>

sources.xml

<sources>
<programs>
<default pathversion="1"/>
</programs>
<video>
<default pathversion="1"/>
<source>
<name>Videos</name>
<path pathversion="1">/storage/videos/</path>
<allowsharing>true</allowsharing>
</source>
<source>
<name>TV Shows</name>
<path pathversion="1">smb://SynologyNAS/SynologyNAS/Tv-Shows/</path>
<allowsharing>true</allowsharing>
</source>
<source>
<name>Movies</name>
<path pathversion="1">smb://SynologyNAS/SynologyNAS/Movies/</path>
<allowsharing>true</allowsharing>
</source>
</video>
<music>
<default pathversion="1"/>
<source>
<name>Music</name>
<path pathversion="1">/storage/music/</path>
<allowsharing>true</allowsharing>
</source>
</music>
<pictures>
<default pathversion="1"/>
<source>
<name>Pictures</name>
<path pathversion="1">/storage/pictures/</path>
<allowsharing>true</allowsharing>
</source>
</pictures>
<files>
<default pathversion="1"/>
<source>
<name>SynologyNAS</name>
<path pathversion="1">smb://SynologyNAS/SynologyNAS/</path>
<allowsharing>true</allowsharing>
</source>
<source>
<name>storage</name>
<path pathversion="1">/storage/</path>
<allowsharing>true</allowsharing>
</source>
</files>
<games>
<default pathversion="1"/>
</games>
</sources>

I tried to enable WS-Discovery but didn't make any difference.

Quote from chewitt

LE is using the default libc resolver and this caches records according to their TTL values so I doubt caching is the issue. I'd make an educated guess that Kodi makes some form of discovery request which is being denied or sinkholed by Pi Hole and so the request is being repeated (ad infinitum) hoping to get a response (which never comes). There is probably something in Kodi that could have better failure logic. In the same breath Pi Hole improvement to not break the world's most popular mediacentre app would be a good thing too. The decision to use Pi Hole also makes it a self-inflicted problem, sort of, so both sets of developers will probably point fingers at the other.

More verbose logging from Pi Hole and/or perhaps a PCAP of the traffic to look at would be useful.

I made a pcap and verbose logging file. Is there any place where I can upload it safely (especially the pcap, not sure if sensitive data is in it and the file is almost 100mb big as well)

Quote from HiassofT

The screenshot in your first post is showing that your PiHole received a DNS A (address) request for "synologynas" and responded with NXDOMAIN (no address) - so your PiHole doesn't know anything about a "synologynas" host in your LAN.

You may want to add your local domain name (eg ".lan") to the source hostname (eg "synologynas.lan") and make sure PiHole resolves the name to the IP correctly.

so long,

Hias

It looks like you are right.

I added it in pihole and don't see those massive requests again. I'm still at work so can't test a lot but will do when I get back.

However it's still strange for me because I never used this feature and hardly make use of .local/lan domains.

Thanks

Yes, tested it yday and it's solved,ty!