Dear community, may I ask for your support?
I have been using: Fritzbox 7590 AX on a fiber optic modem since 27.12.2023.
The fiber optic is provided operationally by Telekom.
My provider is Vodafone.
My eBlocker is the white cube with eBlocker OS 3.0.1
All Fritzbox settings were restored from a backup when the 7590 was first set up. The backup came from the Fritzbox 6591 Cable which was previously in reliable use with eBlocker.
The now active 7590 AX has IPv6 activated.
Problem: the eBlocker function test shows an error message at 'DNS Firewall' : Your device uses a cached DNS response. Please restart the test in a few minutes.
This function test result is displayed on Windows, Linux and iOS.
I am uncertain whether this is an indication of suboptimal Fritzbox settings that prevent eblocker from working optimally. Therefore, I would like to make sure that at least the Fritzbox is set so that the eBlocker works properly.
Do you have any sample solutions for the Fritzbox 7590 AX that I can use?
Thank you very much!
@obitwo First off all the backup does not include any network/DNS parameters. This is intended. Otherwise a backup could not be restored for an eBlocker running in a different network.
So you need to set up your network settings again following the eBlocker Setup Instructions.
The error you are getting indicates that you have not rebooted your client device (as it still uses cached information). Please reboot as told in the extended error message.
If you are still get an error in the Function Test afterwards, please share all infos requested here: https://eblocker.org/en/docs/setup-instructions-start-here-eblocker-beginners/
Last: there is no such thing as "setting templates" for certain devices/routers. The setup is up to your liking, requirements and know how. I'd personally recommend to use eBlocker's Individual or Expert Network Mode for maximum flexibility and compatibility.
THX!
@random Thank you for your swift response, much appreciated!
The error you are getting indicates that you have not rebooted your client device (as it still uses cached information). Please reboot as told in the extended error message.
The reboot I did on all client devices. The error message persists, though.
If you are still get an error in the Function Test afterwards, please share all infos requested here: https://eblocker.org/en/docs/setup-instructions-start-here-eblocker-beginners/
THX!
Hardware you use for running eBlockerOS
White Cube eBlocker device
eBlockerOS version as well as filter lists version
3.0.1
eBlocker network mode (auto, individual or expert)
Auto
eBlocker network settings (IP, mask, gateway)
IP: 192.168.188.53
mask: 255.255.255.0
Gateway: 192.168.188.1
Which device runs DHCP server? Router/external, eBlocker or client fixed IP?
Router Fritzbox 7590 AX runs DHCP server for both IPv4 and IPv6
eBlocker
IPv6 disabled for client/network?
IPv6 is enabled
eBlocker DNS firewall settings
eBlocker is set as DNS firewall
Resolve domain names via: Internet Provider
Client network settings (IP, mask, DNS, gateway)
IP: auto
DNS: auto
gateway: auto
Whether eBlocker’s https integration is enabled for client
No
Client browser and OS version (i.e. FireFox 80.1 running on macOS 13.4)
#1 Chrome 120 on Windows 11
#2 Chrome 120 on Ubuntu 23.10
#3 Safari on iOS 17.2.1
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
Thank you!
@obitwo I'd try to switch to Individual Network mode (or Expert even). This will probably solve the issue.
THX!
@random Thank you for your feedback.
I wonder how this could solve the DNS Firewall issue.
Thank you!
I wonder how this could solve the DNS Firewall issue
Technical background: Automatic Network Mode uses ARP-spoofing to redirect IPv4 packets to the eBlocker. Most OSs use IPv4 UDP for resolving DNS even if IPv6 is active. Some routers have issues with the constant ARP responses eBlocker is sending. In rare cases this yields to the effect that some IPv4 packets are by-passing the eBlocker. This seems to be the reason why the DNS test fails. But maybe just the test is broken?
Again: I'd suggest to give it a try and judge afterwards... And, yes: a reboot of all network devices is mandatory after switching Network Mode.
THX!
@random Thank you once again for your recommendation.
However I tried something else first: Fritz!OS 7.7 has been available as a beta from AVM for a few days now. Among other improvements, this version is intended to eliminate unspecified errors in the home network.
I installed Fritz!OS 7.70 beta on the Fritzbox on 18.01.2024.
The subsequent tests now show error-free protection by the eBlocker on all devices.
However, it is not clear what exactly has now eliminated the problem. At least the eBlocker is now working again.
Thank you!
@obitwo Perfect. 👍
As I discussed above Automatic Network Mode can result in issues with some routers - or apparently even with specific router OS versions. 😉
Again: It's always the safest bet to switch to Individual or Expert Network Mode. And I repeat my suggestion: make the switch in case other network issues arise again.
Nevertheless, I'm happy AVM fixed it's bugs turning Automatic Mode to be compatible again.
THX!