05-22-2024, 07:29 PM
(05-22-2024, 06:03 PM)TheOldPresbyope Wrote:I confirm that all the information is correctly entered in the GUI, but the result in moodeutl -l is as it appears in the previous thread, with the impossibility of accessing the external network and therefore listening to web radios. I need to have a static address as I have many devices at home connected to the wifi network and in some cases they use the MoOde IP address forcing me to search for the new IP. Up until now with the old version it has always worked perfectly, but now I'm encountering this annoying problem. I can put everything in DHCP, it's not a big problem, but I would like to understand why if it worked correctly before, but not anymore.(05-22-2024, 02:35 PM)ECELO Wrote: unfortunately changing the subnet mask seemed to have solved the problem, in reality the GUI shows the change but upon restart, checking with moodeutl -l the connection is still in DHCP, no longer even allowing the connection to the web radios. I honestly think there are major problems with this release.
I answered about the moodeutl -l report in your other thread, but let's keep the discussion about network addressing here since it's not about touch screens.
In that other thread, you reported
Code:20240522 181628 worker: Wireless: method dhcp
20240522 181628 worker: Wireless: address 192.168.1.203
20240522 181628 worker: Wireless: netmask 255.255.255.0
20240522 181628 worker: Wireless: gateway 192.168.1.1
20240522 181628 worker: Wireless: pri DNS none found
20240522 181628 worker: Wireless: domain none found
As I already answered, the Wireless: method dhcp line is incorrect and I can repro the same on my player. This a reporting bug, not a networking bug.
However, in my installation the following 4 lines are reported correctly.
In your case, is 192.168.1.203 the address you assigned statically and w ere you able to access your player via that address?
Is 192.168.1.1 the gateway address you assigned statically?
What's with that Wireless: pri DNS none foundentry? If moOde thinks there is no DNS server then it can't reach hosts on the Internet, including any web radios. Did you explicitly assign a primary (and possibly a secondary) DNS address statically?
As counterexample, I'm playing the JazzGroove on my rebooted, statically addressed moOde 9.0.0 player without issue.
Regards,
Kent
PS - I'm curious. W hat is the use-case you have which makes static addressing an imperative?