05-22-2024, 06:03 PM
(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 foundAs 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?
