Thank you for your donation!


Cloudsmith graciously provides open-source package management and distribution for our project.


Solved: Raspberry always goes to AP Mode...
#11
(08-14-2023, 05:58 PM)yannig Wrote:
(08-12-2023, 04:52 PM)Tim Curtis Wrote: The log shows a configured and alternate SSID and that after waiting for 90 seconds for Linux to connect to either SSID that no IP address was received from your Router.

20230812 174011 worker: wlan0 configured SSID (Tenda-917B00)
20230812 174011 worker: wlan0 SSID alternates (Tenda-917B00-5G)
20230812 174011 worker: wlan0 router mode (Off)
20230812 174011 worker: wlan0 address check (up to 90 secs)
20230812 174143 worker: wlan0 address not assigned
20230812 174143 worker: wlan0 activating AP mode

This could be caused by one of the following:

1. Router DHCP (IP address assignment) is responding extremely slowly. Normally this happens almost instantly.
Try rebooting your Router.
Try increasing the "Address timeout" setting to max of 120 seconds. The setting is in System config.

2. Linux can't connect to configured SSID "Tenda-917B00" for some reason and thus falls back to the alternate SSID "Tenda-917B00-5G" but also can't connect to this SSID.
Open Network config
- Click MANAGE Saved networks and delete the SSID "Tenda-917B00-5G"
- Enter manually the SSID and password for the alternate SSID "Tenda-917B00-5G"
- Enter manually the SSID and password for the configured SSID "Tenda-917B00"

You can look at the wpa_supplicant file to verify that it contains just  the two SSID's you defined above. The configured SSID will be listed having priority 100 and the alternate SSID will have priority 10.

Code:
sudo cat /etc/wpa_supplicant/wpa_supplicant.conf

If all looks good go ahead and reboot.

If Linux is still not able to get an IP address for either SSID then its not obvious to me what might be happening.

Hello Tim

thanks for your response
I tried everything above, but this strange problem is still there.

And I still don't have any problem to connect other devices (than rasberries/moode), ie android, macbookpro, etc.

Code:
pi@moode-l:~ $ sudo cat /etc/wpa_supplicant/wpa_supplicant.conf
#########################################
# This file is automatically generated by
# the player Network configuration page.
#########################################

country=FR
ctrl_interface=DIR=/var/run/wpa_supplicant GROUP=netdev
update_config=1

