You can go to System / Diagnostics and click the button: Generate Report.

It creates a Zip file (it might take a few minutes). Are there any errors shown in the "install-eblocker-updates.*" files?

I can also take a look at the report if you send it to "support AT eblocker.org".

Thanks for the quick reply.

I think I gave the wrong details about my Raspberry Pi.

My Raspberry Pi has 4GB.

Best regards

Thomas

Hi Thomas,

the eOS 4.0.3 release seems to have some issue with memory usage on the Raspberry Pi with 2 GB. I have experienced some issues on my 2 GB test system where available memory was very low and the system froze.

In the upcoming release 4.1 we will hopefully solve that problem by assigning a better maximum RAM usage to the main Java process. I think the issue is related to the switch from 32-bit to 64-bit.

Best regards

Boris

Unfortunately, the error described has occurred again.

After disconnecting and reconnecting the power supply, everything was working again. Could this be a bug?

Best regards, Thomas

Thank you for your explanation, very clarifying. Knowing the error-message was just the symptom helped me a lot.

Thanks also for your test suggestions. I assume it may help others the provide some feedback:

1. in VirtualBox (version 7.2.20) I could not find anything related to Offloading so I could not test this unfortunately, and

3. luckily I already had implemented, but

2. did work out as you said. Since then no errors anymore.  

So thank you very much for your help !

But if you want to take eBlocker with you, it depends on the network mode you are running. If you have it in individual or expert network mode, you should switch it back to auto mode at home. The reason is that the network address could be different at the vacation location.

For example, if your home network has address 192.168.178.0 but the vacation location has 192.168.1.0 and your eBlocker has a fixed IP address, it won't work. You would have to change eBlocker's configuration at the vacation location which could be difficult.

Also something to think about: if it's a rented place you probably won't have access to the router's settings, so it could be difficult to find the eBlocker in the network if something does not work immediately.

Can I take the eBlocker to a vacation environment, fare away from my home but Germany, where also a router is available and connect eBlocker to it ?

In other words, during vacation I want to be secured by the eBlocker. At home there is the FritzBox running alone. 

When coming back from vacation eBlocker will be added to home environment soon. 

Are there any issues to do this - or should I follow a special routine for adding eBlocker at vacation location ?

Kind regards Hartmut 

Hi,

This is a known issue in Virtual Box, and the good news: you can test the fix entirely from VirtualBox on Windows - no access to eBlocker needed.

WHAT THE MESSAGE MEANS
"NETDEV WATCHDOG: transmit queue timed out" is the kernel's safety net: eBlocker handed packets to the NIC, ~5.6 s passed without the hardware confirming transmission, so the kernel forced a driver reset. Each event = a brief network drop. It's a symptom, not the cause.

IS THE RED HAT OFFLOAD EXPLANATION PLAUSIBLE?
Partly. The ethtool workaround is real — but for physical Intel 8254x cards. Your "PRO/1000 MT" in VirtualBox is an emulated adapter, so in a VM the likelier causes are: Windows stalling the host (updates, antivirus, disk), PCIe power saving on the NUC, the VM being underpowered (eBlocker with HTTPS integration is CPU-hungry), and only then the emulated e1000 offload path.

WHAT TO TEST, IN ORDER (minutes each, then observe a few days)

1. VirtualBox → Settings → Network → Advanced → Offloading: untick all three boxes, power the VM off, start it. This does exactly what ethtool -K tso off gso off would do inside eBlocker, from the outside.
2. On the NUC: Power Options → Advanced → PCI Express → Link State Power Management → Off. Fixed exactly this symptom on NUCs.
3. Give the VM 2 vCPUs, 2 GB RAM; VDI on the SSD, not a spinning disk.
4. Adapter switch: Settings → Network → Advanced → Adapter Type → "Intel PRO/virtualnet" (virtio). Different driver path, also faster. Caution: if the eBlocker image lacks the virtio driver, the VM gets no network and you can't install it. So: take a snapshot first, switch, start, verify eBlocker still gets 192.168.178.119 and your client can browse. No network → restore snapshot (that result is still useful data for support). Keep the MAC address fixed when switching.

Hope this works for you.

I added an issue on GitHub: https://github.com/eblocker/eblocker/issues/457

first of all I'm not tech savy, but while testing eBlocker OS 4.03 I'm getting this error message on the VirtualBox VM (see the attached picture): 

" e1000 0000:00:03.0 eth0: NET e1000 0000:00:03.0 eth0: NETDEV WATCHDOG: CPU: transmit queue 0 timed out 5632 ms e1000 0000:00:03.0 eth0: reset eth adapter"

and this keeps on repeating multiple times a day.

Now I read in the Red Hat documentation that this could be because the Linux kernel stopped receiving completed packets from my network interface card (NIC) for too long. Suggestion there is to force a driver reset using ethtool to turn off tx and rx checksum or segmentation offloading. Is this a plausible explanation? And is it possible for me to test that in eBlocker since it is a closed OS? 

Any help is appreciated :-)

About my setup: Function testing is all green except for IP6 which I disabled in the router

• Hardware you use for running eBlockerOS > Intel NUCi7 with Intel PRO/ 1000MT Desktop NIC running as a server in network
• eBlockerOS version as well as filter lists version > 4.03
• eBlocker network mode (auto, individual or expert) > auto
• eBlocker network settings (IP, mask, gateway) > Automatic, IP address 192.168.178.119, Networkmask 255.255.255.0, Gateway 192.168.178.1
• Which devices runs DHCP server? Router/external, eBlocker or client fixed IP? > Router runs DHCP, clients have locked IP's 
• IPv6 disabled for client/network? Disabled in router
• eBlocker DNS firewall settings > eBlocker is DNS Server, forwarding DNS requests is Default
• Client network settings (IP, mask, DNS, gateway) >192.168.178.38
• Whether eBlocker’s https integration is enabled for client > Yes
• Client browser and OS version (i.e. FireFox 80.1 running on macOS 13.4) Win11 24H2, Edge 154.0.4258.53
• Additional non default Blockers enabled? (like DuckDuckGo, Consent-Blocker, custom lists etc.) > No
• HTTPS Auto Trust App enabled? > No
• Exact way or a link / screenshot to reproduce the issue
• If VPN or Tor is enabled for the client in eBlocker (and which VPN provider you are using) >No
• Are automatic updates enabled? > Yes