moodeaudio.org > Moode Forum › moOde audio player › Support v
[SOLVED] Why is Moode pounding my router?

Thank you for your donation!


Cloudsmith graciously provides open-source package management and distribution for our project.


Thread Modes
Solved: Why is Moode pounding my router?
HemiRick Offline
Member
*
Posts: 82
Threads: 10
Joined: Dec 2018
Reputation: 2
#21
09-12-2019, 11:09 AM
(09-11-2019, 11:56 AM)Tim Curtis Wrote:
Code:
netstat
I've done a sudo netstat -nputw and the results yield nothing interesting or unexpected.
Find
Reply
HemiRick Offline
Member
*
Posts: 82
Threads: 10
Joined: Dec 2018
Reputation: 2
#22
09-12-2019, 11:21 AM
The etc hosts change has fixed the ipv4 part of the problem, but ipv6 is still unhappy

Sep 12 12:15:24 dnsmasq[26771]: query[A] EA7300.home.linksys.com from 192.168.1.130
Sep 12 12:15:24 dnsmasq[26771]: /etc/hosts EA7300.home.linksys.com is 192.168.1.1
Sep 12 12:15:24 dnsmasq[26771]: query[AAAA] EA7300.home.linksys.com from 192.168.1.130
Sep 12 12:15:24 dnsmasq[26771]: forwarded EA7300.home.linksys.com to 1.0.0.1
Sep 12 12:15:24 dnsmasq[26771]: reply EA7300.home.linksys.com is NODATA-IPv6
Sep 12 12:15:24 dnsmasq[26771]: query[A] EA7300.home.linksys.com from 192.168.1.130
Sep 12 12:15:24 dnsmasq[26771]: /etc/hosts EA7300.home.linksys.com is 192.168.1.1
Sep 12 12:15:24 dnsmasq[26771]: query[AAAA] EA7300.home.linksys.com from 192.168.1.130
Sep 12 12:15:24 dnsmasq[26771]: cached EA7300.home.linksys.com is NODATA-IPv6
Sep 12 12:15:24 dnsmasq[26771]: query[A] EA7300.home.linksys.com from 192.168.1.130
Sep 12 12:15:24 dnsmasq[26771]: /etc/hosts EA7300.home.linksys.com is 192.168.1.1
Sep 12 12:15:24 dnsmasq[26771]: query[AAAA] EA7300.home.linksys.com from 192.168.1.130
Sep 12 12:15:24 dnsmasq[26771]: cached EA7300.home.linksys.com is NODATA-IPv6
Sep 12 12:15:24 dnsmasq[26771]: query[A] EA7300.home.linksys.com from 192.168.1.130
Sep 12 12:15:24 dnsmasq[26771]: /etc/hosts EA7300.home.linksys.com is 192.168.1.1
Sep 12 12:15:24 dnsmasq[26771]: query[AAAA] EA7300.home.linksys.com from 192.168.1.130
Sep 12 12:15:24 dnsmasq[26771]: cached EA7300.home.linksys.com is NODATA-IPv6
Sep 12 12:15:24 dnsmasq[26771]: query[A] EA7300.home.linksys.com from 192.168.1.130
Sep 12 12:15:24 dnsmasq[26771]: /etc/hosts EA7300.home.linksys.com is 192.168.1.1
Sep 12 12:15:24 dnsmasq[26771]: query[AAAA] EA7300.home.linksys.com from 192.168.1.130
Sep 12 12:15:24 dnsmasq[26771]: cached EA7300.home.linksys.com is NODATA-IPv6
Sep 12 12:15:24 dnsmasq[26771]: query[A] EA7300.home.linksys.com from 192.168.1.130
Sep 12 12:15:24 dnsmasq[26771]: /etc/hosts EA7300.home.linksys.com is 192.168.1.1
Sep 12 12:15:24 dnsmasq[26771]: query[AAAA] EA7300.home.linksys.com from 192.168.1.130
Sep 12 12:15:24 dnsmasq[26771]: cached EA7300.home.linksys.com is NODATA-IPv6
Sep 12 12:15:24 dnsmasq[26771]: query[A] EA7300.home.linksys.com from 192.168.1.130
Sep 12 12:15:24 dnsmasq[26771]: /etc/hosts EA7300.home.linksys.com is 192.168.1.1
Sep 12 12:15:24 dnsmasq[26771]: query[AAAA] EA7300.home.linksys.com from 192.168.1.130
Sep 12 12:15:24 dnsmasq[26771]: cached EA7300.home.linksys.com is NODATA-IPv6
Sep 12 12:15:24 dnsmasq[26771]: query[A] EA7300.home.linksys.com from 192.168.1.130
Sep 12 12:15:24 dnsmasq[26771]: /etc/hosts EA7300.home.linksys.com is 192.168.1.1
Find
Reply
TheOldPresbyope Offline
Moderator
****
Posts: 5,573
Threads: 168
Joined: Apr 2018
Reputation: 207
#23
09-12-2019, 01:06 PM
@HemiRick

