(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.

(05-22-2024, 06:03 PM)TheOldPresbyope Wrote:

(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?

(05-22-2024, 08:27 PM)Tim Curtis Wrote: Someone will need to reproduce your issue in order to troubleshoot it and see if it could be a software bug. We can't just guess at what might be happening :-0

Static IP addressing works fine on my end and based on Kent's tests also on his end and thus I don't have any avenues in the code to investigate.

One thing you could check after setting a static ip address is the actual NM connection file thats generated by the Network Config screen. You can find the files in /etc/NetworkManager/system-connections/ These files are what the NetworkManager system service uses to make connections.

(05-22-2024, 09:44 PM)Tim Curtis Wrote: Your post is missing the lines for [ipv4] section which would contain the ip address info.

Here's some screen shots from a quick test. Static ip address, internet radio playing, etc.

Code:

pi@moode9:~ $ sudo cat /etc/NetworkManager/system-connections/AirnetN5.nmconnection
#########################################
# This file is managed by moOde          
# Wireless: Configured SSID              
#########################################

[connection]
id=AirnetN5
uuid=46850510-1c32-40ea-8113-c266d90b804e
type=wifi
interface-name=wlan0
autoconnect=true
autoconnect-priority=100
[wifi]
mode=infrastructure
ssid=AirnetN5
hidden=false
[wifi-security]
key-mgmt=wpa-psk
psk=xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
[ipv4]
method=manual
address1=192.168.1.251/24
gateway=192.168.1.1
dns=192.168.1.1
[ipv6]
addr-gen-mode=default
method=auto
pi@moode9:~ $

(05-22-2024, 10:15 PM)Tim Curtis Wrote: Try setting Primary DNS to your gateway address 192.168.1.1. Thats a typical config for a residential Router that proxies DNS requests.