I am running the current version of eBlocker on a Raspberry Pi 3 with 4 GB RAM. My router is a Fritzbox 7490. The eblocker is running the DHCP server, but not the Fritzbox, as recommended in the manual. Since the upgrade on eBlocker version 3.x approximately each third night something happens so that in the morning I have no internet connection for the devices within my WLAN. So every morning, I restart the eBlocker via its GUI. And then again, the internet connection is re-established. But I consider it as a workarround.
What can I do in order to have an continious internet connection as like before the upgrade to eBlocker version 3.x?
as recommended in the manual.
Maybe there is a misunderstanding or the "manual" is wrong as it's technically not recommended to run the DHCP on the router. Would you please point us to the reference where you got this impression so we can correct it. THX!
From your post above I assume
- you are running eBlockerOS in Individual or Expert Network Mode (not in Automatic Mode)
- you have not made any changes to the fritzbox recently (no firmware update, setting change etc.)
- IPv6 is still disabled on the router
- you have rebooted eBlockerOS after the update to 3.0.x already (if not, please do so and check if the issue persists)
If this all holds true, I'd suggest to switch off IPv6 on the eBlocker (Settings> Network > IPv6 Tab - disabled the switch). Otherwise please correct my assumptions and we take it from there.
BTW: It would be great to know at least one of the device's OS that has the WLAN issue to move things forward.
THX!
as recommended in the manual.
Maybe there is a misunderstanding or the "manual" is wrong as it's technically not recommended to run the DHCP on the router. Would you please point us to the reference where you got this impression […]
I refer to this manual: https://eblocker.github.io/help/de/360004553694.html
From your post above I assume
- you are running eBlockerOS in Individual or Expert Network Mode (not in Automatic Mode)
In Individual mode.
- you have not made any changes to the fritzbox recently (no firmware update, setting change etc.)
That's right. I am running Fritzbox with FritzOS 7.57 without any changes on firmware or unusual settings.
- IPv6 is still disabled on the router
Yes. IPv6 is disabled on the Fritzbox at: Internet > Access Data > IPv6
- you have rebooted eBlockerOS after the update to 3.0.x already
As already written above: I did restart the eBlocker in the last couple of weeks approximately two or three times a week due to re-enable the internet connection.
Or is reboot something different than restart?
If this all holds true, I'd suggest to switch off IPv6 on the eBlocker […].
Switching off means disabeling Network > IPv6 (beta) > "Route IPv6 traffic to the eBlocker so that it is protected"? I did it just for now.
But now the eBlocker shows:
IPv6 is active in the network, but the eBlocker is not activated for IPv6. Therefore, the eBlocker cannot protect IPv6 traffic.
Select one of these options:
- Activate the switch above,
- switch off IPv6 on your router
- or manually configure the local address (see below) of the eBlocker as a gateway on all your devices.
As said before IPv6 is been switched off at the Fritzbox.
I will now observe whether the disconnect issue reappears.
BTW: It would be great to know at least one of the device's OS that has the WLAN issue to move things forward.
It is not a WLAN issue because within the WLAN all connection e.g. to Fritzbox or eBlocker or Apple Homepod works. Only the internet is not accessible until the eBlocker was being restarted. All macOS and iOS devices are affected by this issue. We have no machines with other OS'es except the Raspberry Pi that is running the eBlocker.
If eBlockerOS tells you:
IPv6 is active in the network,
Then it is very possible IPv6 is not deactivated on your fritzbox or another router (or device) is acting as an IPv6 gateway. Please double check. Maybe you just did not reboot your device, which might produce the same message. 🤔
You can easily verify if IPv6 is still active by visiting http://ipv6.eBlocker.org - in case it's disabled you'll get an error.
Honestly, I highly doubt the issue is connected to eBlockerOS 3 at all as some ten thousands of users are running this version without issues. But I'm sure we'll find the cause of trouble in your setup.
To do so firstly please provide all infos requested here and stick to one(!) of the macOS devices for future reporting: https://eblocker.org/community/announcements/before-posting-here-please-read/#post-117
On the macOS device please
- Run the eBlocker Doctor (Settings> Doctor) and the Function Test (in device Dashboard) post screenshots of both.
- Run a Traceroute while the device has Internet and post screenshot of the result (see here).
- Please repeat step 2 once Internet is down on the device and also post screenshot here.
THX!
I refer to this manual: https://eblocker.github.io/help/de/360004553694.html
🤔 Maybe my German is too poor but to my understanding it reads no recommendation to run a DHCP on the router. Can you please share the exact phrase that raised the opposite impression with you.
THX!
A router, such as the FritzBox, restarts every night to renew the WAN IP.
The eBlocker does not, you do this manually in the morning.
You should leave the FB to the DHCP and can still assign the eBlocker
a fixed IP. Then set the DNS in the FB to the
eBlocker in the FB.
A router, such as the FritzBox, restarts every night to renew the WAN IP.
The eBlocker does not, you do this manually in the morning.
You should leave the FB to the DHCP and can still assign the eBlocker
a fixed IP. Then set the DNS in the FB to the
eBlocker in the FB.
Sorry, @neuling, but this is complete nonsense!!!
@facebita Please don't get mixed up by @neuling's post and just follow my advice above.
@neuling If you want to discuss further why your post is technical nonsense I'm happy to elaborate in a different thread. Here the discussion is not fruitful as we focus on @facebita's issue.
THX!
You can easily verify if IPv6 is still active by visiting http://ipv6.eBlocker.org - in case it's disabled you'll get an error.
I can not connect my browser to the said website.
So I assume, IPv6 really is not active in my configuration
To do so firstly please provide all infos requested here and stick to one(!) of the macOS devices for future reporting:
- Hardware you use for running eBlockerOS: Raspberry Pi 3 with 4 GB of RAM
- eBlockerOS version as well as filter lists version: eBlockerOS 3.0.2 filter list version 2024-01-22-10-15-04
- eBlocker network mode (auto, individual or expert): individual
- eBlocker network settings (IP, mask, gateway): 192.168.178.83, 255.255.255.0, 192.168.178.1
- Which devices runs DHCP server? Router/external, eBlocker or client fixed IP? On Fritzbox the DHCP server is deacivated. If I go to eBlocker > Network > Network Mode > Edit it shows "individual settings" being activated and "In this mode, the eBlocker assigns the IP addresses in the network."
- IPv6 disabled for client/network? Yes. Disabled.
- eBlocker DNS firewall settings: eBlocker used as DNS firewall is activates, as redommended. External DNS servers is activated with addresses 1.1.1.1 and 9.9.9.9
- Client network settings (IP, mask, DNS, gateway): 192.168.178.59, 255.255.255.0, 192.168.178.83, What means "gateway"?
- Whether eBlocker’s https integration is enabled for client: Yes, HTTPS is enabled.
- Client browser and OS version (i.e. FireFox 80.1 running on macOS 13.4): Firefox 121.0.1 on macOS 12.7.2
- Additional non default Blockers enabled? (like DuckDuckGo, Consent-Blocker, custom lists etc.): none
- HTTPS Auto Trust App enabled? Yes.
- Exact way or a link / screenshot to reproduce the issue: Up from several days before christmas until I have switched off IPv6 on eBlocker on several mornings not device within the WLN could connect to the internet until eBlocker was being restarted.
- If VPN or Tor is enabled for the client in eBlocker (and which VPN provider you are using): No
- Are automatic updates enabled? Yes
- Please use a meaningful title & description other users with same issue would enter as search term: Hopefully I did already.
On the macOS device please
- Run the eBlocker Doctor (Settings> Doctor)and the Function Test (in device Dashboard) post screenshots of both.
In Settings > Doctor > expert mode "The eBlocker itself cannot reach the IPv6 Internet via ICMPv6/ping." has a red alert. Everything else is marked green.
- Run a Traceroute while the device has Internet and post screenshot of the result (see here).
~ % traceroute 1.1.1.1 traceroute to 1.1.1.1 (1.1.1.1), 64 hops max, 52 byte packets 1 dnscheck.eblocker.org (192.168.178.83) 2.151 ms 2.872 ms 3.301 ms 2 fritz.box (192.168.178.1) 2.461 ms 2.142 ms 1.865 ms 3 * * * 4 188.111.213.38 (188.111.213.38) 10.090 ms 188.111.213.40 (188.111.213.40) 9.427 ms 10.263 ms 5 * 88.79.25.24 (88.79.25.24) 9.896 ms 88.79.24.20 (88.79.24.20) 10.170 ms 6 92.79.214.204 (92.79.214.204) 9.636 ms 92.79.214.202 (92.79.214.202) 10.041 ms 9.825 ms 7 145.254.2.51 (145.254.2.51) 14.103 ms 13.544 ms 145.254.2.49 (145.254.2.49) 13.470 ms 8 cloudflare.bcix.de (193.178.185.17) 15.071 ms 145.254.2.51 (145.254.2.51) 13.807 ms 13.376 ms 9 one.one.one.one (1.1.1.1) 12.344 ms cloudflare.bcix.de (193.178.185.17) 14.112 ms 13.565 ms
- Please repeat step 2 once Internet is down on the device and also post screenshot here.
Hmm. How can I make the Internet down only for my own device without disconnect all the other devices from Internet as well?
Very good 👍 Thanks for the comprehensive info and your great collaboration! That helps a lot 🚀
Hmm. How can I make the Internet down only for my own device without disconnect all the other devices from Internet as well?
Sorry for not being clear: I meant to run the traceroute once the issue has occurred (and you can not reach the Internet).
Would you please additionally run nslookup www.eblocker.org (now - and after the issue occurs) and share results.
Actually, I suspect just the DNS servers are unreachable (but the Internet connection is fine) when the error occurs. Could you please check everything is as marked in the screenshot and check server reliability again when the issue occurs.
We'll see more clearly after the error occurs and you run the traceroute and nslookup.👍
THX!
Sorry for not being clear: I meant to run the traceroute once the issue has occurred (and you can not reach the Internet).
I'll do it. But currently the Internet connection seems to be stable.
Would you please additionally run nslookup www.eblocker.org (now - and after the issue occurs) and share results.
~ % nslookup www.eblocker.org Server: 192.168.178.83 Address: 192.168.178.83#53 Non-authoritative answer: Name: www.eblocker.org Address: 174.138.100.168
Actually, I suspect just the DNS servers are unreachable (but the Internet connection is fine) when the error occurs. Could you please check everything is as marked in the screenshot and check server reliability again when the issue occurs.
Here 9.9.9.9 is "slow" "high"
We'll see more clearly after the error occurs and you run the traceroute and nslookup.👍
I am waiting for the next Internet blackout. 😉
I would re-enable IPv6 at eBlocker in the night from Friday to Saturday or in the night from Saturday to Sunday and, if Internet connection will being interrupted again, forward to you the traceroot and nslookup reports, okay?
@facebita Please don't make any changes to the setup discussed above until advised.
The possibility of IPv6 (or eBlockerOS 3) is causing your "blackout" is indeed very low. But switching IPv6 back on will act counter productive for drilling down to what's happening in your network.
Please rather reboot eBlockerOS (via the settings) and run the commands (traceroute/nslookup) before and after the reboot (if that cures the "blackout").
Again, I rather suspect an external factor (as your provider's routing to the DNS servers) being the culprit here. We'll find out jointly 👍
Last: Could you please double check you are not resolving DNS via Tor. This can cause the same "blackouts" if the selected Tor node has routing issues:
THX!
@facebita Just checking back if the "backouts" you were facing "almost every night" have occurred in the past week again?
As said, you might rather want to check your DNS server availability as your "blackouts" are very probably not related to eBlockerOS 3 at all.
THX!
Just checking back if the "backouts" you were facing "almost every night" have occurred in the past week again?
I did not have any backout after I have switched off on January, 23th, the IPv6.
Regarding your foregoing question: I never had enabled DNS resolving via Tor.
@facebita Thanks for your feedback. Just as a counter proof: Please switch IPv6 back on. I bet it's not not related at all - but time will tell. 👍
Please don't forget to run nslookup/traceroute if the issue occurs to find out the real cause...
THX!
No interruptions did happen. Since I have switched on again IPv6 my eBlocker and my internet connection work absolutely without no complication. Thanks a lot for your support.
@facebita Again: Perfect👍 But you have not changed anything 🤔
Nevertheless, next time you get a "blackout", please check the external DNS servers for availability in the DNS Firewall. I'm very sure they were the cause of trouble.
THX!