05-21-2020, 05:59 PM
@quasimono
Guten tag!
It's hard for me to make order out of the various clues you've posted. Somehow we have to sort out what may be a networking issue vs what may be a moOde issue. Turning on WiFi should not be killing any essential moOde processes. I'm just going to toss out some random thoughts.
1) in post #3 you presented a reasonable looking output from sysinfo.sh for an unconfigured system connected to Ethernet. Looking at the network info:
These are normal values for an IPv4 network with a consumer-grade router assigning the customer-side LAN to a traditional private subnet 192.168.1.x and with DHCP enabled.
Then in post #10 you mention "I also switched IPv6 off for testing....". What is IPv6 vis-a-vis your network and how did you switch it off?
While some components of moOde are not yet IPv6-ready, the underlying Raspbian OS is and does enable IPv6 at the network interfaces. Recently, I have been experimenting with dual stack IPv4/IPv6 on my LAN. I don't see any problem with moOde running in this environment as an IPv4 client but it definitely won't work correctly against an IPv6-only host/browser.
2) The use of "moode.local" is independent of the network issue. The .local suffix is the indicator that you are asking mDNS to resolve the address of hostname "moode" (this process is called zero-configuration networking). It should work in most browser/OS combinations except on Android.
The use of the numeric IP address should always work. If it doesn't then I would suggest the wrong address is being tried. Please note that when WiFi is enabled, your moOde player will have a different IP address for the WiFi interface than it had for the Ethernet interface. That's why it's nice to be able to use a symbolic hostname instead. Various methods are available to determine what the IP address is. Probably the easiest is to ask the router using whatever UI it has. Next easiest is to use a phone- or tablet-based network sniffer app like Fing. Third easiest is to become proficient with Linux command line usage.
3) Don't change so many things randomly. I gather you went from the working system described in post #3 to a semi-responsive system described in post #7. If you get back to that, there are Linux command line exercises we can do in a working ssh session to gather more information if you are up for it.
Regards,
Kent
Guten tag!
It's hard for me to make order out of the various clues you've posted. Somehow we have to sort out what may be a networking issue vs what may be a moOde issue. Turning on WiFi should not be killing any essential moOde processes. I'm just going to toss out some random thoughts.
1) in post #3 you presented a reasonable looking output from sysinfo.sh for an unconfigured system connected to Ethernet. Looking at the network info:
Code:
20200504 063928 worker: -- Network
20200504 063928 worker: eth0 exists
20200504 063928 worker: IP addr (192.168.1.11)
20200504 063928 worker: Netmask (255.255.255.0)
20200504 063928 worker: Gateway (192.168.1.1)
20200504 063928 worker: Pri DNS (192.168.1.1)
20200504 063928 worker: Domain (localdomain)
20200504 063928 worker: wlan0 exists
20200504 063928 worker: wifi country (US)
20200504 063928 worker: wlan0 SSID is blank
20200504 063928 worker: eth0 addr exists, AP mode not started
20200504 063928 worker: wlan0 address not assignedThese are normal values for an IPv4 network with a consumer-grade router assigning the customer-side LAN to a traditional private subnet 192.168.1.x and with DHCP enabled.
Then in post #10 you mention "I also switched IPv6 off for testing....". What is IPv6 vis-a-vis your network and how did you switch it off?
While some components of moOde are not yet IPv6-ready, the underlying Raspbian OS is and does enable IPv6 at the network interfaces. Recently, I have been experimenting with dual stack IPv4/IPv6 on my LAN. I don't see any problem with moOde running in this environment as an IPv4 client but it definitely won't work correctly against an IPv6-only host/browser.
2) The use of "moode.local" is independent of the network issue. The .local suffix is the indicator that you are asking mDNS to resolve the address of hostname "moode" (this process is called zero-configuration networking). It should work in most browser/OS combinations except on Android.
The use of the numeric IP address should always work. If it doesn't then I would suggest the wrong address is being tried. Please note that when WiFi is enabled, your moOde player will have a different IP address for the WiFi interface than it had for the Ethernet interface. That's why it's nice to be able to use a symbolic hostname instead. Various methods are available to determine what the IP address is. Probably the easiest is to ask the router using whatever UI it has. Next easiest is to use a phone- or tablet-based network sniffer app like Fing. Third easiest is to become proficient with Linux command line usage.
3) Don't change so many things randomly. I gather you went from the working system described in post #3 to a semi-responsive system described in post #7. If you get back to that, there are Linux command line exercises we can do in a working ssh session to gather more information if you are up for it.
Regards,
Kent
