What is affected by this bug?
My Android rooted devices (no matter the Android version)
When does this occur?
- The device boot up with dnscrypt-proxy installed on it.
routes are configured with 2 relays at least.
skip_incompatible = true.
- Wi-fi connection disabled.
- Data connection only.
Where does it happen?
How do we replicate the issue?
On a Android rooted device with Magisk installed:
- Disable Wi-fi connection.
- Enable data connection.
- Download my latest module release.
Magisk > Modules > Install from storage > dnscrypt-proxy-android-v2.1.1-1.zip.
- Reboot.
- Unlock the device (PIN and/or lock screen).
- See the issue happen: it take almost 10 minutes to initialize the connection and make the X sign under LTE icon disappear. (sometimes after 10 minutes the connection isn't initialized yet).
Expected behavior (i.e. solution)
The device should connect immediatly, just like under wi-fi only network.
Solution 1: I found useful (but again in random ways) toggling on/off the airplane mode.
Solution 2: I found usefull toggling on the wi-fi connection. At this point the dnscrypt-proxy initialize the connection almost immediatly and then I can use data connection as well if I switch back to it.
Solution 3: skip_incompatible = false (not considered due to the lose of the routes correct functionality)
Other Comments
dnscrypt-proxy.toml
Take logs was very difficult due to the fact that the issue happen randomly, happen on vacation for example.
At the actual state, with no-wifi connection, is an high risk use dnscrypt-proxy with this configuration.
log_level = 0
dnscrypt-proxy-wifi-only.log
dnscrypt-proxy-data-only.log
dnscrypt-proxy-data-only.jpg
What is affected by this bug?
My Android rooted devices (no matter the Android version)
When does this occur?
routesare configured with 2 relays at least.skip_incompatible = true.Where does it happen?
How do we replicate the issue?
On a Android rooted device with Magisk installed:
Magisk > Modules > Install from storage > dnscrypt-proxy-android-v2.1.1-1.zip.Expected behavior (i.e. solution)
The device should connect immediatly, just like under wi-fi only network.
Solution 1: I found useful (but again in random ways) toggling on/off the airplane mode.
Solution 2: I found usefull toggling on the wi-fi connection. At this point the dnscrypt-proxy initialize the connection almost immediatly and then I can use data connection as well if I switch back to it.
Solution 3:
skip_incompatible = false(not considered due to the lose of the routes correct functionality)Other Comments
dnscrypt-proxy.toml
Take logs was very difficult due to the fact that the issue happen randomly, happen on vacation for example.
At the actual state, with no-wifi connection, is an high risk use dnscrypt-proxy with this configuration.
log_level = 0dnscrypt-proxy-wifi-only.log
dnscrypt-proxy-data-only.log
dnscrypt-proxy-data-only.jpg