Hi, I lost access to my eBlocker (Raspberry Pi) after changing network settings to automatic reception of an IP-address (NOT to eBlocker as DHCP-server!)
The problem remains even after complete new installation of eBlocker-OS on new SD-card.
Viewed through Fritzbox 7590 (192.168.178.1) the eBlocker-IP-adresses seem to change by themselves: From "192.168.179.5" (instead 192.168.178.x while an IPv4-address is shown as 192.168.178.61), then it changes back to 192.168.178.1 (same as Fritzbox) - so it looks like a conflict of IP-Addresses between eBlocker and Fritzbox (?)
My settings (private relay etc.) are all correctly set.
The problem already turned up with the old eBlocker box, when all of a sudden the eBlocker-address was shown as 192.168.178.1 = Fritzbox address (with Fritzbox as DHCP-server) with loss of access to the dasboard. Then I bought a raspberry Pi, installed eBlocker OS, at first all seemed to work well, I assigned a fixed (unique) IP-address to eblocker (192.168.178.2), but after changing the network settings of eblocker back to automatic DHCP-address reception the "192.168.178.1"-problem returned ...
Is eBlocker working at all under these circumstances??
@thomasr There is no conflict with the Fritzbox. It's rather a bogus configuration.
Make sure to run eBlocker in Individual Network Mode, follow the wizard closely and disable the DHCP on the Fritzbox when the wizard says so.
Then reboot all devices to catch the new IP from eBlocker's DHCP. All IPs will stay the same btw.
THX!
Thx - but how shall I change the configuration without access to eBlocker?
@thomasr Set your iOS to a fixed (manual) IP address, i.e. 192.168.179.88 and access the eBlocker with the (accidentally wrong configured) IP: http://192.168.179.5
Or use the emergency IP as described here: https://eblocker.org/en/docs/accessing-the-eblocker-settings/#8-toc-title
THX!
I managed to access eBlocker through different ways (manual IP-address of the client, emergency IP), but I seem to be trapped in a loop as any input ends up at the setup assistant which always requires an internet connection to continue, which cannot be established at this moment of configuration (?)
@thomasr Change the network interface of eBlockerOS to match your network otherwise eBlocker can not communicate to the internet. Thus cancel the setup and configure 192.168.178.x as the network (same as the Firitzbox)
If you are not a network expert and all this is too confusing, I'd rather start of anew with a fresh image SD Card. The setup just works if you follow the Individual Network Mode setup instructions. DO NOT CHANGE eBlocker's IP address or the IP of your Fritzbox in this process, as this change has brought you into the situation.
THX!
If network settings are "messed up", you can also do a factory reset via the interface. No need for a new SD install, to my knowledge.
Easier might be to set eBlocker's IP, say to 192.168.178.100, so it can be reached in your network. When you set eBlockerOS to individual settings (use ...178.1 as gateway), it should work as desired when you switch off DHCP on your router. Make sure to change iOS back to DHCP and reboot all devices to fetch the new setting from eBlocker DHCP.
Hope this is not confusing you too much. It's basically different ways to correct the 179.x misconfig.
Good luck 👍
Hi @thomasr,
are you running eBlockerOS 3.2.3?
I am a bit confused about the IP ranges in your network.
By default the usual main network of the Fritzbox is 192.168.178.0, while the guest network is 192.168.179.0. Please make sure the LAN port that the eBlocker is connected to is not configured to be in the guest network. (I think only LAN 4 can be configured that way.)
Hi! Yes, I am using 3.2.3. Meanwhile I managed to reinstall eBlockerOS on my raspberry Pi, and for about 2 days after the "recovery" everything worked fine, eblocker-Test was fully "green", no problems. This morning, however (something might have happened overnight???), eblocker seems to "capture" the Fritzbox-IP (192.168.178.1) again (in automatic network mode, eblocker's address being shown as
IP 192.168.178.187), which again completely blocks the client connection to the LAN/network (internal and external). So again the only option is to pause or disconnect eBlocker ... meanwhile - after hours and hours, I do not know what else to do ... (and - sorry - I am pretty pissed off ...)
Make sure to run eBlocker in Individual Network Mode, follow the wizard closely and disable the DHCP on the Fritzbox when the wizard says so.
I'm not sure which part of the instruction is unclear. But I totally understand you are "pissed off" if you do not follow instructions. Same here.
To cure unhappiness: follow the instructions given and all gonna be fine.
THX!
@thomasr to me it looks like an IPv6 issue. In your screenshot I can see that eBlocker has a public IPv6 address. Your client device might go directly to the router instead via eBlocker for IPv6 so the connection test in the Dashboard shows errors. (eBlocker announces itself as an IPv6 router with higher priority, but the client can sometimes prefer the router directly, even if it has lower priority.)
You could try to disable IPv6 in the Fritzbox at Internet / Zugangsdaten / IPv6 / IPv6-Unterstützung.
Regarding the "capturing" of the Fritzbox' IP: In auto-mode this is normal, because eBlocker is not DHCP and so it cannot set its own IP as the gateway for the clients. It has to spoof the 192.168.178.1 address.
To have the most stable setup I would suggest:
- Disable IPv6 at the Fritzbox
- Switch eBlocker to individual network mode, as Random suggested.
Hi folks, and sorry random, I apologize!! Just to make sure I understood random right - is it this what you suggest by "individual network mode"? I've actually tried this before (DHCP by eblocker, disabled in Fritzbox), but it did not solve any problem ...
or do you suggest to touch this:
I have now also disabled IPv6 in the Fritzbox as described (plus IPv6-beta in the eblocker), but this alone does not solve the problem either ...
Yes to your first screenshot. This is meant by "Individual Network Mode".
No to your second screenshot: The DNS server needs to be set to "eBlocker" (not to external). Your current configuration will not work properly (as already discussed here: https://eblocker.org/community/bugs-features/error-connection-failed/#post-8680 ). And also to repeat myself: Turn off the DNS server in your router once eBlocker's DNS server is enabled.
I'm really happy to help you get going and repeating myself - but easiest is to just follow the instructions. Reading and following the instructions step by step is key to success and helps reduce frustration. You might want to give it a try...
THX!
@random: I followed your instructions the last time already, and now for a second time again. The starting point was this:
the setting results come here:
As FritzBox is configured as a dependant IP-client it loses the login data to establish the internet connection to the provider, which in turn eBlocker cannot provide as there is no option to feed it with the internet login data of the provider (in my case O2).
So following your instructions ends up in no connection to the internet.
So I reconfigured FritzBox and eBlocker to "normal" = Fritzbox as DHCP-server and eBlocker as dependent client. The Internet connection is established and all seems to work well for the moment - as before (!):
Last time I had reached this point I assumed to have solved the problems. It took just 2 days for them to return (maybe by an overnight-update? I'm a donor!). So let's wait and see what happens (when eBlocker spoofs the gateway IP-address?!). I guess I'll have the same problems again.
Is there a possibility that eBlockerOS contains a bug? I have been using eblocker in the actual configuration ever since it came to market and have never had any problems until some months ago ... in the attempt to solve the issues I damaged my well working old Box without achieving any progress with a raspberryPi either.
As FritzBox is configured as a dependant IP-client it loses the login data to establish the internet connection to the provider, which in turn eBlocker cannot provide as there is no option to feed it with the internet login data of the provider (in my case O2).
Well, I fear you might got mixed up between using DHCP for your Internet(!) connection (which is a must) and disabling the internal LAN(!) DHCP server on the Fritzbox.
To make it clear: do not touch the Internet settings of the Fritzbox! Never ever!
Rather disable the Fritzbox DHCP server in you LAN (Heimnetzwerk) like this:
Sorry for the confusion.
And just for your background: eBlockerOS 3 and 4 run absolutely stable without any issues for tens of thousands of users. There are no know bugs.
Hope now the skys clear up on your side.
THX! Yes, indeed I did not realize the seperate IP4 DHCP config options ... so now I changed the system successfully to individual settings. But as a result as to eBlocker function I got this (while all the Firefox browser anti-tracking settings, DNS by HTTPS etc. are disabled!):
DNS is configured like this:
So ... ??
I do not know how - but after some hours the issue disappeared by itself
I hope this will last ... and many thx for bearing with me
@thomasr Closely reading what we suggest is absolutely key for success:
Then reboot all devices to catch the new IP from eBlocker's DHCP. All IPs will stay the same btw.
BTW: That's exactly what the error message says "Your device uses a cached DNS response". After a reboot the DNS cache gets flushed - or after waiting some time.
And if you just follow closely what Boris said, the IPv6 message will also vanish.
To have the most stable setup I would suggest:
- Disable IPv6 at the Fritzbox
Nobody said to disable IPv6 in eBlockerOS and I'm not sure why you felt like changing it. 🤷
I'd suggest to enable IPv6 in eBlockerOS as this is a pre-caution to also filter IPv6 traffic if the router changes or disabling IPv6 in the router did not succeed (like in your case).
THX!