@nerd
I loaded the latest version of Volumio 4.026 onto the SD card and launched it on a Raspberry Pi 5.
Initial configuration over Wi-Fi - the connection to the Hotspot was successful.
It works without any problems over Wi-Fi with the Fritzbox router - whether 2.4 or 5 GHz - whether WPA 2 or WPA2/3.
The problem begins when:
The Raspberry Pi 5 (Volumio 4.026) is connected to the Fritzbox router over Wi-Fi and at the same time a LAN cable is connected to the Raspberry Pi 5 (Volumio).
The Wi-Fi network settings disappear - in the Volumio network settings menu - there is no option to connect over Wi-Fi.
The LAN settings appear in the Volumio network settings. Only LAN connection works - Raspberry Pi (Volumio 4.026)
After disconnecting the LAN cable from the Raspberry Pi 5, Wi-Fi connection to the router returns - regardless of 2.4 - 5 GHz - WPA2 or WPA2/3.
The Volumio menu appears - networks - Wi-Fi settings - and the LAN settings disappear.
Some of you have noticed that starting with version 4.024 (see PR #231), Volumio behaves differently when both Ethernet and Wi-Fi are connected. This change is not specific to Bookworm, nor to any single router brand - it applies across all platforms.
What has changed is the introduction of Single Network Mode:
Why: Running both Ethernet (eth0) and Wi-Fi (wlan0) at the same time has long caused problems with discovery protocols like Avahi, mDNS, UPnP, Airplay, and DLNA. When a device advertises the same services twice on the LAN, some clients fail to connect or see duplicates.
How it works:
If Ethernet is plugged in, Wi-Fi is disabled. Only LAN settings are shown in the Network menu.
If Ethernet is disconnected, Wi-Fi is enabled and wireless options appear in the menu.
Switching is dynamic: unplugging Ethernet immediately brings Wi-Fi back, plugging it in hides Wi-Fi again.
Impact:
If you configure Wi-Fi while Ethernet is still connected, the credentials are saved, but Wi-Fi will not start until Ethernet is unplugged. This often looks like Wi-Fi is âmissingâ.
This is not a bug - it is by design to prevent unstable network behavior.
Known limitation
At present, the UI does not explain why Wi-Fi disappears when a LAN cable is present. This can be confusing, especially during first-time setup.
Potential improvements
Adding a clearer message in the Network settings, for example: âWi-Fi disabled because Ethernet is connectedâ.
Longer term, offering a setting to choose interface priority (LAN vs Wi-Fi) could give advanced users more flexibility.
For now, the simple rule is:
Use Ethernet if you want a wired connection.
Unplug Ethernet if you want to use Wi-Fi.
Donât expect both to be visible at once in the Network menu.
@nerd
ok but the problem are the information settings over GUI when save data not work, I save data for connection via wifi disconnect LAN cable and not work via wireless connection this is the problem, also if I restard raspberry.
My personal opinion are both interface must be UP like old version and end user deactivate one of this,in alternative GUI must save data also if LAN cable are plug in.
Fresh installation = LAN cable plugged in
Or alternatively, by default the new situation: either wired or wifi, with a user-switchable option to have both. The latter requirements is probably the exception. This way the accidental clashes described by @nerd will not happen.
I did this on my Raspberry Pi 3B+.
I selected one of my networks, pressed connect, and quickly disconnected the LAN cable. After a moment, I launched Advanced IP Scanner and found the Raspberry Pi connected via Wi-Fi. But I donât think thatâs how itâs supposed to work
Hey @nerd,
I unplugged the LAN cable and disabled the LAN, and rebooted my Raspberry Pi connected to the touch panel and also virtual keyboard donât work, so I connected a keyboard set the password from my 5G router but not connect.
@nerd
I reinstalled Volumio 4.026 â the initial configuration was only via LAN.
The âMedia Serversâ plugin in Volumio sees the Fritzbox â the âFritzbox MediaSerwerâ sees the drive connected to the Fritzbox.
After accessing this drive via the Media Server plugin, it sees the driveâs contents â directories and music files. I can play these files using Volumio without any problems.
With version 4.027 we have reverted the change from 4.024 that forced Single Network Mode, and returned to the familiar multi-mode networking (both Ethernet and Wi-Fi visible at the same time).
Why was Single Network Mode introduced in the first place?
Running both Ethernet (eth0) and Wi-Fi (wlan0) simultaneously has long caused issues with discovery protocols like Avahi, mDNS, UPnP, Airplay, and DLNA.
When a device advertises the same services twice on the LAN, some clients fail to connect, or show duplicate entries.
The idea behind Single Network Mode was to simplify this by ensuring only one active interface at a time, switching dynamically between Ethernet and Wi-Fi.
Why revert now?
In practice, the all-or-nothing switch proved confusing.
Users configuring Wi-Fi while Ethernet was connected often thought Wi-Fi was âmissingâ, even though credentials were saved.
The UI did not explain what was happening, making first-time setup harder rather than easier.
What happens next?
The concept of Single Network Mode is still needed, but it will be introduced in smaller steps.
This allows us to add the proper UI messages, clarify behavior, and eventually offer an option for advanced users to set interface priority.
For now, 4.027 restores the previous behavior so that:
Ethernet and Wi-Fi are visible together.
You can configure both without unplugging cables.
Stability will be monitored while we refine the Single Network Mode approach.
Hello @nerd
I just updated my Rpi5 wireless from 4.026 to 4.027. After update wifi connection is gone. I tried manual shutdown and restart without any luck. This rpi5 is only connected using wifi.
I will try to connect with ethernet when I get back home.
Similar problem with Rpi4 - updated OTA from 4.026 to 4.027 - will no longer work with wireless only. On manual restart with wired ethernet managed to reconnect but wireless is still showing no connection
Thank you for reporting. The Wi-Fi loss you saw after updating to 4.027 was not caused by your hardware or configuration. That build ran into a timeout with independent third-party repositories during image creation, which was reported, but missed.
Iâve cleared out those errors in the new 4.028 build. Once it becomes available for your device, please update and check again. If Wi-Fi still does not come up, connect temporarily with Ethernet, open http://<volumio_IP>/dev and share the generated log link so we can confirm.
I found another bug when playing files using the Media Servers plugin.
The network drive (connected via USB to the router) has a root directory containing music directories and, separately, the music files themselves.
When selecting a music file from the root directory, the first file in the first directory is selected for playback. Instead of the correct music file.
For example, in the picture, I select the song âDrive MQA.flacâ or âCell block tango.mp3â for playback, and the first music file in the directory is selected: Dschinghis Khan
Example music directories and separate music files.
Thank you for following up with 4.028. There was an important change between 4.026 and 4.028:
In 4.026 we introduced Single Network Mode - only one interface (Ethernet or Wi-Fi) is active at a time.
In 4.028 we reverted to multi-homed interfaces - both Ethernet and Wi-Fi can be up simultaneously again.
Because your Fritzbox sees Volumio differently in these two versions, we need to check whether the problem lies in Volumioâs Media Server browsing code or in how the Fritzbox handles a multi-homed client.
Could you please test the following three scenarios with 4.028 and send us a dev log link (http://<volumio-ip>/dev â Send Log) for each?
Raspberry Pi connected via Ethernet only (Wi-Fi disabled/unplugged).
Raspberry Pi connected via Wi-Fi only (Ethernet unplugged).
Raspberry Pi connected with both Ethernet and Wi-Fi enabled.
This will help us see whether the Media Server disappearance only happens in multi-homed mode or also when a single interface is active.
Raspberry PI 5 - Volumio 4.028 - After updating from 4.027 to version 4.028 and after several restarts, access to files in the router via the Media Servers plugin appeared.
Fritzbox 5590 - wifi 5 Ghz - WPA 2 / 3.
The problem with the Media Servers plugin not selecting files for playback correctly remains. This issue was described a few posts above
Hey @nerd ,
I have test several time and a little bug persist, if I start first time (fresh install) my raspberry PI 5 at network tab select my wifi network and GUI freeze (lan cable plugged in).
If I start up (fresh install) and not try to connect to my wireless router after finish power up go in network setting (LAN cable plugged in) select my network insert my wpa key SAVE it GUI interface freeze.
I unplug LAN cable but no connections to my router so I power off my Raspberry (GUI are freezed) and after restart finally (LAN cable sconnected) my wireles connections are ok.
Another things is virtual keyboard not work in touch display.
