Moode Forum
Wifi problems - Printable Version

+- Moode Forum (https://moodeaudio.org/forum)
+-- Forum: moOde audio player (https://moodeaudio.org/forum/forumdisplay.php?fid=3)
+--- Forum: Support (https://moodeaudio.org/forum/forumdisplay.php?fid=7)
+--- Thread: Wifi problems (/showthread.php?tid=7797)

Pages: 1 2 3 4

Wifi problems - andyjohnson - 06-08-2025

Hi,

This is my first post here. I've been using moode audio on ethernet for about a year, but now need to use wifi. I'm having some problems and hoping someone can help me.

Set-up is Raspberry Pi 4 Model B 2GB and a HifiBerry Amp2, with music on a local usb drive. I've downloaded 2025-05-13-moode-r934-arm64-lite.img and written it to an sd card, configuring it for my wifi hub per the instructions. When I boot the pi with ethernet disconnected I am unable to access the device, and it doesn't appear to connect to the wifi hub. Connecting the ethernet cable gives me web access, and downloading the startup log gives me:


Code:
20250513 130129 worker: --
20250513 130129 worker: -- Network
20250513 130129 worker: --
20250513 130129 worker: WiFi SSID/PSK imported
20250513 130129 worker: Eth0
20250513 130129 worker: Ethernet: adapter exists
20250513 130129 worker: Ethernet: timeout off
20250513 130129 worker: Ethernet: address not assigned
20250513 130129 worker: Wlan0
20250513 130129 worker: Wireless: adapter exists
20250513 130129 worker: Wireless: country GB
20250513 130129 worker: Wireless: SSID    Polygon
20250513 130129 worker: Wireless: other   None
20250513 130129 worker: Wireless: timeout up to 90 secs
20250513 130301 worker: Wireless: address not assigned
20250513 130301 worker: Wireless: Hotspot activating
20250513 130301 worker: Wireless: timeout up to 90 secs
20250513 130433 worker: Wireless: address not assigned
20250513 130433 worker: No active network interface
20250513 130433 worker: mDNS
20250513 130433 worker: Discover: IPv4 and IPv6


Clicking Configure -> Network shows the correct SSID ("Polygon") and WPA-PSK security, which is what I configured, Access method is DHCP, but underneath that box is says "Not in use" -- I don't know, but I suspect that this is because I subsequently connected the ethernet cable. I have multiple devices attached to the "Polygon" wifi hub that use DHCP.

I've tried configuring it (in the image writer) for a different wifi hub (my main router) and get the same outcome.

I'm unsure how to proceed from here, and am hoping that someone can suggest ways to troubleshoot this problem.

Thanks!

RE: Wifi problems - Tim Curtis - 06-08-2025

The log shows no IP address was assigned by after waiting 90 seconds.

Code:
20250513 130129 worker: Wireless: SSID    Polygon
20250513 130129 worker: Wireless: other   None
20250513 130129 worker: Wireless: timeout up to 90 secs
20250513 130301 worker: Wireless: address not assigned


To troubleshoot check the WiFi log on the Polygon device to see whether it was the association that failed or the DHCP request.

RE: Wifi problems - TheOldPresbyope - 06-08-2025

@andyjohnson

Occasionally I've had problems with predefining the WiFi connection in an image. Never figured out why (never discount fat-finger typing), but since you can connect via Ethernet, why not just do the job from the Network Configuration panel? It's always worked for me.

m>Configure>Network

Scroll down to the Wireless section, choose DHCP for the Address method, click the Network SSID SCAN button, choose your AP (Polygon) from the resulting list, enter the Password, make sure the Security and Country choices are correct. Save the Wireless settings and reboot. You can disconnect the Ethernet cable while the system is rebooting. 

Should be good to go. If not, you can always plug the Ethernet cable in again and go bug hunting.

Regards,
Kent

RE: Wifi problems - andyjohnson - 06-08-2025

(06-08-2025, 01:37 PM)Tim Curtis Wrote: The log shows no IP address was assigned by after waiting 90 seconds.

Code:
20250513 130129 worker: Wireless: SSID    Polygon
20250513 130129 worker: Wireless: other   None
20250513 130129 worker: Wireless: timeout up to 90 secs
20250513 130301 worker: Wireless: address not assigned


To troubleshoot check the WiFi log on the Polygon device to see whether it was the association that failed or the DHCP request.

Hi. Thanks for replying!

Unfortunately neither wifi device provide any useful logging. But I can see that the RasPi isn't being shown in the Polygon hub's list of connected devices, so it seems like its failing to even associate. It has multiple other connected devices, as does the other router, and since the RasPi fails to connected to either I'm thinking the problem is on the RasPi itself. Are there any other more detailed logs that I could check, or anything else that you'd recommend?

RE: Wifi problems - andyjohnson - 06-08-2025

(06-08-2025, 06:31 PM)TheOldPresbyope Wrote: @andyjohnson

Occasionally I've had problems with predefining the WiFi connection in an image. Never figured out why (never discount fat-finger typing), but since you can connect via Ethernet, why not just do the job from the Network Configuration panel? It's always worked for me.

m>Configure>Network

Scroll down to the Wireless section, choose DHCP for the Address method, click the Network SSID SCAN button, choose your AP (Polygon) from the resulting list, enter the Password, make sure the Security and Country choices are correct. Save the Wireless settings and reboot. You can disconnect the Ethernet cable while the system is rebooting. 

Should be good to go. If not, you can always plug the Ethernet cable in again and go bug hunting.

Regards,
Kent

Hi. Thanks for replying!

I should have mentioned that I tried changing the network configuration using the web UI, but unfortunately it made no difference.

The scan button does find the "Polygon" hub's SSID, along with others, and I've verified that the access password I'm using is correct.But after a reboot it doesn't connect.

If you can think of anything else that I could try then I'd be grateful for any suggestions.

RE: Wifi problems - Tim Curtis - 06-08-2025

(06-08-2025, 09:17 PM)andyjohnson Wrote:
(06-08-2025, 01:37 PM)Tim Curtis Wrote: The log shows no IP address was assigned by after waiting 90 seconds.

Code:
20250513 130129 worker: Wireless: SSID    Polygon
20250513 130129 worker: Wireless: other   None
20250513 130129 worker: Wireless: timeout up to 90 secs
20250513 130301 worker: Wireless: address not assigned


To troubleshoot check the WiFi log on the Polygon device to see whether it was the association that failed or the DHCP request.

Hi. Thanks for replying!

Unfortunately neither wifi device provide any useful logging. But I can see that the RasPi isn't being shown in the Polygon hub's list of connected devices, so it seems like its failing to even associate. It has multiple other connected devices, as does the other router, and since the RasPi fails to connected to either I'm thinking the problem is on the RasPi itself. Are there any other more detailed logs that I could check, or anything else that you'd recommend?

What make and model are the routers?

RE: Wifi problems - DRONE7 - 06-08-2025

Any special characters in your ssid or password ?

RE: Wifi problems - TheOldPresbyope - 06-08-2025

@andyjohnson

Random thought - Does your passphrase contain any special characters?

You can check your system log to see the progress of the wlan0 interface as it tries to associate with your access point. Reboot, ssh into it, and run the following command

Code:
journalctl -b -g wlan0

The -b option means examine only the most recent boot info; the -g option means grep on the following string.

In my case of a successful association, I see 50 lines of wlan-related output (follows my signature). You can read them at your leisure. Do you see notable differences in your case? In particular, what happens with key negotiation?

Regards,
Kent

- sorry, the lines wrap.

Code:
Jun 08 14:19:18 moodey NetworkManager[675]: <info>  [1749406758.9554] device (wlan0): driver supports Access Point (AP) mode
Jun 08 14:19:18 moodey NetworkManager[675]: <info>  [1749406758.9560] manager: (wlan0): new 802.11 Wi-Fi device (/org/freedesktop/NetworkManager/Devices/3)
Jun 08 14:19:18 moodey NetworkManager[675]: <info>  [1749406758.9562] device (wlan0): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'externa
l')
Jun 08 14:19:19 moodey NetworkManager[675]: <info>  [1749406759.2886] device (wlan0): supplicant interface state: internal-starting -> disconnected
Jun 08 14:19:19 moodey NetworkManager[675]: <info>  [1749406759.2886] Wi-Fi P2P device controlled by interface wlan0 created
Jun 08 14:19:19 moodey NetworkManager[675]: <info>  [1749406759.2889] manager: (p2p-dev-wlan0): new 802.11 Wi-Fi P2P device (/org/freedesktop/NetworkManager/Devices/4)
Jun 08 14:19:19 moodey NetworkManager[675]: <info>  [1749406759.2891] device (p2p-dev-wlan0): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state:
'external')
Jun 08 14:19:19 moodey NetworkManager[675]: <info>  [1749406759.2894] device (wlan0): state change: unavailable -> disconnected (reason 'supplicant-available', sys-iface
-state: 'managed')
Jun 08 14:19:19 moodey NetworkManager[675]: <info>  [1749406759.2898] device (p2p-dev-wlan0): state change: unavailable -> disconnected (reason 'none', sys-iface-state:
'managed')
Jun 08 14:19:22 moodey NetworkManager[675]: <info>  [1749406762.1096] device (wlan0): Activation: starting connection 'Krypton5' (0a02d0d7-96e2-4925-8582-979d310419a7)
Jun 08 14:19:22 moodey NetworkManager[675]: <info>  [1749406762.1097] device (wlan0): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed')
Jun 08 14:19:22 moodey NetworkManager[675]: <info>  [1749406762.1100] device (wlan0): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
Jun 08 14:19:22 moodey NetworkManager[675]: <info>  [1749406762.1103] device (wlan0): Activation: (wifi) access point 'Krypton5' has security, but secrets are required.
Jun 08 14:19:22 moodey NetworkManager[675]: <info>  [1749406762.1103] device (wlan0): state change: config -> need-auth (reason 'none', sys-iface-state: 'managed')
Jun 08 14:19:22 moodey NetworkManager[675]: <info>  [1749406762.1104] sup-iface[beedd27ca10fc896,0,wlan0]: wps: type pbc start...
Jun 08 14:19:22 moodey NetworkManager[675]: <info>  [1749406762.1110] device (wlan0): state change: need-auth -> prepare (reason 'none', sys-iface-state: 'managed')
Jun 08 14:19:22 moodey NetworkManager[675]: <info>  [1749406762.1112] device (wlan0): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
Jun 08 14:19:22 moodey NetworkManager[675]: <info>  [1749406762.1113] device (wlan0): Activation: (wifi) connection 'Krypton5' has security, and secrets exist.  No new s
ecrets needed.
Jun 08 14:19:22 moodey wpa_supplicant[677]: wlan0: WPS-CANCEL
Jun 08 14:19:22 moodey wpa_supplicant[677]: wlan0: Trying to associate with a8:70:5d:49:74:ba (SSID='Krypton5' freq=5785 MHz)
Jun 08 14:19:22 moodey NetworkManager[675]: <info>  [1749406762.1194] device (wlan0): supplicant interface state: disconnected -> associating
Jun 08 14:19:22 moodey NetworkManager[675]: <info>  [1749406762.1194] device (p2p-dev-wlan0): supplicant management interface state: disconnected -> associating
Jun 08 14:19:22 moodey wpa_supplicant[677]: wlan0: Associated with a8:70:5d:49:74:ba
Jun 08 14:19:22 moodey wpa_supplicant[677]: wlan0: CTRL-EVENT-SUBNET-STATUS-UPDATE status=0
Jun 08 14:19:22 moodey wpa_supplicant[677]: wlan0: CTRL-EVENT-REGDOM-CHANGE init=COUNTRY_IE type=COUNTRY alpha2=US
Jun 08 14:19:22 moodey NetworkManager[675]: <info>  [1749406762.2518] device (wlan0): supplicant interface state: associating -> 4way_handshake
Jun 08 14:19:22 moodey NetworkManager[675]: <info>  [1749406762.2519] device (p2p-dev-wlan0): supplicant management interface state: associating -> 4way_handshake
Jun 08 14:19:22 moodey wpa_supplicant[677]: wlan0: WPA: Key negotiation completed with a8:70:5d:49:74:ba [PTK=CCMP GTK=CCMP]
Jun 08 14:19:22 moodey wpa_supplicant[677]: wlan0: CTRL-EVENT-CONNECTED - Connection to a8:70:5d:49:74:ba completed [id=0 id_str=]
Jun 08 14:19:22 moodey NetworkManager[675]: <info>  [1749406762.2593] device (wlan0): supplicant interface state: 4way_handshake -> completed
Jun 08 14:19:22 moodey NetworkManager[675]: <info>  [1749406762.2593] device (wlan0): Activation: (wifi) Stage 2 of 5 (Device Configure) successful. Connected to wireles
s network "Krypton5"
Jun 08 14:19:22 moodey NetworkManager[675]: <info>  [1749406762.2593] device (p2p-dev-wlan0): supplicant management interface state: 4way_handshake -> completed
Jun 08 14:19:22 moodey NetworkManager[675]: <info>  [1749406762.2594] device (wlan0): state change: config -> ip-config (reason 'none', sys-iface-state: 'managed')
Jun 08 14:19:22 moodey NetworkManager[675]: <info>  [1749406762.2598] dhcp4 (wlan0): activation: beginning transaction (timeout in 45 seconds)
Jun 08 14:19:22 moodey avahi-daemon[559]: Registering new address record for fe80::d8dd:a3b0:f03:b9d on wlan0.*.
Jun 08 14:19:23 moodey NetworkManager[675]: <info>  [1749406763.7806] dhcp6 (wlan0): activation: beginning transaction (timeout in 45 seconds)
Jun 08 14:19:23 moodey NetworkManager[675]: <info>  [1749406763.7810] policy: set 'Krypton5' (wlan0) as default for IPv6 routing and DNS
Jun 08 14:19:23 moodey avahi-daemon[559]: Registering new address record for 2601:147:4380:e0d0:47bc:fd49:ad88:bec2 on wlan0.*.
Jun 08 14:19:23 moodey avahi-daemon[559]: Withdrawing address record for fe80::d8dd:a3b0:f03:b9d on wlan0.
Jun 08 14:19:23 moodey NetworkManager[675]: <info>  [1749406763.7940] dhcp6 (wlan0): state changed new lease, address=2601:147:4380:e0d0::7fb5
Jun 08 14:19:23 moodey avahi-daemon[559]: Registering new address record for 2601:147:4380:e0d0::7fb5 on wlan0.*.
Jun 08 14:19:24 moodey NetworkManager[675]: <info>  [1749406764.2832] dhcp4 (wlan0): state changed new lease, address=10.0.0.241
Jun 08 14:19:24 moodey NetworkManager[675]: <info>  [1749406764.2835] policy: set 'Krypton5' (wlan0) as default for IPv4 routing and DNS
Jun 08 14:19:24 moodey avahi-daemon[559]: Joining mDNS multicast group on interface wlan0.IPv4 with address 10.0.0.241.
Jun 08 14:19:24 moodey avahi-daemon[559]: New relevant interface wlan0.IPv4 for mDNS.
Jun 08 14:19:24 moodey avahi-daemon[559]: Registering new address record for 10.0.0.241 on wlan0.IPv4.
Jun 08 14:19:24 moodey NetworkManager[675]: <info>  [1749406764.2974] device (wlan0): state change: ip-config -> ip-check (reason 'none', sys-iface-state: 'managed')
Jun 08 14:19:24 moodey NetworkManager[675]: <info>  [1749406764.2993] device (wlan0): state change: ip-check -> secondaries (reason 'none', sys-iface-state: 'managed')
Jun 08 14:19:24 moodey NetworkManager[675]: <info>  [1749406764.2994] device (wlan0): state change: secondaries -> activated (reason 'none', sys-iface-state: 'managed')
Jun 08 14:19:24 moodey NetworkManager[675]: <info>  [1749406764.3012] device (wlan0): Activation: successful, device activated.


RE: Wifi problems - TheOldPresbyope - 06-08-2025

...and bob beat me to the question Tongue

RE: Wifi problems - andyjohnson - 06-09-2025

[quote pid='64465' dateline='1749420883']
What make and model are the routers?
[/quote]

"Polygon" is a Devolo dLAN 550 wifi hub. It uses poweline networking to connect to a port on my main domestic router (the other wifi device I tried) which is a Technicolor DGA0122 supplied by my internet provider.


The Devolo device is currently providing wifi to a couple of laptops, four phones/tablets, and a few iot devices. I've never had a problem with it.