yocky

Forum Replies Created

Viewing 6 posts - 1 through 6 (of 6 total)
  • 16. August 2017 at 20:29 #30672

    I came back home this evening and without me doing anything, the issue was gone. No warning message and I could use the Squeezebox functionality. I’ve included an updated debug copy which as you can see is almost identical to the earlier one.

    So I have some questions.

    Doesn’t this invalidate your previous diagnosis?

    Did the WPS solution involve me buying a USB wifi adaptor?

    Why would the system prioritize an ethernet connection that wasn’t made?

    None of this sounds very satisfactory.

    eth0 Link encap:Ethernet HWaddr b8:27:eb:a8:ed:1a
    UP BROADCAST MULTICAST MTU:1500 Metric:1
    RX packets:0 errors:0 dropped:0 overruns:0 frame:0
    TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
    collisions:0 txqueuelen:1000
    RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)

    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:638 errors:0 dropped:0 overruns:0 frame:0
    TX packets:638 errors:0 dropped:0 overruns:0 carrier:0
    collisions:0 txqueuelen:1
    RX bytes:41899 (40.9 KiB) TX bytes:41899 (40.9 KiB)

    wlan0 Link encap:Ethernet HWaddr b8:27:eb:fd:b8:4f
    inet addr:192.168.1.10 Bcast:192.168.1.255 Mask:255.255.255.0
    UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
    RX packets:29197 errors:0 dropped:0 overruns:0 frame:0
    TX packets:10843 errors:0 dropped:0 overruns:0 carrier:0
    collisions:0 txqueuelen:1000
    RX bytes:1971755 (1.8 MiB) TX bytes:2021417 (1.9 MiB)

    • This reply was modified 7 years, 2 months ago by yocky.
    16. August 2017 at 8:03 #30655

    Yes. I have rebooted the device multiple times, including just now in exactly the way you specified. Same result every time.

    Here is the debug info from just after my last reboot.

    eth0 Link encap:Ethernet HWaddr b8:27:eb:a8:ed:1a
    UP BROADCAST MULTICAST MTU:1500 Metric:1
    RX packets:0 errors:0 dropped:0 overruns:0 frame:0
    TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
    collisions:0 txqueuelen:1000
    RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)

    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:186 errors:0 dropped:0 overruns:0 frame:0
    TX packets:186 errors:0 dropped:0 overruns:0 carrier:0
    collisions:0 txqueuelen:1
    RX bytes:13340 (13.0 KiB) TX bytes:13340 (13.0 KiB)

    wlan0 Link encap:Ethernet HWaddr b8:27:eb:fd:b8:4f
    inet addr:192.168.1.10 Bcast:192.168.1.255 Mask:255.255.255.0
    UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
    RX packets:226 errors:0 dropped:0 overruns:0 frame:0
    TX packets:455 errors:0 dropped:0 overruns:0 carrier:0
    collisions:0 txqueuelen:1000
    RX bytes:23300 (22.7 KiB) TX bytes:476050 (464.8 KiB)

    15. August 2017 at 10:06 #30632

    Any more input on this please?

    14. August 2017 at 13:57 #30612

    Last week the Pi was operating fine via wifi. Just a standard dchp connection (no static address). Now I can see it in my router config’s network map and I can reach it via the max2play web interface, but the squeezebox functionality doesn’t work and I get this „No Internet Connection Available“ message.

    Nothing has changed, it just stopped working via wifi.

    14. August 2017 at 11:49 #30609

    ….. should have said, I have the unit running successfully via *ethernet*. Wifi is still not working.

    14. August 2017 at 10:42 #30603

    Sure.

    https://www.max2play.com/en/forums/topic/no-internet-connection-on-wifi/

    The PSU is 18v/3.3A . In fact, ths one: https://www.hifiberry.com/shop/accessories/meanwell-gs60a18-p1j/

    I’m not sure which squeezelite settings you mean, but I haven’t altered anything from the default settings.

    FYI, I have the unit running successfully via LAN now.

    • This reply was modified 7 years, 2 months ago by yocky.
    • This reply was modified 7 years, 2 months ago by yocky.
Viewing 6 posts - 1 through 6 (of 6 total)