network={
ssid="Tenda-917B00"
priority=100
scan_ssid=1
psk=a3b13ba98f6d03b9d222e3bb78e7c2d887fd51eac92a357f5dcdd4f35a77ab63

Additional troubleshooting can be done by examining your WiFi Router wireless and DHCP logs for errors associated with the host "moode-l" or its WLAN MAC address.

The MAC address can be viewed via:
moodeutl -s | grep "WLAN MAC"

When a client attempts to connect to a WiFI LAN two steps are performed:
1. Client associates (is granted access) to the WiFi LAN provided by the Router. This is the step where the client WiFi password is checked by the Router to see if it matches the one defined for the SSID.
2. Router DHCP service delivers an IP address to the client. This is the step where the client receives an IP address so it can communicate with other clients on the WiFI LAN.

Both 1 and 2 must be successful for a client to be able to use the wireless LAN.

Failure to associate is typically due to wrong password defined on the client or poor signal strength/quality.
Failure to get a DHCP address can be due to configuration issues in the DHCP service on the Router.
Enjoy the Music!
moodeaudio.org | Mastodon Feed | GitHub
Reply
#12
@yannig 

What Al said regarding moOde's WebUI Network Configuration screen.

As for the iwlist outout, the reported signal level (-71dBm) is extremely low; hence the low link quality.

I don't have an RPi3B+ fired up but an RPi4B in a partially metallic Argon One case, and located about 3m from my router containing dual APs yields the following numbers


Code:
         Cell 01 - Address: A8:70:5D:49:74:BA
                   Channel:157
                   Frequency:5.785 GHz
                   Quality=65/70  Signal level=-45 dBm
         ...
          Cell 08 - Address: A8:70:5D:49:74:B9
                    Channel:6
                    Frequency:2.437 GHz (Channel 6)
                    Quality=70/70  Signal level=-27 dBm
         ...

where -27 dBm is stronger than -45 dBm (you can look it up...) but both have been acceptable in my operations. I normally connect to the 5GHz AP because the congestion is less.

Is your RPi3B+ in a metal enclosure or otherwise shielded? If so, you might try an external USB/WiFi adapter if you have one.

Another thought: your RPi and AP are rather close together. You might try moving them farther apart as a test---it's possible to overload the input stage of the WiFi adapter.

I'm not sure, though, that the low link quality by itself would prevent authentication.

I'm glad you included the full iwlist output. I see your AP is advertising both the older WPA(1) and the newer WPA2 authentication schemes. I'll have to think a bit about whether it's possible for that to create a problem when moOde/Linux negotiates with it. Off the top of my head, it wouldn't but it's been quite a while since I wrestled with the transition (WPA2 was approved in 2004).

Interesting puzzle Tongue 

Regards,
Kent

PS - I don't understand why you got that curious "wlan0 interface doesn't support scanning...." message.
Reply
#13
(08-14-2023, 08:00 PM)Nutul Wrote:
(08-14-2023, 06:18 PM)yannig Wrote: (...) (and it is impossible to edit manually such SSIDs under moOde).

Unfortunately I cannot help you with your problem, but the above statement leaves me a bit perplexed... what is, specifically, that doesn't let you edit them manually?
1. there is an option to manually enter the SSID
2. the OSK contains the underscore
3. you can always edit them from a browser

I can't edit manually only SSID which contains underscores
but that's not a problem : I changed the SSIDs
musical regards

y.
Reply
#14
(08-14-2023, 08:50 PM)TheOldPresbyope Wrote: @yannig 

What Al said regarding moOde's WebUI Network Configuration screen.

As for the iwlist outout, the reported signal level (-71dBm) is extremely low; hence the low link quality.

I don't have an RPi3B+ fired up but an RPi4B in a partially metallic Argon One case, and located about 3m from my router containing dual APs yields the following numbers


Code:
         Cell 01 - Address: A8:70:5D:49:74:BA
                   Channel:157
                   Frequency:5.785 GHz
                   Quality=65/70  Signal level=-45 dBm
         ...
          Cell 08 - Address: A8:70:5D:49:74:B9
                    Channel:6
                    Frequency:2.437 GHz (Channel 6)
                    Quality=70/70  Signal level=-27 dBm
         ...

where -27 dBm is stronger than -45 dBm (you can look it up...) but both have been acceptable in my operations. I normally connect to the 5GHz AP because the congestion is less.

Is your RPi3B+ in a metal enclosure or otherwise shielded? If so, you might try an external USB/WiFi adapter if you have one.

Another thought: your RPi and AP are rather close together. You might try moving them farther apart as a test---it's possible to overload the input stage of the WiFi adapter.

I'm not sure, though, that the low link quality by itself would prevent authentication.

I'm glad you included the full iwlist output. I see your AP is advertising both the older WPA(1) and the newer WPA2 authentication schemes. I'll have to think a bit about whether it's possible for that to create a problem when moOde/Linux negotiates with it. Off the top of my head, it wouldn't but it's been quite a while since I wrestled with the transition (WPA2 was approved in 2004).

Interesting puzzle Tongue 

Regards,
Kent

PS - I don't understand why you got that curious "wlan0 interface doesn't support scanning...." message.

"Is your RPi3B+ in a metal enclosure or otherwise shielded?" :
no, is it a test at the moment, these is absolutly nothing around the Raspberry, only the Boss.
musical regards

y.
Reply
#15
@kent


And I get this in AP mode.

And with a distance around 4 meters from my  computer to the raspberry

Code:
pi@moode-l:~ $ sudo iwlist wlan0 s
wlan0     Scan completed :
         Cell 01 - Address: CC:2D:21:91:7B:01
                   Channel:1
                   Frequency:2.412 GHz (Channel 1)
                   Quality=70/70  Signal level=-20 dBm  
                   Encryption key:on
                   ESSID:"Tenda-917B00"
                   Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 6 Mb/s
                             9 Mb/s; 12 Mb/s; 18 Mb/s
                   Bit Rates:24 Mb/s; 36 Mb/s; 48 Mb/s; 54 Mb/s
                   Mode:Master
                   Extra:tsf=0000000000000000
                   Extra: Last beacon: 20ms ago
                   IE: Unknown: 000C54656E64612D393137423030
                   IE: Unknown: 010882848B960C121824
                   IE: Unknown: 030101
                   IE: Unknown: 050402030000
                   IE: Unknown: 2A0104
                   IE: Unknown: 32043048606C
                   IE: Unknown: 2D1AEE191EFFFF000000000000000000000000000000001804810800
                   IE: Unknown: 3D1601050000000000000000000000000000000000000000
                   IE: WPA Version 1
                       Group Cipher : CCMP
                       Pairwise Ciphers (1) : CCMP
                       Authentication Suites (1) : PSK
                   IE: IEEE 802.11i/WPA2 Version 1
                       Group Cipher : CCMP
                       Pairwise Ciphers (1) : CCMP
                       Authentication Suites (1) : PSK
                   IE: Unknown: DD180050F2020101800003A4000027A4000042435E0062322F00
                   IE: Unknown: DD0600E04C020160
                   IE: Unknown: DD5A0050F204104A00011010440001021054000800060050F2040001101100135265616C74656B20576972656C65737320415010080002278810470010112233445566778899AACC2D21917B00103C0001031049000600372A000120
                   IE: Unknown: 7F080000000000000000

The Raspberry looks OK, at least !

it looks like it's really my router that's weird, but only with rapsberries.

On my macmookpro (at around 4 meters), the signal strength RSSI is-40dBm on 2.5GHz and -45dBm on 5GHz
musical regards

y.
Reply
#16
Try removing the Boss DAC. It has clocks (oscillators) that may be emitting EMI thats interfering with WiFi signal.
Enjoy the Music!
moodeaudio.org | Mastodon Feed | GitHub
Reply
#17
(08-15-2023, 01:07 AM)yannig Wrote: @kent


And I get this in AP mode.

And with a distance around 4 meters from my  computer to the raspberry

Code:
pi@moode-l:~ $ sudo iwlist wlan0 s
wlan0     Scan completed :
         Cell 01 - Address: CC:2D:21:91:7B:01
                   Channel:1
                   Frequency:2.412 GHz (Channel 1)
                   Quality=70/70  Signal level=-20 dBm  
                   Encryption key:on
                   ESSID:"Tenda-917B00"
                   Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 6 Mb/s
                             9 Mb/s; 12 Mb/s; 18 Mb/s
                   Bit Rates:24 Mb/s; 36 Mb/s; 48 Mb/s; 54 Mb/s
                   Mode:Master
                   Extra:tsf=0000000000000000
                   Extra: Last beacon: 20ms ago
                   IE: Unknown: 000C54656E64612D393137423030
                   IE: Unknown: 010882848B960C121824
                   IE: Unknown: 030101
                   IE: Unknown: 050402030000
                   IE: Unknown: 2A0104
                   IE: Unknown: 32043048606C
                   IE: Unknown: 2D1AEE191EFFFF000000000000000000000000000000001804810800
                   IE: Unknown: 3D1601050000000000000000000000000000000000000000
                   IE: WPA Version 1
                       Group Cipher : CCMP
                       Pairwise Ciphers (1) : CCMP
                       Authentication Suites (1) : PSK
                   IE: IEEE 802.11i/WPA2 Version 1
                       Group Cipher : CCMP
                       Pairwise Ciphers (1) : CCMP
                       Authentication Suites (1) : PSK
                   IE: Unknown: DD180050F2020101800003A4000027A4000042435E0062322F00
                   IE: Unknown: DD0600E04C020160
                   IE: Unknown: DD5A0050F204104A00011010440001021054000800060050F2040001101100135265616C74656B20576972656C65737320415010080002278810470010112233445566778899AACC2D21917B00103C0001031049000600372A000120
                   IE: Unknown: 7F080000000000000000

...

These numbers are excellent. Assuming the Pi is still running moOde and still has the BOSS DAC attached, you should be able to reboot and have it associate properly in WiFi-client mode rather than time out and revert to AP mode.

Regarding Tim's observation, several DAC HATs (the problem first came to light with one of the HiFiBerry products) are known to interfere with 2.4GHz WiFi. IIRC the interference was especially bad on channel 1 and with RPi3Bs. Switching to 5GHz WiFi or using an external USB/WiFi adapter are viable remedial solutions.

As an aside, it's also true that using the USB3.0 ports on the RPi4B can interfere with 2.4GHz WiFi.

We like to think of WiFi as a digital communication mechanism, but inside and between the transceivers it's all analog radio communications. I dabbled for a time in radio engineering way back in the last century when everything was based on vacuum tube. It's astounding to me that WiFi works at all.

Regards,
Kent
Reply
#18
Hi Guys first post here, but a long time Moode user
I have a Pi 4, Allo DigiOne dac, and a Pi  7"touch display.
I can confirm that the only way to have a reliable WiFi
connection is with a usb fob ,plus extension cable.
My current setup is with an Ethernet cable.

as an interesting aside, a recent upgrade (don't recall which)
caused my very ancient Wi-Pi fob to stop working,apparently
no longer supported.
Reply
#19
Hello
Sorry for the long time without message.

In the meanwhile, I installed the Raspberry + moOde in a friend's house, with another router.
Ans surprise : it worked (and still works) like a charm !

I assume that the (strange)problem is more on my router side than the Rapsberry.

So I'm going to find out about a new better router.
musical regards

y.
Reply


Forum Jump: