Official moOde 7.3.0 support thread

[Tim Curtis]

I'm a little confused. What are the steps to reproduce the issue starting from a powered off Pi.

[eraser1320]

I'm a little confused. What are the steps to reproduce the issue starting from a powered off Pi.

Tell me about it, it's been working great since maybe version 6.9? Until today after I rebooted it, after being on 7.3 since just after it came out, I couldn't connect to the interface anymore and it was no longer connected to my wifi router. It's not in a place where I can keep it plugged into ethernet, so it's always been on wifi.

- From power off, no ethernet plugged in = no wifi.
- Plug in ethernet, wifi and ethernet get IPs and I can connect to both fine.
- Unplug ethernet, wifi dies can't connect anymore.
- Plug back in ethernet, both come up and I can connect to either again just fine.

- Power off, unplug, plug back in power with with ethernet plugged in or unplugged, same behavior as above.
- DHCP or static IPs combinations with both wifi and eth0, same behavior as above.

[Tim Curtis]

I'm not able to repro this because WiFi works fine for me in Step 1 - "From power off, no ethernet plugged in = no wifi.".

All my Pi's except for one are all using just WiFi.

[eraser1320]

I'm not able to repro this because WiFi works fine for me in Step 1 - "From power off, no ethernet plugged in = no wifi.".

All my Pi's except for one are all using just WiFi.

I'm not sure if I'd call this progress but I've gotten somewhere, it seems that without an ethernet cable plugged in it gets stuck in AP mode.

1. I reset the network settings.
2. With ethernet plugged in, setup my wifi network again.
3. Same behavior as before, with ethernet unplugged no wifi connection.
4. However, it switches into AP mode when the ethernet is unplugged.
5. Connect to Moode AP network via IP 172.24.1.1
6. Setup wifi network to connect to again.
7. Same issue, without ethernet plugged in, it switched over to AP mode.
8. As soon as I plug in the ethernet, everything goes back to normal functionality in eth0 or wifi.

[TheOldPresbyope]

I'm not able to repro this because WiFi works fine for me in Step 1 - "From power off, no ethernet plugged in = no wifi.".

All my Pi's except for one are all using just WiFi.

I'm not sure if I'd call this progress but I've gotten somewhere, it seems that without an ethernet cable plugged in it gets stuck in AP mode.

1. I reset the network settings.
2. With ethernet plugged in, setup my wifi network again.
3. Same behavior as before, with ethernet unplugged no wifi connection.
4. However, it switches into AP mode when the ethernet is unplugged.

This suggests to me that your moOde player is unable to locate and/or associate with your LAN's WiFi Access Point using the information you supplied so it reverts to stand-alone AP mode.

5. Connect to Moode AP network via IP 172.24.1.1
6. Setup wifi network to connect to again.
7. Same issue, without ethernet plugged in, it switched over to AP mode.
8. As soon as I plug in the ethernet, everything goes back to normal functionality in eth0 or wifi.

I see in several posts this assertion that both eth0 and wlan0 interfaces are connected yet the only hard data posted so far contradicts it. In post #130 we find

Code:

pi@moode:~ $ moodeutl -l
20210828 111422 worker: -- Start
...
20210828 111427 worker: -- Network
20210828 111427 worker: eth0 exists
20210828 111427 worker: eth0 address not assigned
20210828 111427 worker: wlan0 exists
20210828 111427 worker: wifi country (US)
20210828 111427 worker: wlan0 trying SSID (xxxxxx)
20210828 111427 worker: IP addr (192.168.0.151)
20210828 111427 worker: Netmask (255.255.255.0)
20210828 111427 worker: Gateway (192.168.0.1)
20210828 111427 worker: Pri DNS (192.168.0.1)
20210828 111427 worker: Domain  (xxxxx.xxx)
20210828 111432 worker: Pi integrated wlan0 power save disabled
...

Note the line "eth0 address not assigned"

I'm curious. What is the command-line output from either "ifconfig" or "ip address"?

Regards,
Kent

PS - ifconfig is an obsolete command which hasn't been dropped yet from many Linux distros. I suspect that's because there's a lot of scripts out there with ifconfig embedded in them. Besides, it's hard to teach us old dogs new tricks.

[eraser1320]

Code:

pi@moode:~ $ ifconfig
eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
       inet 192.168.0.152  netmask 255.255.255.0  broadcast 192.168.0.255
       inet6 fe80::1475:f503:d07d:763d  prefixlen 64  scopeid 0x20<link>
       ether b8:27:eb:2d:2c:60  txqueuelen 1000  (Ethernet)
       RX packets 1492  bytes 484409 (473.0 KiB)
       RX errors 0  dropped 0  overruns 0  frame 0
       TX packets 4600  bytes 6043777 (5.7 MiB)
       TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 65536
       inet 127.0.0.1  netmask 255.0.0.0
       inet6 ::1  prefixlen 128  scopeid 0x10<host>
       loop  txqueuelen 1000  (Local Loopback)
       RX packets 245  bytes 23555 (23.0 KiB)
       RX errors 0  dropped 0  overruns 0  frame 0
       TX packets 245  bytes 23555 (23.0 KiB)
       TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

wlan0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
       inet 192.168.0.151  netmask 255.255.255.0  broadcast 192.168.0.255
       inet6 fe80::c50f:5684:92cc:475f  prefixlen 64  scopeid 0x20<link>
       ether b8:27:eb:78:79:35  txqueuelen 1000  (Ethernet)
       RX packets 39  bytes 12386 (12.0 KiB)
       RX errors 0  dropped 0  overruns 0  frame 0
       TX packets 61  bytes 12040 (11.7 KiB)
       TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

[Tim Curtis]

Whats the point of this repost of a previous post?

There is no added new information.

[TheOldPresbyope]

@Tim Curtis - he top posted

@eraser1320 - OK, so both interfaces are indeed assigned IP addresses.

I have a nagging suspicion I have seen something about this before but I can't remember any details and whatever notes I may have had are packed away.

I have no way to use the Ethernet interface here in my temporary digs to experiment with so I'll let others take it from here.

Regards,
Kent

[Wheel_nut]

@eraser1320 - OK, so both interfaces are indeed assigned IP addresses.

I have a nagging suspicion I have seen something about this before but I can't remember any details and whatever notes I may have had are packed away.

I have no way to use the Ethernet interface here in my temporary digs to experiment with so I'll let others take it from here.

Regards,
Kent

Kent, You may be thinking of my report that my RPi 2B with a Realtek USB adapter was unable to search and finf my Access Point. The solution I used was to Manually configure the SSID and Passphrase and was then able to connect.

Tim suggested that the WiFi adapter needs to support "Promiscuous Mode".

Robin

[eraser1320]

@eraser1320 - OK, so both interfaces are indeed assigned IP addresses.

I have a nagging suspicion I have seen something about this before but I can't remember any details and whatever notes I may have had are packed away.

I have no way to use the Ethernet interface here in my temporary digs to experiment with so I'll let others take it from here.

Regards,
Kent

Kent, You may be thinking of my report that my RPi 2B with a Realtek USB adapter was unable to search and finf my Access Point. The solution I used was to Manually configure the SSID and Passphrase and was then able to connect.

Tim suggested that the WiFi adapter needs to support "Promiscuous Mode".

Robin

@Wheel_nut Do you mean manually through the CLI or through the GUI? I can try that for sure.