Moode Forum
[PROBLEM] WiFi (AP) and CAT-5 together - Printable Version

+- Moode Forum (http://moodeaudio.org/forum)
+-- Forum: moOde audio player (http://moodeaudio.org/forum/forumdisplay.php?fid=3)
+--- Forum: Support (http://moodeaudio.org/forum/forumdisplay.php?fid=7)
+--- Thread: [PROBLEM] WiFi (AP) and CAT-5 together (/showthread.php?tid=1730)

Pages: 1 2


RE: WiFi (AP) and CAT-5 together - psychofaktory - 09-21-2019

That feature has been requested for several times now.

I've posted an instruction how you can turn Moode to a real Access-Point for MoodeOS 4.1:
Turn Moode to a real Access-Point


I didn't test if thats still working in MoodeOS 6.2.1

I would appreciate this as an integral feature part of MoodeOS, as at least some other users have this usage scenario.

@Meestor_X:
If you find a better/easier way to achive this in MoodeOS 6.2.1 I would be happy if you share your solution with us.


RE: WiFi (AP) and CAT-5 together - Meestor_X - 09-21-2019

I'm not really a networking expert, so I don't know that the difference is between having both wired and wireless interfaces working at the same time and making MoOde into a "real" AP. I would just like to have both working together.

I'm not sure if getting rid of the "if" statement that Tim alluded to will also get rid of any "delay" that there might be before enabling the WiFi. My "feeling" (not confirmed) is that MoOde polls the wired connection for several seconds/minutes to see if it's connected before enabling WiFi AP mode. I'd also like to eliminate that delay.


RE: WiFi (AP) and CAT-5 together - Tim Curtis - 09-21-2019

System Config, Wait for eth0 address, set to OFF


RE: WiFi (AP) and CAT-5 together - Meestor_X - 09-27-2019

Thanks, Tim.

Setting that OFF doesn't make much difference. There's still an extra minute+ of time before the WiFi is enabled.

With my RPI3 it's 30sec from boot to ready via wired.
It's 90sec from boot to ready via wireless with Wait for eth0 OFF, and it's 135sec from boot to read via wireless with Wait for eth0 ON.

Is that a limitation of the RPI's wireless system or is there another delay in the MoOde software?


RE: WiFi (AP) and CAT-5 together - Tim Curtis - 09-27-2019

Have a look at the moOde log. It will show exactly how much time it takes for eth0 and wlan0 interfaces to acquire an IP address from your Router.

moodeutl -l

- or -

cat /var/log/moode.log


RE: WiFi (AP) and CAT-5 together - Meestor_X - 10-09-2019

On my RPI3+, with Wait Off and Wired disconnected, here is the log:

Code:
20191009 141751 worker: - Start
20191009 141753 worker: Successfully daemonized
20191009 141753 worker: Integrity check (passed)
20191009 141753 worker: Session loaded
20191009 141753 worker: Debug logging (off)
20191009 141753 worker: ALSA volume set to (0%)
20191009 141753 worker: - Platform
20191009 141755 worker: Rel  (Moode 6.2.0 2019-09-05)
20191009 141755 worker: Rasp (10.0)
20191009 141755 worker: Kern (4.19.69-v7+)
20191009 141755 worker: MPD  (0.20.23)
20191009 141755 worker: Host (moode)
20191009 141755 worker: Hdwr (Pi-3B+ 1GB v1.3)
20191009 141755 worker: Arch (armv7l)
20191009 141755 worker: Gov  (ondemand)
20191009 141755 worker: USB boot enabled
20191009 141755 worker: File system expanded
20191009 141755 worker: HDMI port on
20191009 141756 worker: File check (OK)
20191009 141756 worker: - Network
20191009 141756 worker: eth0 exists
20191009 141756 worker: eth0 address not assigned
20191009 141756 worker: wlan0 exists
20191009 141756 worker: wifi country (US)
20191009 141756 worker: wlan0 SSID is blank
20191009 141756 worker: wlan0 AP mode started
20191009 141829 worker: wlan0 wait 0 for IP address
20191009 141832 worker: wlan0 wait 1 for IP address
20191009 141835 worker: wlan0 (172.24.1.1)
20191009 141835 worker: - Audio
20191009 141836 worker: ALSA outputs unmuted
20191009 141836 worker: ALSA card number (0)
20191009 141836 worker: Audio output (I2S audio device)
20191009 141836 worker: Audio device (HiFiBerry DAC+ Pro)
20191009 141836 worker: ALSA mixer name (Digital)
20191009 141836 worker: MPD volume control (software)
20191009 141836 worker: Hdwr volume controller exists
20191009 141836 worker: - Services
20191009 141836 worker: Reset renderer active state
20191009 141836 worker: MPD conf updated
20191009 141836 worker: MPD started
20191009 141837 worker: MPD accepting connections
20191009 141837 worker: Configure MPD outputs
20191009 141837 worker: MPD output 1 ALSA default (on)
20191009 141837 worker: MPD output 2 ALSA crossfeed (off)
20191009 141837 worker: MPD output 3 ALSA parametric eq (off)
20191009 141837 worker: MPD output 4 ALSA graphic eq (off)
20191009 141837 worker: MPD output 5 ALSA polarity inversion (off)
20191009 141837 worker: MPD output 6 ALSA bluetooth (off)
20191009 141837 worker: MPD output 7 HTTP stream (off)
20191009 141837 worker: MPD crossfade (1 secs)
20191009 141837 worker: Audio source (Local)
20191009 141837 worker: Output device (Local)
20191009 141837 worker: Airplay receiver started
20191009 141837 worker: Bluetooth controller started
20191009 141844 worker: Bluetooth controller initialized
20191009 141844 worker: Bluetooth pairing agent started
20191009 141844 worker: USB auto-mounter (udisks-glue)
20191009 141844 worker: - Music sources
20191009 141844 worker: USB sources (none attached)
20191009 141844 worker: NAS and UPnP sources (none configured)
20191009 141844 worker: - Miscellaneous
20191009 141844 worker: Saved MPD vol level (0)
20191009 141844 worker: Preamp volume level (0)
20191009 141845 worker: MPD volume level (75) restored
20191009 141845 worker: ALSA volume level (100%)
20191009 141845 worker: Auto-play (Off)
20191009 141845 worker: Maintenance interval (6 hrs)
20191009 141845 worker: Screen saver activation (Never)
20191009 141845 worker: Session permissions (OK)
20191009 141845 worker: Watchdog started
20191009 141845 worker: Ready

Not sure how to read this.... How many seconds is that?


RE: WiFi (AP) and CAT-5 together - Tim Curtis - 10-09-2019

The time is in 24 hour format for example 14 = 2PM. The other digits are minutes and seconds.

The elapsed times from your log are perfectly normal. I see similar times on a 3B that comes up in AP mode. Just remember that these times only represent how long it takes moOde startup sequence to complete. It doesn't include the time it takes Linux to boot to the point where it runs /etc/rc.local script which launches the moOde startup daemon, worker.php.

Code:
20191009 141751 worker: - Start
20191009 141845 worker: Ready
         ------
             54 secs total

Code:
20191009 141756 worker: wlan0 exists
20191009 141756 worker: wifi country (US)
20191009 141756 worker: wlan0 SSID is blank
20191009 141756 worker: wlan0 AP mode started
20191009 141829 worker: wlan0 wait 0 for IP address
20191009 141832 worker: wlan0 wait 1 for IP address
20191009 141835 worker: wlan0 (172.24.1.1)
         ------
             39 secs to complete AP mode initialization