This thread is exclusively to share experiences about eBlockerOS 2.6 on Raspberry Pi 3 only.
Background
The update to 2.6 should should eliminate the "freeze bug" discussed here. To update please use this image. It's not recommended to update from <2.6 (as your Raspi 3 might freeze during the update)
eBlocker Freeze on Raspi 3, V2.6.2
- Clean installation done. No VPN, no individual block lists, no device cloaking, no eBlocker Mobile.
- eBlocker is DHCP-server, Parental Controls and HTTPS activated
- Worked fine for 5 days, then freeze / no internet -> restart via power switch
Setup:
Raspberry Pi 3 B V1.2, 1GB
SanDisk Ultra 32GB, A1, Class 10
Power Supply 5V/3A/15W
eBlockerOS Version: 2.6.2
Worked fine for 5 days, then freeze
Next time the devices freezes please ping the device and also do a „tracert eblocker.org“ to see if it still routes. (see here for PC clients https://eblocker.org/docs/check-the-network-connection-with-windows/ - also available for macOS)
Please send diagnosis report right after rebooting if freeze occurs again to support at eblocker.org.
THX!
Today, 6 days after the last freeze, there was another freeze. I was able to ping the eblocker device successfully, but a tracert did not work ("The target name eblocker.org could not be resolved"). I also had no access to the dashboard and the settings anymore.
I created a diagnostic report directly after the reboot and sent it to support at eblocker.org. Maybe you can find out something.
The target name eblocker.org could not be resolved
This is a DNS but not a routing issue. With the next „freeze“ please execute „tracert 1.1.1.1“ to verify the routing.
Please also share your settings of the DNS firewall (screenshots of all settings please). I feel it‘s not eBlocker „freezing“, but maybe some of your external DNS servers not responding...
Could you please disable the DNS firewall for the next trial. In the meantime we‘ll check your logs.
THX!
@misterwick Just quickly checked the logs and a quick thought: Your Pi signals an "undervoltage" condition sometimes.
Are you using a >2A power supply to power the Pi? If not, please change to provide more power to your Pi as undervoltage is a regular "bug" causing freezes.
THX!
@misterwick Logs show that your freeze is not software but hardware related. Please change power supply to 2.5A at least (as discussed above) - and if issue still occurs - please change SD card as well.
BTW: we have a couple of Raspi 3 - all running smoothly since release of 2.6. 👍
THX!
I already use a 3A power supply. Ok, then I will exchange it for another one with 3A and continue testing.
@misterwick You might want to change the SD as well if you have an extra one to spare...
THX!
@misterwick Just checking back: have you had any more „freezes“ after changing SD/power supply?
Here all Raspi 3 run fine with 2.6 and I‘d like to confirm your issue is not related to eOS but to hardware.
THX!
@random I replaced the power supply and had 2 more freezes after that. I will send you the two diagnostic reports.
Next I will replace the SD card and continue testing.
I will send you the two diagnostic reports.
No need for the reports. Problem must be hardware related. Please change SD card first.
THX!