[SOLVED] WiFi and SSH

[hurcheon]

Hi there, first the SSH, as some of the forum posts involve doing things on the RPi side

The RPi is a 4B 4GB, has a 64GB card in it, an IQAudio DAC and is in a case with a touchscreen.

• Wired, it works
  
• the WiFi does not
  

I tried the SSH option on the RPI, but neither  pi/moodeaudio or my own uid/password, no joy

The basic issue is that the WiFi, though set, does not work. 

• I have increased the timeout to 180 seconds on the configuration page
  
• I have rebooted the router
  
• With no access to the terminal, I can't get other diagnostics or settings 
  

Any help on the SSH, and how to get the WiFi working?


Some of the log

Code:

20231130 012905 worker: -- Audio debug
20231130 012905 worker: --
20231130 012905 worker: ALSA cards: (0:Headphones | 1:IQaudIODAC | 2:empty | 3:empty
20231130 012905 worker: MPD config: (1:IQaudIODAC | mixer:(Analogue) | card:1)
20231130 012905 worker: ALSA mixer actual (Analogue)
20231130 012905 worker: ALSA Analogue volume set to (0%)

Code:

20231130 012905 worker: --
20231130 012905 worker: -- System
20231130 012905 worker: --
20231130 012907 worker: Host      (moodehost)
20231130 012907 worker: Hardware  (Pi-4B 1.5 4GB)
20231130 012907 worker: moOde     (8.3.6 2023-09-05)
20231130 012907 worker: RaspiOS   (11.7)
20231130 012907 worker: Kernel    (6.1.21-v8+ #1642)
20231130 012907 worker: Procarch  (aarch64, 64-bit)
20231130 012907 worker: MPD ver   (0.23.12)
20231130 012907 worker: CPU gov   (ondemand)
20231130 012907 worker: Userid    (XXXXXX)
20231130 012907 worker: Homedir   (/home/XXXXXX)
20231130 012907 worker: Timezone  (Europe/London)
20231130 012907 worker: Keyboard  (gb)
20231130 012907 worker: USB boot  (enabled)
20231130 012907 worker: File sys  (expanded)
20231130 012907 worker: HDMI port (On)
20231130 012907 worker: Sys LED0  (On)
20231130 012907 worker: Sys LED1  (On)
20231130 012907 worker: --

Code:

20231130 012907 worker: -- Network
20231130 012907 worker: --
20231130 012907 worker: eth0 adapter exists
20231130 012907 worker: eth0 address check (Off)
20231130 012907 worker: eth0 address not assigned
20231130 012907 worker: wlan0 adapter exists
20231130 012907 worker: wlan0 country (GB)
20231130 012907 worker: wlan0 configured SSID (XXXXXX)
20231130 012907 worker: wlan0 SSID alternates (None)
20231130 012907 worker: wlan0 router mode (Off)
20231130 012907 worker: wlan0 address check (up to 120 secs)
20231130 013110 worker: wlan0 address not assigned
20231130 013110 worker: wlan0 activating AP mode
20231130 013142 worker: wlan0 address check (up to 120 secs)
20231130 013149 worker: wlan0 AP mode activated (SSID XXXXXX)
20231130 013149 worker: wlan0 power save (Disabled)
20231130 013149 worker: IP addr (172.24.1.1)
20231130 013149 worker: Netmask (255.255.255.0)
20231130 013149 worker: Gateway (0.0.0.0)
20231130 013149 worker: Pri DNS (127.0.0.1)
20231130 013149 worker: Domain  ()

[DRONE7]

Did you use the RPI imager and set the wifi address? and username/password ?

see the setup guide...
https://github.com/moode-player/moode/bl.../setup.txt

SECURITY AND OPERATING SYSTEM (OS) IMAGE

For improved security the OS image does not contain the userid pi, SSH service,
WiFi SSID or Access Point password.

- Use the official Raspberry Pi Imager to choose a moOde OS image, enable SSH,
  create a userid and password and optionally a WiFi SSID and password.

  *** READ THIS ***
  1. SSH and userid/password are REQUIRED for correct operation of moOde.
  2. Do not set the host name using the Imager. Refer to CUSTOM CONFIGURATIONS
     in this guide for information on changing the host name.

- An Access Point password can be set using the Network Configuration screen
  after accessing the moOde WebUI, or before first boot via a moodecfg.ini
  file as described in the CUSTOM CONFIGURATIONS section.

- The moOde OS images are listed in the "Media Player OS" category of the Pi
  Imager, or if they were downloaded directly via the Download page at
  http://moodeaudio.org they can be selected via the "Use custom" category.

- Refer to the links below for more information on operating system security
  and how to download and use the Raspberry Pi Imager.
  https://www.raspberrypi.com/software/
  https://www.raspberrypi.com/news/raspber...pril-2022/

To access the OS command console use Secure Shell (SSH). An easy to use WebSSH
terminal is available in the WebUI, System Config screen.

[TheOldPresbyope]

@hurcheon 

Concerning the default user account and SSH, see @DRONE7's response. It covers setting up WiFi too.

Nevertheless, concerning the WiFi information you posted

Code:

20231130 012907 worker: -- Network
20231130 012907 worker: --
20231130 012907 worker: eth0 adapter exists
20231130 012907 worker: eth0 address check (Off)
20231130 012907 worker: eth0 address not assigned
...

Okay, so the Ethernet port is enabled but there's no Ethernet connection. Moving on

Code:

20231130 012907 worker: wlan0 adapter exists
20231130 012907 worker: wlan0 country (GB)
20231130 012907 worker: wlan0 configured SSID (XXXXXX)
20231130 012907 worker: wlan0 SSID alternates (None)
20231130 012907 worker: wlan0 router mode (Off)
20231130 012907 worker: wlan0 address check (up to 120 secs)
20231130 013110 worker: wlan0 address not assigned
20231130 013110 worker: wlan0 activating AP mode
20231130 013142 worker: wlan0 address check (up to 120 secs)
...

Okay, so the WiFi adapter is live, and moOde (the underlying Linux actually) has tried for two minutes to associate with your LAN's AP with SSID XXXXX and whatever password you gave it, and failed.

Finally,

Code:

20231130 013149 worker: wlan0 AP mode activated (SSID XXXXXX)
20231130 013149 worker: wlan0 power save (Disabled)
20231130 013149 worker: IP addr (172.24.1.1)
20231130 013149 worker: Netmask (255.255.255.0)
20231130 013149 worker: Gateway (0.0.0.0)
20231130 013149 worker: Pri DNS (127.0.0.1)
20231130 013149 worker: Domain  ()

Okay, so moOde has activated its own AP mode. The AP will have the SSID you assigned in the Network configuration. It will associate with WiFi clients if they present the correct credentials and assign them an address in the 172.24.1.x range, and the moOde WebUI will be accessible at 172.24.1.1 with the hostname assigned in the moOde configuration. The AP does not provide DNS service so you have to access it by IP address or by the mDNS artfice hostname.local

As an aside, generally it's not helpful to post only selected and redacted portions of the startup log when you're seeking assistance.

Regards,
Kent

[hurcheon]

Did you use the RPI imager and set the wifi address? and username/password ?

Cheers

hopefully it is as simple as that. My fault for using a "how to make a music device" guide elsewhere on the internet

I am about to follow your advice to flash a card. If this does it then I will mark this as solved

EDIT: And, of course, this is where I find out my linux laptop can't run Pi imager, as the version of Mint is too old to have the new version of libc6, Not a job for today, but a job for Christmas time, rebuild that

[hurcheon]

@hurcheon 


As an aside, generally it's not helpful to post only selected and redacted portions of the startup log when you're seeking assistance.

Regards,
Kent

Hi Kent

Thanks, point taken, will bear that in mind for the future

[hurcheon]

Did you use the RPI imager and set the wifi address? and username/password ?

Hi

This done now, WiFi is working, though the moode.local name is not found on the network

So I can get there by IP address, but not the URL

Any thoughts on how to improve pickup of the alias?

I suspect I might have to figure out how to put a static IP on this, just in case

[TheOldPresbyope]

Did you use the RPI imager and set the wifi address? and username/password ?

Hi

This done now, WiFi is working, though the moode.local name is not found on the network

So I can get there by IP address, but not the URL

Any thoughts on how to improve pickup of the alias?

I suspect I might have to figure out how to put a static IP on this, just in case

The fully qualified domain name hostname.local is just vanilla multicast DNS aka mDNS.

Possible reasons it might not be found on your LAN

• you changed the hostname to something besides moode. The fix is obvious
  
• your AP is blocking the multicast packets. That's unlikely but it would be on you to figure out and fix.
  
• you're trying to find the player using a web browser on an older Android device. Google fixed that problem some releases ago but unless you upgrade to recent Android you're stuck with using the IP address.
  
• ?
  

None of my end-user devices---Google Pixel 6a phone, Apple iPhone SE, Apple iPad, Linux Minx laptop, my partner's Windows 10 laptop--- have any trouble discovering my various moOde players using mDNS.

Regards,
Kent

[hurcheon]

Did you use the RPI imager and set the wifi address? and username/password ?

Hi

This done now, WiFi is working, though the moode.local name is not found on the network

So I can get there by IP address, but not the URL

Any thoughts on how to improve pickup of the alias?

I suspect I might have to figure out how to put a static IP on this, just in case

The fully qualified domain name hostname.local is just vanilla multicast DNS aka mDNS.

Possible reasons it might not be found on your LAN

• you changed the hostname to something besides moode. The fix is obvious
  
• your AP is blocking the multicast packets. That's unlikely but it would be on you to figure out and fix.
  
• you're trying to find the player using a web browser on an older Android device. Google fixed that problem some releases ago but unless you upgrade to recent Android you're stuck with using the IP address.
  
• ?
  

None of my end-user devices---Google Pixel 6a phone, Apple iPhone SE, Apple iPad, Linux Minx laptop, my partner's Windows 10 laptop--- have any trouble discovering my various moOde players using mDNS.

Regards,
Kent

I have been trying

Chrome and Firefox on Windows 10 - Both Chrome and Firefox connects by  IP, not by alias 
Chromium and Firefox on Linux Mint 20 - both work by the alias
Chrome, DuckDuckGo and Firefox on Android 14 - Google Pixel 6 PRO - Chrome /DuckduckGo/Firefox IP only
Chrome and Safari on iPad - Chrome doesn't connect with either, iPad takes the alias and IP

[TheOldPresbyope]

Sorry, I don't see any evidence of a problem with moOde and its underlying RPiOS.There's plenty of information available about mDNS and its implementation in various OSes.

Regards,
Kent

[hurcheon]

Sorry, I don't see any evidence of a problem with moOde and its underlying RPiOS.There's plenty of information available about mDNS and its implementation in various OSes.

Regards,
Kent

I agree,  by this stage the lack of machines resolving to the hostname is definitely a problem at THIS side, as some devices connect

Thank you for your help