Search before asking
System information
System Information:
- Device: Raspberry Pi 4b
- OS: Raspberry Pi OS (Fresh installation)
Describe the bug
When installing dweOS via the installation script on a fresh Raspberry Pi OS setup, the installation finishes successfully. However, upon rebooting, if the device is not connected via an Ethernet cable, the dweOS service fails to start.
The service needs a safeguard or a try-catch block to handle network initialization gracefully, ensuring it doesn't crash if a user intends to connect via Wi-Fi instead of a wired connection.
To Reproduce
- Flash a fresh image of Raspberry Pi OS onto an RPi 4b.
- Run the installation script:
curl -s https://raw.githubusercontent.com/DeepwaterExploration/dweOS/main/install.sh | sudo bash -s
- Disconnect the Ethernet cable.
- Reboot the Raspberry Pi.
- Check the service status to see the failure.
Expected behavior
dweOS should handle the absence of an active Ethernet connection gracefully (e.g., via a try-catch block or proper systemd network targets) and remain active so that the user can configure or connect via Wi-Fi.
Additional information
The service needs a safeguard or a try-catch block to handle network initialization gracefully, ensuring it doesn't crash if a user intends to connect via Wi-Fi instead of a wired connection.
Search before asking
System information
System Information:
Describe the bug
When installing dweOS via the installation script on a fresh Raspberry Pi OS setup, the installation finishes successfully. However, upon rebooting, if the device is not connected via an Ethernet cable, the dweOS service fails to start.
The service needs a safeguard or a try-catch block to handle network initialization gracefully, ensuring it doesn't crash if a user intends to connect via Wi-Fi instead of a wired connection.
To Reproduce
curl -s https://raw.githubusercontent.com/DeepwaterExploration/dweOS/main/install.sh | sudo bash -sExpected behavior
dweOS should handle the absence of an active Ethernet connection gracefully (e.g., via a try-catch block or proper systemd network targets) and remain active so that the user can configure or connect via Wi-Fi.
Additional information
The service needs a safeguard or a try-catch block to handle network initialization gracefully, ensuring it doesn't crash if a user intends to connect via Wi-Fi instead of a wired connection.