Hi,
I tried to test PDFW, but PDFW never shows any entries. Also when I refresh or generate traffic.
I also tried the Chromium Browser without success.
Additionally when I refresh the page the PDFW is switched off!
Please run an eBlocker Function Test (in the Dashboard) and post results.
Have you tried enabling the PDFW for other devices (via the Remote Dashboard)?
Post results here.
THX!
Additionally when I refresh the page the PDFW is switched off!
Ups. Just saw this additional line.
Can you please also post your environment as described here ( https://eblocker.org/community/announcements/before-posting-here-please-read/#post-117) to avoid question ping pong…
THX!
Below more information about the problem:
@tuxxer Obviously you‘ve overseen my question:
Can you please also post your environment as described here ( https://eblocker.org/community/announcements/before-posting-here-please-read/#post-117) to avoid question ping pong…
From my gut feeling I‘d say that IPv6 has not been disabled - but that‘s a pure guess without the info asked above.
BTW: your screenshots show that eBlocker / your device is not properly set up, so you can‘t expect the PDFW to work properly either…
Also you might want to answer my other question (above) about PDFW on other devices. Please understand it‘s no fun to support you if you don‘t answer the question being asked!
THX!
- Hardware you use for running eBlockerOS
Raspi4 4GB
- eBlockerOS version as well as filter lists version
e-blocker 2.7.4
- eBlocker network mode (auto, individual or expert)
Individual. The only mode my router is working.
- eBlocker network settings (IP, mask, gateway)
IP: 192.168.1.106
Network mask: 255.255.255.0
Router: 192.168.1.1
- IPv6 disabled for client/network?
IPV6 is deactivated on the router for the whole network.
- eBlocker DNS firewall settings
DNS via TOR.
- Client network settings (IP, mask, DNS, gateway)
Device: 192.168.1.105
eblocker: 192.168.1.106
Gateway: 192.168.1.1
- Whether eBlocker’s https integration is enabled for client
https is enabled!
- Client browser and OS version (i.e. FireFox 80.1 running on macOS 13.4)
Firefox 91.0.with Firejail on Fedora 34.
- Additional non default Blockers enabled? (like DuckDuckGo, Consent-Blocker, custom lists etc.)
Consent & cookie banner: enabled
DuckDuckGo: disabled
Tracking blocker: enabled
- HTTPS Auto Trust App enabled?
Yes
- Exact way or a link / screenshot to reproduce the issue
Please see my first posting!
- If VPN or Tor is enabled for the client in eBlocker (and which VPN provider you are using)
No VPN or Tor activated!
- Please use a meaningful title & description other users with same issue would enter as search term
I hope this helps to understand the problem!
- Client network settings (IP, mask, DNS, gateway)
Device: 192.168.1.105
eblocker: 192.168.1.106
Gateway: 192.168.1.1
I‘m missing the info if eBlocker is doing DHCP or your router or the client is set up manually. 🤔
If manually set up: the Gateway of the device must be set to eBlocker‘s IP address in individual mode. Your router‘s IP must be set as Gateway eBlocker. So, in the above quote, make sure 192.168.1.106 is set as client Gateway.
THX!
My eblocker is in inidividual mode.
and changed the gateway to 192.168.1.106. Then PDFW is showing a list of pages.
But then another problem is popping up. If I want to access any page outside my own network, i.e. eblocker forum it doesn´t work.
By the way the function test is always showing the same results!
After switching back to gateway 192.168.1.1 I can access internet pages and after a while the PDFW shows values suprisingly. But the question for me is if eblocker is really working how it should be, because of the results in the function test.
changed the gateway to 192.168.1.106.
Buddy, PLEASE read what I say. Change the Gateway of your CLIENT to eBlocker‘s IP. eBlocket‘s Gateway need to stay as it was (set to your Router'S IP)!!
Background: To ALL your clients eBlocker needs to be setup as Gateway. And in eBlocker your Router‘s IP is set as Gateway. It‘s not that complicated… just do it!
To sum up: Your network setting is simply messed up. Unless this is fixed eBlocker is of no use - and so the PDFW is. Please follow exactly what I said to get it straight…
THX!
So if I understand you the correct way I cannot use DHCP on my clients. Instead I have to configure it the manual way like this
To be honest I am a little bit puzzled at the moment!
@tuxxer What‘s the eBlocker Function Test results with the client setting above?
If all checkmarks are green PDFW will work…
So if I understand you the correct way I cannot use DHCP on my clients.
No, thats incorrect. Of course you can use a DHCP server (for example eBlocker‘s DHCP server), but you keep missing my questions:
You probably didn‘t disable DHCP on your router, when enabling Individual Network settings, which is mandatory s. here https://eblocker.org/docs/eblocker-individual-network-setting/
THX!
I am worried some advanced features are enabled (like DNS via Tor, ATA, Consent Blocker) but the eBlocker is not even set up properly.
First you need eBlocker to work (all check-marks green in the test) and get it in a defined state.
I recommend a factory reset and then follow the Start here docu: https://eblocker.org/docs/setup-instructions-start-here-eblocker-beginners/
This document need to be followed word by word (ie. if it reads to disable your router’s DHCP, the step cannot be skipped).
See pic to understand the routing: 
All clients talk to eBlocker (=eBlocker is Gateway for clients), only eBlocker talks to Internet Router (=Router is Gateway for eBlocker).
Usually this is setup automatically if instructions for Individual Network Mode are followed closely. Then eBlocker runs the DHCP server (must be the only DHCP server) and there is no need to setup each client manually.
Once your network is setup correctly, you could take it from there and enable the advanced stuff, like PDFW, DNS via Tor etc. Switch it on - one by one - and as needed only, not just because it can be switched on. 😉
Make sure you know what you do, and why! Same as with all tools: Don't use a drill to dig the garden 😜
At the end eBlocker is the best tool for your privacy, I'm aware of, but it needs to be handled right. The PDFW is great by the way - but a dangerous toy for IT novices.
The hint with the factory reset was good. Afterwards I managed to get it up and running with a function test that confirms that everything is working fine. First it even worked in automatic mode, but just one day. After the nightly restart of the connection the function test once again complained. Then I set it to manual mode and it works fine. Let´s keep our fingers crossed that it stays this way.
PDFW is nevertheless not working. If I activate it can wait for some minutes it does not show any values. Also pressing the refresh button does not change the situation, also when I created some internet traffic inbetween. If I refresh the whole page I even get the situation that PDFW immediately gets deactivated.
Also you might want to answer my other question (above) about PDFW on other devices. Please understand it‘s no fun to support you if you don‘t answer the question being asked!
@tuxxer If you want help, it‘s a good idea no to drive supporters mad by continously ignoring important questions. I give up here. Good luck.
THX!
As you did a factory reset please share tech infos from readme again.
Also use the Remote Dashboard for a different device to check PDFW on another device, as @random asked for several times…
After the nightly restart
I‘m not sure what you are talking about. What is restarting?
From what you describe (today green, red tomorrow) I rather suspect you have two DHCP servers in the same network running. See https://eblocker.org/docs/dhcp-server-there-can-only-be-one/
Post tech infos and be more verbose/clear to get further help.
Indeed I had two DHCP servers running. After deactivating the DHCP server on the router the eblocker function test was successful (everything green!).
Nevertheless PDFW doesn´t work. If I switch it on and want to refresh nothing happens. Even after 5-10 minutes. If I refresh the Dashboard page PDFW is automatically switched off. I tried it on two different machines and they are behaving the same way.
I suspect the device(s) you are trying to analyze is/are not enabled for eBlocker protection (Settings>Devices).
But without current infos about your setup (after your improved configuration) this is just a guess. Consider sharing your tech environment again, run a traceroute to see that the device is covered by eBlocker (see docs).
We always love to find bugs in the beta but as you are the only user reporting this behavior, chances are high it‘s a setup/usage issue… which can be fixed, as all the other setup issues discussed above 😉
Nevertheless PDFW doesn´t work. If I switch it on and want to refresh nothing happens. Even after 5-10 minutes. If I refresh the Dashboard page PDFW is automatically switched off.
It's very strange that setting the PDFW switch does not work. If you open the browser console in Firefox on the dashboard page, do you see any JavaScript error messages?
I checked it and the device is accessing the internet via eblocker. I also tried traceroute (traceroute 9.9.9.9) with the following result:
traceroute 9.9.9.9
traceroute to 9.9.9.9 (9.9.9.9), 30 hops max, 60 byte packets
1 _gateway (192.168.1.106) 4.091 ms 4.081 ms 4.072 ms
2 192.168.1.1 (192.168.1.1) 4.065 ms 4.044 ms 4.024 ms
This confirms that it acceses the internet via eblocker (192.168.1.106).
The function ttest is also OK:
The intital problem was that eblocker was running a DHCP server as well as the router. After deactivating routers DHCP function test got positive.
@tuxxer Is the eBlocker DNS firewall enabled? (Settings>DNS Firewall)
Please run „nslookup www.eblocker.org“ and post results.
Unfortunately your screenshot only shows one line of the browser console (the yellow line starting with „Warning“). Please resize window/lower frame, click tab „console“ or copy/paste console output here (the other infos are not relevant).
Are you using any browser plugins? Have you tried a different browser?
THX!
nslookup www.eblocker.org
;; connection timed out; no servers could be reached
and please find attached a bigger picture of the console of a random page:
List of active Firefox extensions:
Is the eBlocker DNS firewall enabled? (Settings>DNS Firewall)
An answer would be great...
console of a random page:
The console of the eBlocker Dashboard please. Read @bpr's post! A "random" page is not helpful.
nslookup www.eblocker.org
;; connection timed out; no servers could be reached
This makes no sense to me. Did you type the command on the Linux console/command line? BTW: Without DNS you can't reach any domain on the Internet... 🤔
The question is, which server acts as DNS in your network. Running nslookup shows the authoritative DNS server.
As you are using Linux and seem to speak German, you might want to learn more here: https://geek-university.com/linux-deutsch/nslookup-befehl/
Also retry the PDFW with all plugins disabled. You seem to have a mix of plugins that are irrelevant when using eBlocker - and interfere with each other... (ie. ClearURL, I don't care about cookies etc.)
THX!
I revised my approach when it comes to nslookup (I hope that I applied it now in the right way!)
nslookup
> www.eblocker.org
Server: 127.0.0.53
Address: 127.0.0.53#53
Non-authoritative answer:
Name: www.eblocker.org
Address: 174.138.100.168
The DNS Firewall is activated:
Console for eblocker dashboard:
If I deactivate all the Firefox extensions the console for the Dashboard is completely empty, but PDFW is still not working.
List of active Firefox extensions
Wow. There are people who mix diesel, gas and coal to fuel their new car to make it go faster. Usually they have no clue how an engine works but a dangerous half knowledge and believe more helps more.
To me it seems we have a very similar case here. STOP mixing fuels, RTFM and everything will work fine, if you want my option.
This thread is really ridiculous. Starting from a completely misconfigured eblocker, to two DHCP server and now mixing fuels. Insane trying to help here @random. Good luck anyway. 😜
@tuxxer: one last hint. Just make sure DNS is set to eBlocker‘s IP on your misconfigured linux. You need basic network support not eblocker support!!
dangerous half knowledge
👍🤣🤣
Even reading & writing is obviously @tuxxer’s problem as nslookup shows 127.0.0.1:53 for sure. Stupidity can grow strong. Proof is here 🤪 REALLY funny to read all this…
@tuxxer Go disable pi-hole leftovers and get professional help for your network. eBlocker is no problem, but you are!
You need basic network support not eblocker support!!
I agree, @tuxxer you‘ve messed up your network by dangerously „mixing fuel“ (as @subscriber calls it). Adding bicycle tires to a Ferrari and using coal for fuel would cause unpredictable results. Same here.
Even this is not the „help for messed up networks forum“, here are my last words on this:
- Set eBlocker to Individual Network mode and make sure it runs the only DHCP server in your network.
- Make sure all clients are set to use DHCP for IP and DNS configuration! (see @Machmut‘s comment…)
- Disable everything you have „accidentally“ added like plugins, local DNS server (probably pihole =„bicycle tires“) and other unwanted stuff.
If you can‘t get it running, get help from a network specialist - or read a book how IP networks work.
Summing up: ALL your issues are caused by a misconfigured network. eBlocker and PDFW just run fine. But a Ferrari with bicycle tires can not run properly either.
THX, I‘m out!
Just to sum up for less tech geeks: You are obviously running a local DNS server on your linux which handles the DNS request. Thats why the PDFW is not seeing any DNS requests, hence the analysis stays empty. So this is not a malfunction of the PDFW at all but rather the cause of your very „individual“ setup.
BTW: This is a rather awkward setup used by tech professionals who know what they are doing. Seems that everyone posted here is pretty unhappy this turned out to be the cause, since a tech professional would have mentioned this in the first place already…
Here the requested outcome for: resolvectl status
Global
Protocols: LLMNR=resolve -mDNS -DNSOverTLS DNSSEC=no/unsupported
resolv.conf mode: stub
Link 2 (wwp0s20u4i6)
Current Scopes: none
Protocols: -DefaultRoute +LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported
Link 3 (enp0s25)
Current Scopes: none
Protocols: -DefaultRoute +LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported
Link 4 (wlp3s0)
Current Scopes: DNS LLMNR/IPv4
Protocols: +DefaultRoute +LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported
Current DNS Server: 192.168.1.106
DNS Servers: 192.168.1.106
Link 5 (virbr0)
Current Scopes: none
Protocols: -DefaultRoute +LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported
In the meantime I set up a new test system (Manjaro). On that system PDFW works.
Thanks to all who gave input!
OK, your eBlocker is 192.168.1.106 ... then eBlocker if for your Clients Gateway and DNS
You have set eBlocker to "Individual" Network Mode !?
So in eBlocker you have to set your Router (192.168.1.1) as Gateway, do you so?
You send the Tracerouet result above, if so it should be running, no problem with eBlocker.
Tested related Setup
PIO78
@pio78 I appreciated your move to find the cause of error, but consider @tuxxer is constantly changing his setup (obviously applying half knowledge), but not sharing what he actually changed, even after being nicely asked several times. Just see above for this support nightmare. The worst I had in 20 years in business!🤮
You easily see that nslookup output was based on a different setup than the output of resolvectl. Again with undisclosed changes. This makes support soo enjoyable… ☹️
The only thing we should care of: he is finally happy, and eBlocker PDFW was not the cause of error, but „someone“ sitting in front of his screen. 🤪😉
Let‘s not waste more time here and keep fingers crossed @tuxxer is not changing his setup again…
THX!