You haven't "fixed" the problem; you've just told your DNS server to lie when it's asked to resolve a bogus FQDN.

I've about concluded I can't help you but before I give up I have one last request:

On your moOde player, what is the content of these three files 

/etc/hosts
/etc/resolv.conf
/etc/dhcpcd.conf

Don't paraphrase, just copy them into code blocks in your reply.

If these are clean then I concede the game to rb0135  Smile

Regards,
Kent
Find
Reply
HemiRick Offline
Member
*
Posts: 82
Threads: 10
Joined: Dec 2018
Reputation: 2
#24
09-12-2019, 05:00 PM (This post was last modified: 09-12-2019, 11:12 PM by HemiRick.)
(09-12-2019, 01:06 PM)TheOldPresbyope Wrote: @HemiRick

You haven't "fixed" the problem; you've just told your DNS server to lie when it's asked to resolve a bogus FQDN.

/etc/hosts
/etc/resolv.conf
/etc/dhcpcd.conf
agreed
  •   
Moodes hosts file is stock

Generated by resolvconf
nameserver 192.168.1.135                                                                                      
nameserver 2601:3c5:c200:c9d:26f5:a2ff:fe00:afce     
  • the netstat -nputw was on the pihole, this is MoodesActive Internet connections (w/o servers)                                                                     Proto Recv-Q Send-Q Local Address           Foreign Address         State       PID/Program name              tcp        0      0 192.168.1.130:80        192.168.1.3:57401       ESTABLISHED 435/nginx: worker p           tcp        0      0 192.168.1.130:58562     192.168.1.110:8888      TIME_WAIT   -                             tcp        0      0 192.168.1.130:80        192.168.1.108:59637     ESTABLISHED 435/nginx: worker p           tcp        0      0 192.168.1.130:58548     192.168.1.110:8888      TIME_WAIT   -                             tcp        0      0 127.0.0.1:6600          127.0.0.1:36288         ESTABLISHED 886/mpd                       tcp        0      0 192.168.1.130:80        192.168.1.108:59638     TIME_WAIT   -                             tcp        0      0 192.168.1.130:58556     192.168.1.110:8888      TIME_WAIT   -                             tcp        0      0 192.168.1.130:58598     192.168.1.110:8888      TIME_WAIT   -                             tcp        0      0 127.0.0.1:51644         127.0.0.1:6600          ESTABLISHED 13179/php-fpm: pool                                                                                                                        tcp        0      0 192.168.1.130:58596     192.168.1.110:8888      TIME_WAIT   -                             tcp        0      0 192.168.1.130:58604     192.168.1.110:8888      TIME_WAIT   -                             tcp        0      0 192.168.1.130:58594     192.168.1.110:8888      TIME_WAIT   -                             tcp        0      0 192.168.1.130:49154     192.168.1.108:59700     TIME_WAIT   -                             tcp        0      0 192.168.1.130:58558     192.168.1.110:8888      TIME_WAIT   -                                                                                                                                          tcp        0      0 192.168.1.130:58600     192.168.1.110:8888      TIME_WAIT   -                             tcp        0      0 192.168.1.130:49154     192.168.1.108:59679     TIME_WAIT   -                             tcp        0      0 192.168.1.130:58546     192.168.1.110:8888      TIME_WAIT   -                             tcp        0    309 192.168.1.130:4200      192.168.1.108:59645     ESTABLISHED 970/shellinaboxd                                                                                                                            tcp        0      0 192.168.1.130:58588     192.168.1.110:8888      TIME_WAIT   -                             tcp        0      0 192.168.1.130:58590     192.168.1.110:8888      TIME_WAIT   -                             tcp        0      0 127.0.0.1:59504         127.0.0.1:6600          ESTABLISHED 16706/php-fpm: pool           tcp        0      0 192.168.1.130:58550     192.168.1.110:8888      TIME_WAIT   -                                                                                                                                          tcp        0      0 192.168.1.130:4200      192.168.1.108:59647     ESTABLISHED 970/shellinaboxd              tcp        0      0 192.168.1.130:58586     192.168.1.110:8888      TIME_WAIT   -                             tcp        0      0 127.0.0.1:6600          127.0.0.1:51644         ESTABLISHED 886/mpd                       tcp        0      0 192.168.1.130:80        192.168.1.3:54560       ESTABLISHED 435/nginx: worker p           tcp        0      0 127.0.0.1:36288         127.0.0.1:6600          ESTABLISHED 10476/upmpdcli                tcp        0      0 127.0.0.1:6600          127.0.0.1:59504         ESTABLISHED 886/mpd                       tcp        0      0 192.168.1.130:58602     192.168.1.110:8888      TIME_WAIT   -                             tcp        0      0 192.168.1.130:49154     192.168.1.108:59687     TIME_WAIT   -                             tcp        0      0 192.168.1.130:58606     192.168.1.110:8888      TIME_WAIT   -                             tcp        0      0 192.168.1.130:58566     192.168.1.110:8888      TIME_WAIT   -                             tcp        0      0 192.168.1.130:49154     192.168.1.108:59727     TIME_WAIT   -                             tcp        0      0 192.168.1.130:49154     192.168.1.108:59720     TIME_WAIT   -                             tcp        0      0 192.168.1.130:60926     192.168.1.3:445         ESTABLISHED -                             tcp        0      0 192.168.1.130:58544     192.168.1.110:8888      TIME_WAIT   -                             tcp        0      0 127.0.0.1:6600          127.0.0.1:58236         ESTABLISHED 886/mpd                       tcp        0      0 192.168.1.130:58552     192.168.1.110:8888      TIME_WAIT   -                             tcp        0      0 192.168.1.130:50930     192.168.1.108:445       ESTABLISHED -                             tcp        0      0 127.0.0.1:58236         127.0.0.1:6600          ESTABLISHED 16697/php-fpm: pool           tcp        0      0 192.168.1.130:80        192.168.1.108:59636     TIME_WAIT   -                             tcp        0      0 192.168.1.130:4200      192.168.1.108:59648     TIME_WAIT   -                             tcp        0      0 192.168.1.130:58584     192.168.1.110:8888      TIME_WAIT   -                             tcp        0      0 127.0.0.1:59500         127.0.0.1:6600          ESTABLISHED 16707/php-fpm: pool           tcp        0      0 192.168.1.130:58554     192.168.1.110:8888      TIME_WAIT   -
                                                                                                             

