Blokada doesn't detect the current Netowrk properly

[PeterDaveHello]

Tested on Android 11/12 with Blokada v5.18.0(via F-Droid) (but I believe this problem exists for a while, not just v5.18.0).

Though there's a feature to let the users decide what config to apply to each network, however, Blokada frequently can't detect the network properly. Even though all the permission, including precise location was given.

For example, I'm now connected to a Wi-Fi network called: workstation, but Blokada only knows that I connected to Wi-Fi, doesn't know that the Wi-Fi SSID is workstation, even though I connected to another Wi-Fi called: Peter_AP, the result is the same. Just like the screenshot below:

Permission Screenshot	Connected WiFi Screenshot	Blokada Networks Screenshot

Blokada sometimes can detect my Wi-Fi SSID, properly. However, Blokada didn't choose the correct network to apply to the config frequently, the activated network easily goes to the "Any WiFi network", instead of the recognizable and connected W-Fi SSID.

Thankfully, killing(force stop) and restarting Blokada will help to detect the correct network, but it's no guarantee and not convenient, so this feature is kind of not working idealy I think.

The same problem is reported here:

• Android: VPN connection is occasionally lost (Blokada libre) #905 (comment) from @TomasRiker
• Android: VPN connection is occasionally lost (Blokada libre) #905 (comment) from @angrox

I didn't go through the whole issue list, but obviously, I'm not the only one who got this issue.

Please let me know how can we help, thanks ;)

[ikurek]

The same thing happens to me, on stock Android 12 (Pixel 5). At random my home WiFi is detected as "All Networks" instead of my SSID, which is really annoying because I want to use network DNS at home (PiHole setup). Resting blokada app usually makes it detect the network correctly, but after some time it still switches to "All Networks".

I'll try to investigate the logs if I have a moment, maybe that will give us more insight into the issue

[bluezed]

Same here with Android 11 and Blokada 5.20.2

My home network is frequently not recognised and so the "prefer network DNS" setting is not used and it falls back to the All Networks setting instead.

Clearing Cache fixes it for a little while but not for long. After a few hours it's randomly back to All Networks.

[weedy]

Ping.

Breaks youtube in annoying ways for me until I airplane mode a couple times.

[Dymstro]

I'm also having this issue on my Pixel 6 Pro running Android 12 and Blokada 5.21.0. I use an internal DNS server to access services like Home Assistant, which won't work until I force close and reopen the app

[JAAdrian]

Same here on Android 10 and Blokada 22.3.8. Nevertheless, this has been the "usual" behavior for the last 2 years.

For a short period, disabling network (e.g. WIFI) and re-enabling it will fix it and the correct network is detected. After some time, I can see the WIFI icon on top of the screen glitching and Blokada is back in "All Networks"-mode.

Let me know, if I can help and provide logs.

[kar]

Could anyone try if the newest release works better in this aspect? I made some relevant changes. https://github.com/blokadaorg/blokada/releases/download/android-v22.4.7/app-five-release.apk

[TomasRiker]

Could anyone try if the newest release works better in this aspect? I made some relevant changes. https://github.com/blokadaorg/blokada/releases/download/android-v22.4.7/app-five-release.apk

With the new release I'm still facing the same problems.

[JAAdrian]

Hi all,

same here for me (Android 10). Can I contribute logs or something like that?

[JAAdrian]

Actually, what would fix the need for network settings for me alltogether would be a default setting to always use the network's DNS and be in libre mode, as I usually only use the (ad-)blocking feature.

Is that somehow possible?

[Lotus815]

Related: #933 #952 #959