+- 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 connection problems (/showthread.php?tid=1827)
wifi connection problems - lurkio - 10-18-2019
Hi All
I'm having problems with wifi connection on a new image of 6.3 on a Rpi 3
all seems fine over ethernet
access mode allows me to get to the network settings where a scan finds my SSID - I enter password save and reboot
but no Rpi on the network - it is as if the settings are not remembered
sometimes it restarts in access mode, sometimes not
tried two different SD Cards and tried adding the info over ethernet - no joy
not sure where to go from here
Lx
RE: wifi connection problems - Tim Curtis - 10-19-2019
Try the command below with your SSID and password. It should generate output similar to below.
Code:
pi@rp3:~ $ sudo wpa_passphrase "MySSID" "MyPassword"
network={
ssid="MySSID"
#psk="MyPassword"
psk=a66e97b9a1008a97285c78c2b95082bed3541d3dd01165b0128f7f3c18563797
}RE: wifi connection problems - lurkio - 10-19-2019
(10-19-2019, 02:35 AM)Tim Curtis Wrote: Try the command below with your SSID and password. It should generate output similar to below.
Code:pi@rp3:~ $ sudo wpa_passphrase "MySSID" "MyPassword"
network={
ssid="MySSID"
#psk="MyPassword"
psk=a66e97b9a1008a97285c78c2b95082bed3541d3dd01165b0128f7f3c18563797
}
Hi Tim - Tx for the help
I connected by ethernet and got similar output to above - so it must mean that at least the details are stored but it is not connecting to the network for some reason ?
if I disconnect ethernet and restart it goes back into access mode
Lx
RE: wifi connection problems - TheOldPresbyope - 10-19-2019
@lurkio
Are you sure you've entered the WiFi client SSID/password credentials? What you are describing sounds suspiciously like they were entered but not correctly.
I just did a test with moOde 6.3.0 running on an RPi4B. Everything was working perfectly---ethernet, WiFi AP mode, and WiFi client mode. While in WiFi client mode, I deliberately altered the WiFi client password, saved it, and rebooted (with ethernet disconnected).
After a very long time, the moOde AP became visible in my WiFi scanner. I associated my laptop with it and then ssh'ed into 172.24.1.1.
Here's an annotated version of what I see in the moOde log:
Code:
pi@moode:~ $ moodeutl -l
...
20191019 150324 worker: -- Network
20191019 150324 worker: eth0 exists # the ethernet interface is enabled
20191019 150324 worker: eth0 wait 0 for IP address # assume ethernet is live and try to
20191019 150328 worker: eth0 wait 1 for IP address # interact with DHCP service
20191019 150331 worker: eth0 wait 2 for IP address
20191019 150334 worker: eth0 wait 3 for IP address
20191019 150337 worker: eth0 wait 4 for IP address
20191019 150340 worker: eth0 address not assigned # OK, so maybe not plugged into ethernet
20191019 150340 worker: wlan0 exists # the WiFi interface is enabled so try it
20191019 150340 worker: wifi country (US)
20191019 150340 worker: wlan0 trying SSID (REDACTED) # I gave it an SSID so try it in client mode
20191019 150340 worker: wlan0 wait 0 for IP address # waiting for handshake with the AP
20191019 150343 worker: wlan0 wait 1 for IP address
20191019 150346 worker: wlan0 wait 2 for IP address
20191019 150350 worker: wlan0 wait 3 for IP address
20191019 150353 worker: wlan0 wait 4 for IP address
20191019 150356 worker: wlan0 no IP addr for SSID (REDACTED) # PW was incorrect so no IP issued by AP
20191019 150356 worker: wlan0 AP mode started # and so we revert to AP mode
20191019 150430 worker: wlan0 wait 0 for IP address
20191019 150433 worker: wlan0 wait 1 for IP address
20191019 150436 worker: wlan0 (172.24.1.1) # the static IP assigned to the AP by Tim
...Now for the tricky business. In your case, while moOde is running in AP mode, plug the ethernet back in. The player will now be accessible via two different IP addresses: 172.24.1.1 on the WiFi network, and xxx.xxx.xxx.xxx on the wired LAN (192.168.1.xxx in my case). Log in from the wired LAN and run moodeutl -l and see if you have similar output.
Regards,
Kent
RE: wifi connection problems - lurkio - 10-20-2019
Quote:.....Now for the tricky business. In your case, while moOde is running in AP mode, plug the ethernet back in. The player will now be accessible via two different IP addresses: 172.24.1.1 on the WiFi network, and xxx.xxx.xxx.xxx on the wired LAN (192.168.1.xxx in my case). Log in from the wired LAN and run moodeutl -l and see if you have similar output.
Regards,
Kent
Hi Kent - yes I get pretty much what you posted above - it seems that it is not able to validate my wifi password
The password is definitely right - I have rechecked and logged in on different devices - all fine
could password strength criteria make this fail ? (my password is just numbers and lowercase) or could the PSK coding somehow fail ?
Code:
20191020 170432 worker: -- Start
20191020 170432 worker: Successfully daemonized
20191020 170432 worker: Integrity check (passed)
20191020 170432 worker: Session loaded
20191020 170432 worker: Debug logging (off)
20191020 170432 worker: ALSA volume set to (0%)
20191020 170432 worker: -- System
20191020 170434 worker: Host name (moode)
20191020 170434 worker: moOde release (6.3.0 2019-10-02)
20191020 170434 worker: Raspbian OS (10.1)
20191020 170434 worker: Linux kernel (4.19.75-v7+ #1270)
20191020 170434 worker: Platform (Pi-3B 1GB v1.2)
20191020 170434 worker: Architecture (armv7l)
20191020 170434 worker: MPD version (0.20.23)
20191020 170434 worker: CPU governor (ondemand)
20191020 170434 worker: USB boot not enabled yet
20191020 170434 worker: File system not expanded yet
20191020 170434 worker: HDMI port on
20191020 170435 worker: File check (OK)
20191020 170435 worker: -- Network
20191020 170435 worker: eth0 exists
20191020 170435 worker: eth0 wait 0 for IP address
20191020 170438 worker: eth0 wait 1 for IP address
20191020 170441 worker: eth0 wait 2 for IP address
20191020 170444 worker: eth0 wait 3 for IP address
20191020 170447 worker: eth0 wait 4 for IP address
20191020 170450 worker: eth0 address not assigned
20191020 170451 worker: wlan0 exists
20191020 170451 worker: wifi country (GB)
20191020 170451 worker: wlan0 trying SSID (XXXXXXXXXXXX)
20191020 170451 worker: wlan0 wait 0 for IP address
20191020 170454 worker: wlan0 wait 1 for IP address
20191020 170506 worker: wlan0 wait 2 for IP address
20191020 170509 worker: wlan0 wait 3 for IP address
20191020 170512 worker: wlan0 wait 4 for IP address
20191020 170515 worker: wlan0 no IP addr for SSID (XXXXXXXXXXXX)
20191020 170515 worker: wlan0 AP mode started
20191020 170548 worker: wlan0 wait 0 for IP address
20191020 170552 worker: wlan0 wait 1 for IP address
20191020 170555 worker: wlan0 (172.24.1.1)
20191020 170555 worker: -- Audio
20191020 170555 worker: ALSA outputs unmuted
20191020 170555 worker: ALSA card number (0)
20191020 170555 worker: Audio output (I2S audio device)
20191020 170555 worker: Audio device (Allo Piano 2.1 Hi-Fi DAC) ......RE: wifi connection problems - Tim Curtis - 10-20-2019
Maybe there is some breakage in your image.
Examine the file below and verify that your SSID and PSK are present and that the PSK is same as the PSK generated by the wpa_passphrase command.
Code:
sudo cat /etc/wpa_supplicant/wpa_supplicant.conf-Tim
RE: wifi connection problems - TheOldPresbyope - 10-20-2019
Could this be another case where a special character in the password is causing a problem with the script which deals with it?
RE: wifi connection problems - lurkio - 10-20-2019
(10-20-2019, 04:52 PM)TheOldPresbyope Wrote: Could this be another case where a special character in the password is causing a problem with the script which deals with it?
no special characters in the password
I just downloaded and burned another SD card - no joy - I did notice that the wifi briefly connected ( showed up on fing anyway)
The pi was previously running Libreelec on wifi so I know that it works
RE: wifi connection problems - lurkio - 10-20-2019
(10-20-2019, 04:26 PM)Tim Curtis Wrote: Maybe there is some breakage in your image.
Examine the file below and verify that your SSID and PSK are present and that the PSK is same as the PSK generated by the wpa_passphrase command.
Code:sudo cat /etc/wpa_supplicant/wpa_supplicant.conf
-Tim
Hi Tim - ok I ran the command, SSID and PSK are present
how do i check it is the same as the PSK generated by the wpa_passphrase command ?
sorry found it above - yes it is the same
Lx
RE: wifi connection problems - Tim Curtis - 10-20-2019
You reported that it briefly connected which suggests some sort of network issue. Maybe try rebooting your Router.
Once moOde successfully configures the wpa_supplicant file, it's Linux that handles the network connection during reboot.