Squeezebox loss of functionality with loss of WAN connection

Max2Play Home 2016 (en) Forums Max2Play as Squeezebox (Player / Server) Squeezebox loss of functionality with loss of WAN connection

This topic contains 3 replies, has 2 voices, and was last updated by  Heiner Moderator 3 years, 1 month ago.

Viewing 4 posts - 1 through 4 (of 4 total)
  • 21. März 2018 at 19:41 #34623

    I’m running Max2Play on 3 RaspberryPi’s (one is acting as a server/player, and they’re all running the current release), and I have 2 Squeezebox radios as well. All devices are on my gigabit LAN, all 3 RPi’s have static IP’s. The music is on an external drive connected to the server RPi.

    When I lose WAN connectivity, I cannot access my local content. The Squeezebox server interface is there, but I only get a shell of an interface(background and the left/right ‚windows‘) but no content to select nor are there any options to select a different player (upper Right corner).

    I have noticed that if I have an active playlist going, and lose WAN, the players keep playing, but am unable to use the server interface.

    I can ping each device and they show up in my Router interface as well as being able to ’see‘ them when using the FING app on my phones.

    Short of not being able to play external (streaming) content, I would think that everything should be available regardless of WAN connectivity or not.

    Is there a setting in Max2Play that I might not have or have improperly selected?

    23. März 2018 at 16:13 #34701

    Hi radiomog,

    Could you paste the debug info log from the WiFi/LAN menu here?

    Also, could you try running one of the Pi’s without static IP to rule this out as a possible source of error?

    26. Oktober 2018 at 6:46 #41666

    Just experienced this problem again. previously, after my post above, I was able to access my LMS Server, and play local content.

    tonight, with loss of WAN, the LMS page only partially loaded (nnn.nnn…:9000)and I couldn’t do anything.

    now that wan is back up, I was able to get the requested DEBUG, but the system is up, so is it still helpful?

    eth0 Link encap:Ethernet HWaddr b8:27:eb:e0:af:43
    inet addr:192.168.0.41 Bcast:192.168.0.255 Mask:255.255.255.0
    UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
    RX packets:398345 errors:0 dropped:0 overruns:0 frame:0
    TX packets:343644 errors:0 dropped:0 overruns:0 carrier:0
    collisions:0 txqueuelen:1000
    RX bytes:169301902 (161.4 MiB) TX bytes:106904905 (101.9 MiB)

    lo Link encap:Local Loopback
    inet addr:127.0.0.1 Mask:255.0.0.0
    UP LOOPBACK RUNNING MTU:65536 Metric:1
    RX packets:84785 errors:0 dropped:0 overruns:0 frame:0
    TX packets:84785 errors:0 dropped:0 overruns:0 carrier:0
    collisions:0 txqueuelen:0
    RX bytes:28271272 (26.9 MiB) TX bytes:28271272 (26.9 MiB)

    ### WLAN ###

    30. Oktober 2018 at 11:02 #41756

    Hi radiomog,

    Did you remove the static IP in this instance?

Viewing 4 posts - 1 through 4 (of 4 total)

You must be logged in to reply to this topic.

Register here