I have quite big problems with eBlocker and temporary complete connection problems to Google News (Android app) and Google Discover (also Android, the Chrome page you get when you open a new tab).
During the day it is almost the rule, rather than the exception, that no content is delivered or errors occur. If I switch to mobile (5G) and bypass my WLAN, it works immediately. If I switch off eBlocker for the device, it also works.
If I have bypassed eBlocker for a short time, I refresh the Chrome Discover page and then switch back to WLAN, then the refreshes work for a while (each refresh then brings new news tiles). If I then check it again later in the day, it no longer works.
The only suspicion I have is that a Bearer Token Refresh may be required. That would explain why it works for a while and then at some point no content is delivered. But then why don't I see anything in the log that the apps are trying to refresh a token somewhere (and failing?)
I don't have any manual lists, and I don't have any configuration changes throughout the day. But sometimes it just works again. But after a while, it doesn't work again.
I have checked the HTTPS traffic, nothing appears there. If I do a manual check, the log tells me that newsstand.googleusercontent.com was detected (and the eBlocker rule is disabled). So actually ok.
I haven't had this problem for long. However, I also don't understand how I can narrow down the problem further.
Sometimes I get the same problem with other websites, but I use Discover and Google News the most.
My network mode is Individual, which has been set up and working for weeks. DHCP is, of course, switched off on the router. I only do HTTPS blocking on one PC and one smartphone. Certificates are installed, and it works for most applications and websites. I work around known problems with banking apps with the mobile connection anyway.
I realize that this is poking around in the dark. That's why I need instructions on how I can check what keeps breaking.
I also noticed that it fails google.com search on Android smartphone with timeout. But Google Maps works. On the other hand, Google photo suggestions does not work.
I found out that the problem only happens on a device with HTTPS blocking: Only on my Android device. The Windows PC can access the Google stuff at the same time without any problems.
All possible settings of the blocker (deactivated bit by bit) did not help. Only when I completely deactivated the eBlocker protection under Devices on the smartphone was Internet access undisturbed.
Btw, if I only deactivate HTTPS blocking for the smartphone, I no longer have any network access at all. How can I change the device (for testing) so that only simple domain blocking is active?
So it is eBlocker in combination with the smartphone only for certain Google services (not all).
@josch Could you please share the exact URL you are accessing (no Android device to replicate the issue here).
Is the issue happening on other (non Android devices) as well?
Could you please start the Blocker Analysis tool (Settings>Blocker>Analysis Tool) before accessing the page and keep the recording running until the error occurs. Then share results here.
Please also share details of your IPv4/IPv6 settings. (see https://eblocker.org/community/announcements/before-posting-here-please-read/#post-117)
What's the result of visiting http://ipv6.eblocker.org (with your Android)?
Last: If there is a browser console accessible on Android/chrome, please share the console output after visiting the page and once the issue occurs.
THX!
Seems we posted at the same time. 👍😉
Here are the answers for your questions:
How can I change the device (for testing) so that only simple domain blocking is active?
See https://eblocker.org/en/docs/devices/#7-toc-title
Choosing Domain Blocker for the device will deactivate HTTPS.
So it is eBlocker in combination with the smartphone only for certain Google services (not all).
All devices (including Android) should work seamlessly with eBlockerOS (maybe after some configuration).
BTW: Have you enabled the Trusted App for Google? (Settings>HTTPS>Trusted Apps - type "goog" in the search field).
THX!
Hi @random
Could you please share the exact URL you are accessing (no Android device to replicate the issue here).
E.g. https:[slash][slash]google[dot]com/search?q=test
(timeout)
Is the issue happening on other (non Android devices) as well?
No.
I have only one Android Device with https blocking. The other device I cannot change to https blocking. And on my Windows PC (with https blocking), the URL is working. So, it's individual to the specific device.
Could you please start the Blocker Analysis tool (Settings>Blocker>Analysis Tool) before accessing the page and keep the recording running until the error occurs. Then share results here.
As mentioned, I get nothing. It's complete empty.
Please also share details of your IPv4/IPv6 settings. (see https://eblocker.org/community/announcements/before-posting-here-please-read/#post-117)
eBlocker: 192.168.2.172 / 255.255.255.0
Gateway: 192.168.2.1
Device: 192.168.2.176 (static, with private MAC - assigned by Android 14)
2003:d5:d72e:88dd:e0ad:10ff:fe5b:f50e,
2003:d5:d72e:88dd:f059:3945:20d8:6df9,
fe80::e0ad:10ff:fe5b:f50e
DNS: 1.1.1.1 & 9.9.9.9
Network mode is individual, router DHCP is deactivated
No extra Blocker lists (only the defaults), no own blocker lists.
HTTPS Auto trust is enabled, but only a single entry (public transportation API, I guess)
No VPN/Tor
No automatic updates, but I updated manually (since the problem occurred)
Dashboard functional test (from Android device): All green
Doctor: all green, except License
What's the result of visiting <a class="wpforo-auto-embeded-link" href=" removed link " target="_blank" rel="noopener"> removed link (with your Android)?
This is working. "You have reached this server via IPv6" ... ip address"
Last: If there is a browser console accessible on Android/chrome, please share the console output after visiting the page and once the issue occurs.
Because I get time-outs, nothing to see.
I'm pretty sure, the Apps (Chrome with Discover and Google News) gets also internally time-outs. Google News shows only the old cached content. Discover in Chrome shows an error. Chrome google.com/search shows a timeout.
I can immediately fix it, by deactivating the complete blocking for this device. Btw. I tried a "reset" of the device in eBlocker, but the issue continues to occur.
Best regards, Josch.
Have you enabled the Trusted App for Google? (Settings>HTTPS>Trusted Apps - type "goog" in the search field).
Yes, it's enabled.
See https://eblocker.org/en/docs/devices/#7-toc-title
Choosing Domain Blocker for the device will deactivate HTTPS.
Ok, I already tried it, that didn't help.
best regards
Josch
Hello @random
I have more details. I installed the fantastic app PingTools to get an understanding of what happening.
With activated eBlocker:
Any website, I can access (if eBlocker is activated for my device) goes via traceroute over dnscheck.eblocker.org (local), speedport.ip (local - my router), p3e9bf7d5.dip0.t-ipconnect.de (my provider), ...
All the websites with issues (like google.com, posteo.de, ...) go directly over p200300d5d72e88ddda3addfffeb8fb92.dip0.t-ipconnect.de, then p200300d5d72e88dd628d26fffe849426.dip0.t-ipconnect.de
eBlocker is deactivated for the device:
google.com, posteo.de, ... go directly over p200300d5d72e88ddda3addfffeb8fb92.dip0.t-ipconnect.de, then p200300d5d72e88dd628d26fffe849426.dip0.t-ipconnect.de without issues
So, two questions (and I don't know if you can answer both):
- Why do some domains run over a wrong route?
- Why does the route via p200300d5d72e88ddda3addfffeb8fb92.* not work when eBlocker is active?
Btw., whitelisting of posteo.de is not working - but this is obvious now.
The second question is for my understanding. The first question goes in the direction of the root cause. But idk, if someone can help me 🙁
Best regards
Josch
@josch I've asked you a bunch of questions. Unfortunately none got answered. Still waiting...
Of course yes...
Missed I something?
And I found another thing with my traceroute checks:
With activated eBlocker:
Websites with IPv6 (like google.com, posteo.de, ...) go directly over p200300d5d72e88ddda3addfffeb8fb92.dip0.t-ipconnect.de, then p200300d5d72e88dd628d26fffe849426.dip0.t-ipconnect.de
That means, my android device routes IPv6 server over p200300d5d72e88ddda3addfffeb8fb92.dip0.t-ipconnect.de
Pure IPv4 server goes all time over dnscheck.eblocker.org (local)
But I found working IPv6 websites (routed over p200300d5d72e88ddda3addfffeb8fb92.dip0.t-ipconnect.de). E.g. strato.de is working with my android device, but not posteo.de
However, the ipv6 blocker is enabled:
IPv6-Adressen des eBlockers
I'm still fighting...
I found out that after a new WLAN connection, the ipv6 gateway points to fe80::1 (which is the Telekom Speedport router).
But DNS1 points to the eBlocker device (IPv6 address) and DNS2 also to eBlocker (IPv4 address).
The question is, why does the Android device receive the address of the telecom provider's router? Yes, the router offers Wi-Fi, but eBlocker should be the correct gateway.
@josch Thanks for all your posts. Honestly it's quite a bit of information overload. Just focusing on answering the open questions would be easier...
Nevertheless, I repeat
Could you please start the Blocker Analysis tool (Settings>Blocker>Analysis Tool) before accessing the page and keep the recording running until the error occurs. Then share results here.
As mentioned, I get nothing. It's complete empty.
Well, you've mentioned the HTTPS analysis. I was asking for the Blocker Analysis (=different thing). Please read carefully!
Sorry, but I can't follow your explanations regarding the different routing via the various *t-ipconnect.de. What are these domains? Could you please share a screenshot of the full traceroute to www.eblocker.org in both cases.
I'm also not clear about your network topology. Are you using several WLAN access points? Please answer all the (network related) questions from the README FIRST to lift the fog.
Last: Is your Android phone using 3G/4G/LTE or other mobile protocols in parallel to the WLAN connection in your home? Then try flight mode (disabling mobile LTE but leaving WLAN active). Also worth a try: Connect your Android via eBlocker Mobile (using OpenVPN). Pretty sure the latter will solve your issue - but that would be a work-around. The core issue is some "special" network config in your home.
We'll see more clear after you've answered the questions fully.
THX!
Hi @random
Well, you've mentioned the HTTPS analysis. I was asking for the Blocker Analysis (=different thing). Please read carefully!
However, still nothing.
When I do a google.com search with "test" an ERR_TIMED_OUT is the result.
Sorry, but I can't follow your explanations regarding the different routing via the various *t-ipconnect.de. What are these domains?
Automatic generated subdomains by the Speedport router (the subdomain name contains the IPv6 address and the domains points to 192.168.2.1 = the router itself).
Architecture:
Smartphone and PC are eBlocker managed (https with certificates installed).
Please answer all the (network related) questions from the README FIRST to lift the fog.
eBlocker: 192.168.2.172 / 255.255.255.0
Gateway: 192.168.2.1
Android Device: 192.168.2.176 (static, with private MAC - assigned by Android 14)
2003:d5:d72e:88dd:e0ad:10ff:fe5b:f50e,
2003:d5:d72e:88dd:f059:3945:20d8:6df9,
fe80::e0ad:10ff:fe5b:f50e
DNS: 1.1.1.1 & 9.9.9.9
Network mode is individual, router DHCP is deactivated
No extra Blocker lists (only the defaults), no own blocker lists.
HTTPS Auto trust is enabled
No VPN/Tor
No automatic updates, but I updated manually (since the problem occurred)
Dashboard functional test (from Android device): All green
Doctor: all green, except License
Traceroute from Android Device to google.com with Wi-Fi (eBlocker activated for this device):
traceroute to google.com (2a00:1450:401b:808::200e), 30 hops max
Hop 1:
From p200300d5d72e88a0da3addfffeb8fb92.dip0.t-ipconnect.de (2003:d5:d72e:88a0:da3a:ddff:feb8:fb92), 5 ms
Hop 2:
From p200300d5d72e88a0628d26fffe849426.dip0.t-ipconnect.de (2003:d5:d72e:88a0:628d:26ff:fe84:9426), 6 ms
Hop 3:
*
Hop 4:
*
Hop 5:
*
Hop 6:
*
Hop 7:
*
Hop 8:
*
Hop 9:
*
Hop 10:
*
Hop 11:
*
Hop 12:
*
Hop 13:
*
Hop 14:
*
Hop 15:
*
Hop 16:
*
Hop 17:
*
Hop 18:
*
Hop 19:
*
Hop 20:
*
Hop 21:
*
Hop 22:
*
Hop 23:
*
Hop 24:
*
Hop 25:
*
Hop 26:
*
Hop 27:
*
Hop 28:
*
Hop 29:
*
Hop 30:
*
Traceroute complete: 30 hops, time: 13699 ms
Traceroute from Android Device to google.com with Wi-Fi (eBlocker deactivated for this device):
traceroute to google.com (142.250.203.206), 30 hops max
Hop 1:
From dnscheck.eblocker.org (192.168.2.172), 9 ms
Hop 2:
From speedport.ip (192.168.2.1), 8 ms
Hop 3:
From p3e9bf7d5.dip0.t-ipconnect.de (62.155.247.213), 9 ms
Hop 4:
From 217.0.197.233, 23 ms
Hop 5:
From 80.150.170.70, 23 ms
Hop 6:
From 192.178.109.243, 23 ms
Hop 7:
From 192.178.109.126, 22 ms
Hop 8:
From 209.85.252.214, 22 ms
Hop 9:
From 192.178.75.98, 31 ms
Hop 10:
From 192.178.83.132, 43 ms
Hop 11:
From 192.178.99.103, 42 ms
Hop 12:
From 209.85.252.109, 42 ms
Hop 13:
From waw02s22-in-f14.1e100.net (142.250.203.206), 42 ms
Traceroute complete: 13 hops, time: 6893 ms
Traceroute from Android Device to google.com with mobile connection (5G):
traceroute to google.com (2a00:1450:4001:82b::200e), 30 hops max
Hop 1:
*
Hop 2:
*
Hop 3:
*
Hop 4:
*
Hop 5:
*
Hop 6:
*
Hop 7:
*
Hop 8:
*
Hop 9:
From 2003:0:1304:800f::2, 53 ms
Hop 10:
From 2a00:1450:8037::1, 37 ms
Hop 11:
From 2001:4860:0:1::5013, 49 ms
Hop 12:
From fra24s08-in-x0e.1e100.net (2a00:1450:4001:82b::200e), 46 ms
Traceroute complete: 12 hops, time: 11290 ms
Over 5G and WLAN (without eBlocker) I can reach google.com.
Over WLAN (with eBlocker) the android device goes directly to the Speedport router and nothing comes back.
Last: Is your Android phone using 3G/4G/LTE or other mobile protocols in parallel to the WLAN connection in your home? Then try flight mode (disabling mobile LTE but leaving WLAN active). Also worth a try: Connect your Android via eBlocker Mobile (using OpenVPN). Pretty sure the latter will solve your issue - but that would be a work-around. The core issue is some "special" network config in your home.
- "Is your Android phone using 3G/4G/LTE or other mobile protocols in parallel to the WLAN connection in your home?"
- Yes, this is the android standard. WLAN and Mobile is activated
- "Then try flight mode (disabling mobile LTE but leaving WLAN active)."
- Now it's more worse. The WLAN shows an exclamation mark with limited internet. I guess a check with a Google service is not working anymore and Android tags the Wi-Fi connection. This means that some apps do not want to work from the start. Some websites work, others don't. The tracceroute is similar to the first route printed above. Only throw the both internal synthetic domains, nothing more.
- I deactivated the flight-mode again and now the WLAN is back without exclamation marks
- "The core issue is some "special" network config in your home."
- Maybe the router is incompatible, but the Speedport is very common. And the router config is not special (I only deactivated DHCP for the eBlocker individual mode).
- "Connect your Android via eBlocker Mobile (using OpenVPN)"
- For this, I need a little bit longer, but only switch to mobile solves the connection problems (but bypass eBlocker). I'll try it later.
My current understanding (and I may be wrong) is that the Android device thinks the Speedport router is the main IPV6 gateway. This is because the Speedport router basically offers an IPV6 gateway and so does eBlocker.
The strange thing is that the Android device only goes directly through the Speedport hardware router when eBlocker is active for the device. If I deactivate eBlocker for the device, then it goes via the eBlocker gateway (see the traceroute above).
best regards
Josch
@josch, to me it looks like an issue with IPv6.
For testing this you can always go to https://ipv6.eblocker.org/
Then check whether you see eBlocker's IP or your Android device's IP there. According to your traceroute to google.com with eBlocker enabled, you should see eBlocker's IP on the page.
If you see eBlocker's IP and eBlocker is enabled for your device you should also see the eBlocker icon on the page. Is this the case?
Just to verify that this is an IPv6 issue: can you disable IPv6 on the Speedport? (I think you should also restart the eBlocker and re-connect your Android device to the WiFi after disabling IPv6.)
Then check whether you see eBlocker's IP or your Android device's IP there. According to your traceroute to google.com with eBlocker enabled, you should see eBlocker's IP on the page.
I see the eBlocker's IP, not the Android IP.
If you see eBlocker's IP and eBlocker is enabled for your device you should also see the eBlocker icon on the page. Is this the case?
Yes
The traceroute with activated eBlocker and Wi-Fi access:
traceroute to ipv6.eblocker.org (2a03:b0c0:3:d0::1a5f:f002), 30 hops max
Hop 1:
From p200300d5d72e88a0da3addfffeb8fb92.dip0.t-ipconnect.de (2003:d5:d72e:88a0:da3a:ddff:feb8:fb92), 2 ms
Hop 2:
From p200300d5d72e88a0628d26fffe849426.dip0.t-ipconnect.de (2003:d5:d72e:88a0:628d:26ff:fe84:9426), 6 ms
Hop 3:
From 2003:0:8702:a800::1, 25 ms
Hop 4:
*
Hop 5:
From 2003:0:1304:800d::2, 23 ms
Hop 6:
From 2001:41a8:600:2::396, 23 ms
Hop 7:
From 2a03:b0c0:fffe::68, 24 ms
Hop 8:
*
Hop 9:
*
Hop 10:
*
Hop 11:
*
Hop 12:
*
Hop 13:
*
Hop 14:
*
Hop 15:
*
Hop 16:
*
Hop 17:
*
Hop 18:
*
Hop 19:
*
Hop 20:
*
Hop 21:
*
Hop 22:
*
Hop 23:
*
Hop 24:
*
Hop 25:
*
Hop 26:
*
Hop 27:
*
Hop 28:
*
Hop 29:
*
Hop 30:
*
Traceroute complete: 30 hops, time: 18449 ms
Just to verify that this is an IPv6 issue: can you disable IPv6 on the Speedport?
No, this is not possible 🙁
Best regards
Josch
And to clarify, with activated Wi-Fi and activated eBlocker:
- I cannot ping google.com
- I cannot traceroute google.com
but
- I can ping ipv6.eblocker.org
- I can traceroute ipv6.eblocker.org
That's so strange.
Btw., a lot of other google services are not working: drive, news (discovery), partly photos. But I can use Google Maps - Strange...
Now, more strange because everything is working now.
Since I didn't make any config changes throughout the day (just kept switching the Android device between Wi-Fi and 5G), I have no idea what it is right now.
The only thing that has happened (which probably happens all the time) is that one IPv6 address has changed.
Ok, because I couldn't believe it, I switched to mobile and then back to Wi-Fi.
Now it's broken again. PingTools shows me the hardware router as Gateway (fe80::1 - speedport router) and not eBlocker.
I checked the ipv6table (via diagnostics export) and the new IP is existing, and I see no to between older diagnostics.
But the android device thinks, the IPv6 gateway is still fe80::1. That's not good, I think.
Ok, in the meanwhile (since I wrote the last reply), the Gateway IPv6 address switched to eBlocker (fe80::da3a:ddff:feb8:fb92). The IPv6 address of the android device is still the same (from the last switch to Wi-Fi).
No changes in the ipv6tables.txt (only the header with timestamp and statistics)
But...
... still no connection to google.com - traceroute runs directly to the hardware router.
Only for curiosity, I restarted eBlocker. The Android device is still configured with the eBlocker (fe80::da3a:ddff:feb8:fb92). So, no switch back to (fe80::1 - speedport router).
Unfortunately, the issue is still existing.
First of all: We've discussed your issue in yesterday's supporter meeting. No one using Android has experienced something similar - even with speedport routers where IPv6 is always active. So for sure it's a very unique configuration/setup issue in your case.
Traceroute from Android Device to google.com with Wi-Fi (eBlocker deactivated for this device):
traceroute to google.com (142.250.203.206), 30 hops max Hop 1: From dnscheck.eblocker.org (192.168.2.172), 9 ms Hop 2: From speedport.ip (192.168.2.1), 8 ms
I wonder if you accidentally mixed up the traceroutes. Otherwise I have no idea why the traffic is routed via eBlocker but you claim eBlocker is de-activated. 🤔
Just for your tech background:
- FE80:... is an IPv6 local address which is always assigned to a devices with an IPv6 stack even if no IPv6 router is in place. Why your Android sets this address as Gateway is strange. Sounds like a bug to me.
- Ping uses ICMP (not TCP). Traceroute uses TCP. So ping is a completely different thing - not very useful for the tests here as traceroute shows everything.
Now to my 2 cents:
How can I change the device (for testing) so that only simple domain blocking is active?
See https://eblocker.org/en/docs/devices/#7-toc-title
Choosing Domain Blocker for the device will deactivate HTTPS.
Try disabling pattern blocker for just your device (as documented) and REBOOT all your devices afterwards. I'd wonder if the problem persist then.
Another thing to try: add "google.com" (without the quotes) as Trusted Website (under Settings-HTTPS> Tab Trusted Websites). Then eBlocker is disabled when you visit the domain. I'd wonder if the problem persists then.
If the issue still exists I would investigate further in LTE off mode only as this seems to interfere somehow. And then re-run all tests discussed here to have a clear test environment with no changes...
Hello @benne
I truly appreciate the fact that my very strange problem is still being followed up. It is probably a chain of unfortunate connections (or lack of connections 😆). I can understand that this is all really strange.
I'm aware of the difference between traceroute and ping, but if traceroute doesn't work, ping doesn't work either. Furthermore, I once read up on fe80:* and fe80:1, and there are good texts on this.
It's therefore strange, that I'm able to reach plenty of websites (in general pure IPv4), but all websites that do not work always have an IPv6 DNS record. Only very few sites with IPv6 still work, one of them is ipv6.eblocker.org - and not ipv6.google.com
Why your Android sets this address as Gateway is strange. Sounds like a bug to me.
I think, this is the root of evil. Maybe it's a shortcut for Android to look quick around for the next hop. The PingTools are very helpful to follow, what is happening.
- Switch from LTE to Wi-Fi
- Android Device still runs with both EUI-64 addresses (global & local)
- and uses fe80::1 to fetch a dynamic IPv6 with the global Telekom prefix (2003:*)
- In the meanwhile, eBlocker detects the new IP and adds this IP to the ipv6tables (sometimes together with the old one from a previous Wi-Fi connection, but the old one disappears after a while)
- After a while (I guess 5 to 10 minutes, maybe a TTL ends?) PingTools shows me, that the IPv6 gateway switched from fe80::1 to the eBlocker local IPv6 address.
- However, all the time, DHCP (v4), DNS1 (v6) and DNS2 (v4) pointing to eBlocker (in Wi-Fi mode)
The biggest issue is, I cannot disable IPv6 on the Speedport router (another good reason to buy a FritzBox). The next one is better to test for me: Set up another Android device. I have an old S8 pro and can try to reproduce it on this device. But it comes with a much older Android version. Maybe not comparable.
Try disabling pattern blocker for just your device (as documented) and REBOOT all your devices afterwards. I'd wonder if the problem persist then.
Ok, I can try it.
Another thing to try: add "google.com" (without the quotes) as Trusted Website (under Settings-HTTPS> Tab Trusted Websites). Then eBlocker is disabled when you visit the domain. I'd wonder if the problem persists then.
This is the default in my eBlocker:
If the issue still exists I would investigate further in LTE off mode only. And re-run all tests discussed here...
This led to my Wi-Fi being flagged as having no internet access at all (which was not correct because many websites were still accessible). Presumably because Android couldn't reach a check domain.
But I can try again.
best regards,
Josch
Try disabling pattern blocker for just your device (as documented) and REBOOT all your devices afterwards. I'd wonder if the problem persists then.
Ok, I changed the device in eBlocker to Domain Blocker only. Restarted smartphone. Unfortunately, the issue persists.
Then I also restarted eBlocker.
No change. Same issue.
But I misinterpreted the subdomains, and I'm now more confused. However, it looks like a broken ipv6 handling on the speedport router. Everything in direction to eBlocker looks like ok.
Here is the updated architecture (Android device in Wi-Fi mode):
So I'm desperate about the problem, and you can close the subject, and I'll sink into shame - eBlocker can't be the problem.
I'm just wondering why other people have no problems with the Speedport.
Maybe I'll kick the device and buy a good router...
A small update: My android switched from IPv6 to IPv4 (just like that, over lunchtime) and everything is working. The traceroute runs the IPv4 address with eBlocker and everything is fine.
However, this confirms more a routing issue with IPv6 with the Speedport router.
What you could theoretically try is to switch off eBlocker completely. Restart all devices and see if it all works with Speedport. But I won't be able to do that for the next few days.
@josch As said above there is a simple work-around which will cure the router's IPv6 nightmare: Always use eBlocker Mobile on you phone. Done.
THX!
Hi @random
As said above there is a simple work-around which will cure the router's IPv6 nightmare: Always use eBlocker Mobile on you phone. Done.
But this adds another additional complex config to an existing issue. (and yes, that was another function I wanted to integrate - but only if the network infrastructure is error-free)
I bought another DSL router from Amazon via 1-day delivery (a Fritzbox). I have now switched everything over in 2 hours. It works. The Speedport was the problem (or maybe Speedport + Pixel Android 14 + eBlocker - idk).
All devices in my network have been set up again and there are no problems with the 20+ devices. Two PCs, two notebooks, and two smartphones (one via HTTPS, the other "normal" only HTTP). My problematic smartphone via IPv6 (dual mobile/Wi-Fi) can now connect to IPv4 and pure AAAA IPv6 websites (including ipv6.google.com and ipv6.eblocker.org), all the Apps (running google services via IPv6) are working now fine.
So, everything works 🙂
I would really like to thank you all once again for listening and giving me ideas. I have learned a lot about eBlocker and especially about IPv6.
Best regards,
Josch
The Speedport was the problem (or maybe Speedport + Pixel Android 14 + eBlocker - idk)
Congats finding out.👏
Would you mind sharing the exact models of the devices (and maybe also OS version) so we can add this to the compatibility chart.
If you found our support valuable we'd appreciate your support as well - so we can support you in future... 👍😉
THX!
Hi @random
Would you mind sharing the exact models of the devices (and maybe also OS version) so we can add this to the compatibility chart.
The problematic Speedport Router (you'll get this as a rental offer in Germany with your VDSL account)
- Name: Speedport Smart 3,
- Firmware: 010137.5.1.001.0
- UI-Version: 2.13.213
- Boot-Version: 1.30.002.0000
- Hardware Version: 06
Android Smartphone
- Name: Pixel 6 pro
- Android 14 - June Update
The new router from AVM (working without any special IPv6 configuration):
- Name: Fritzbox 7530 AX
- Fritz OS: 7.81
- DSL-Version: B2pv6L047k.d28a
If you found our support valuable we'd appreciate your support as well - so we can support you in future... 👍😉
Of course, yes 🙂
best regards
Josch