My active host file is on the pi hole 
108 is main win10 box
110 is an integra recviever w DLNA
130 is Moode
135 is pi hole
Find
Reply
Tim Curtis Online
moOde audio founder
******
Posts: 12,056
Threads: 272
Joined: Mar 2018
Reputation: 459
#25
09-12-2019, 05:14 PM
Please edit and fix your post. Place command and log output in code boxes so users can more easily read it.

Its the 5th button from the right on the toolbar.
Enjoy the Music!
moodeaudio.org | Mastodon Feed | GitHub
Website Find
Reply
TheOldPresbyope Offline
Moderator
****
Posts: 5,573
Threads: 168
Joined: Apr 2018
Reputation: 207
#26
09-12-2019, 05:49 PM
What Tim said!

I did notice in the first few lines that your moOde player is in communication with your "Integra receiver". 

I know nothing about them but if it has TCP/IP capability, then it becomes a suspect too.

I don't see anything amiss with the two files you did copy (I have to assume the IPv6 address listed in resolv.conf is correct), which again suggests you have a problem with your LAN which is external to moOde. At this point, I'm out.

Regards,
Kent
Find
Reply
HemiRick Offline
Member
*
Posts: 82
Threads: 10
Joined: Dec 2018
Reputation: 2
#27
09-13-2019, 04:56 AM
I've contacted Linksys tech support, 1st level person was clueless, elevated to 2nd level,. waiting on them to reply.
I'm hoping they can at least tell me where moode got the URL from.
Find
Reply
HemiRick Offline
Member
*
Posts: 82
Threads: 10
Joined: Dec 2018
Reputation: 2
#28
09-17-2019, 02:06 AM
This is Dennis from Linksys Technical Support.

Please have your music server checked by its manufacturer as you have mentioned that the rest of your devices are working fine. We have not encountered such concern before. Please ask them if there is a need to have its firmware or software updated.
Find
Reply
DRONE7 Offline
Senior Member+
*
Posts: 1,462
Threads: 105
Joined: Mar 2018
Reputation: 67
#29
09-17-2019, 07:07 AM
(09-17-2019, 02:06 AM)HemiRick Wrote: This is Dennis from Linksys Technical Support.

Please have your music server checked by its manufacturer as you have mentioned that the rest of your devices are working fine. We have not encountered such concern before. Please ask them if there is a need to have its firmware or software updated.

https://www.raspberrypi.org/

I think Dennis from Linksys Technical Support is playing 'pass the parcel'   Wink
You perhaps need to upgrade your tech-support beyond Dennis.... ask for the next tier above ...
----------
bob
Find
Reply
HemiRick Offline
Member
*
Posts: 82
Threads: 10
Joined: Dec 2018
Reputation: 2
#30
09-17-2019, 08:13 AM
The number of these requests has gone to nearly zero after turning off UPnP/DLNA....so it was obviously something to do w them.
Find
Reply


Forum Jump: