[SOLVED] WIFI STATIC mode does not work

[ECELO]

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.

[TheOldPresbyope]

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?

[Tim Curtis]

If no Primary DNS address was specified there will be a lot of network breakage :-0

I should also mention that when setting a static IP address there needs to be a configuration in the Router to map the address to a host name other wise http://host wont work. t's usually done in the /etc/hosts file or in some Router config screen.

[ECELO]

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?

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.

[Tim Curtis]

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.

[ECELO]

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.

this is all that appears in my SSID file after setting STATIC in MoOde. No external connection is possible, while there are no problems with my local network.

#########################################
# This file is managed by moOde
# Wireless: Configured SSID
#########################################

[connection]
id=BlackHole
uuid=2faad75e-7699-4bc0-a7d9-42f645949399
type=wifi
interface-name=wlan0
autoconnect=true
autoconnect-priority=100
[wifi]
mode=infrastructure
ssid=BlackHole
hidden=false
[wifi-security]
key-mgmt=wpa-psk
psk=a8b7e7895c64e88d4e4412254f0b536d8fadb85314385b7019616f842406531c
[ipv4]

[Tim Curtis]

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:~ $

[ECELO]

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:~ $

I really can't understand it all seems the same, but as you can see it doesn't connect to the internet.

#########################################
# This file is managed by moOde
# Wireless: Configured SSID
#########################################

[connection]
id=BlackHole
uuid=e3327a39-df8f-477b-8565-1b4c15d014b7
type=wifi
interface-name=wlan0
autoconnect=true
autoconnect-priority=100
[wifi]
mode=infrastructure
ssid=BlackHole
hidden=false
[wifi-security]
key-mgmt=wpa-psk
psk=xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
[ipv4]
method=manual
address1=192.168.1.203/24
gateway=192.168.1.1
dns=8.8.8.8,8.8.4.4
[ipv6]
addr-gen-mode=default
method=auto

[Tim Curtis]

Try setting Primary DNS to your gateway address 192.168.1.1. Thats a typical config for a residential Router that proxies DNS requests.

[ECELO]

Try setting Primary DNS to your gateway address 192.168.1.1. Thats a typical config for a residential Router that proxies DNS requests.

Yesss, now web radios also work! But what has changed compared to 8.3.9? I always entered Google DNS 8.8.8.8 and 8.8.4.4 and it worked without any problems. Anyway, thanks for the support (and patience..)!