[PROBLEM] Connecting with wifi

[LuNik700]

Hi everybody,
my name is  Ludger and I'm having problems to integrated one of my moOde-players into my network via wifi.

I use 2 Raspberry Pi with moOde - one is working perfect, the other isn't.

Both a based on a Raspberry Pi 2 Modell B V1.1, with a MamboBerry LS I2S audio device and an EdiMax Wifi stick. And both are using an SD-Card with the lastest moOde release 6.3. So I would say the setup is identical.

The problem seems to be that scanning for an SSID does not return a result (no matter of distance - the Raspberry is right beside the router!). Entering the SSID manually doesn't help.
Therefore the RasPi falls into AP mode. If I then connect to moOde using 172.24.1.1, I can access moOde but again I not able to change settings for my wifi network.

The funny thing is that when I use an SD card with an old moOde Release 3.8.4. everything works fine out of the box. So it doesn't seem to be a hardware issue!?!

Here is a a snippet of moodeutl -l ...

20191113 110500 worker: wlan0 trying SSID (LuNik700-2)
20191113 110500 worker: wlan0 wait 0 for IP address
20191113 110503 worker: wlan0 wait 1 for IP address
20191113 110507 worker: wlan0 wait 2 for IP address
20191113 110510 worker: wlan0 wait 3 for IP address
20191113 110513 worker: wlan0 wait 4 for IP address
20191113 110516 worker: wlan0 no IP addr for SSID (LuNik700-2)
20191113 110516 worker: wlan0 AP mode started
20191113 110549 worker: wlan0 wait 0 for IP address
20191113 110553 worker: wlan0 wait 1 for IP address
20191113 110556 worker: wlan0 (172.24.1.1)

I not very experienced in Raspbian so I havn't got a clue where to look at next.

Please can somebody give me a hint. Thanks!

Best regards 
Ludger

[Tim Curtis]

Check that the wpa_supplicant file is identical on both Pi's.

Refer to this post
http://moodeaudio.org/forum/showthread.p...8#pid14358

[LuNik700]

Check that the wpa_supplicant file is identical on both Pi's.

Refer to this post
http://moodeaudio.org/forum/showthread.p...8#pid14358

Thanks Tim!

Before reading your reply I kept on trying and suddenly it worked! No idea why!?!?!
I checked the wpa_supplicant files on both RasPis and right now they are identical. The password of my wifi includes a '*' and a '#'.

What I don't understand is why scanning for a wifi network did not work?!?! In fact I've got two of them but until at last I succeeded neither of them was found?!?!?!. Is this another bug or is this corresponding to the one mentioned in the post above?

Thanks for your quick and helpful reply!!!!

Best regards
Ludger

[Tim Curtis]

Prolly not a bug in the scan. It runs the command below twice to improve the results. Give it a try.

Code:

sudo iwlist wlan0 scan | grep ESSID | sed 's/ESSID://; s/\"//g'
sudo iwlist wlan0 scan | grep ESSID | sed 's/ESSID://; s/\"//g'

-Tim

[LuNik700]

Prolly not a bug in the scan. It runs the command below twice to improve the results. Give it a try.

Code:

sudo iwlist wlan0 scan | grep ESSID | sed 's/ESSID://; s/\"//g'
sudo iwlist wlan0 scan | grep ESSID | sed 's/ESSID://; s/\"//g'

-Tim

As the wifi failed again after a reboot I tried out the cmd above ...

pi@SysL-RasPi2:~ $ sudo iwlist wlan0 scan | grep ESSID | sed 's/ESSID://; s/\"//g'
wlan0     Interface doesn't support scanning : Operation not supported

and I think that's what moodeutl -l shows:

20191113 173931 worker: wifi country (DE)
20191113 173931 worker: wlan0 trying SSID (LuNik700-2)
20191113 173931 worker: wlan0 wait 0 for IP address
20191113 173934 worker: wlan0 wait 1 for IP address
20191113 173937 worker: wlan0 wait 2 for IP address
20191113 173940 worker: wlan0 wait 3 for IP address
20191113 173944 worker: wlan0 wait 4 for IP address
20191113 173947 worker: wlan0 no IP addr for SSID (LuNik700-2)
20191113 173947 worker: wlan0 AP mode started
20191113 174003 worker: wlan0 wait 0 for IP address
20191113 174007 worker: wlan0 wait 1 for IP address
20191113 174657 worker: wlan0 (172.24.1.1)

By the way the wpa_supplicant filesare still identical on both Pi's....


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

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

network={
ssid="LuNik700-2"
scan_ssid=1
psk=xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
}



---
Ludger


pi@SysL-RasPi2:~ $

[Tim Curtis]

I have same config: Pi-2B, EdiMax EW-7811Un, Mamboberry LS and no issues with scan.

Code:

pi@rp1:~ $ moodeutl -l | grep Platform
20191108 162628 worker: Platform      (Pi-2B 1GB v1.1)

pi@rp1:~ $ moodeutl -l | grep "Audio device"
20191108 162632 worker: Audio device (Mamboberry LS DAC+)

pi@rp1:~ $ lsusb
Bus 001 Device 004: ID 7392:7811 Edimax Technology Co., Ltd EW-7811Un 802.11n Wireless Adapter [Realtek RTL8188CUS]
Bus 001 Device 003: ID 0424:ec00 Standard Microsystems Corp. SMSC9512/9514 Fast Ethernet Adapter
Bus 001 Device 002: ID 0424:9514 Standard Microsystems Corp. SMC9514 Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

pi@rp1:~ $ sudo iwlist wlan0 scan | grep ESSID
                   ESSID:"AirnetN2"

[TheOldPresbyope]

@LuNik700

(no matter of distance - the Raspberry is right beside the router!)

Literally right beside? That may be so close you're overloading the radio receiver in either or both devices. Try separating them a (meter | 3 feet) or so.

Regards,
Kent

[LuNik700]

@LuNik700

(no matter of distance - the Raspberry is right beside the router!)

Literally right beside? That may be so close you're overloading the radio receiver in either or both devices. Try separating them a (meter | 3 feet) or so.

Regards,
Kent

Good idea ... but didn't work. Before I tried it the Pi was about a meter away from the router ...

Cheers
Ludger

[swizzle]

Might be worth swapping WiFi dongles to see if the problem persists or moves to the other Pi.