New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
No Internet after switching connection type (wifi - > mobile and around) #852
Comments
I tried out a lot. nothing worked, i still need to restart my phone to get an internet connection after leaving wifi, entering wifi, switching from LTE to 3G, EDGE etc. any ideas? EDIT: |
Today I gave it another try and found out that the iptables flushing in my custom script is responsible for the behavior.
How can this happen? |
probably here is not the place for an answer or for help. |
Read the bug submission rules. I can't help without looking at what's happening with iptables. Kindly post the iptables rules ( from menu -> Show rules -> export or send error report ) and attach it here. I will look into it. |
I posted my rules in the first post. |
I can confirm this. Same problem here. After commenting these lines, it's working:
But then I'm facing OS restarts. 👎 I also have to remove these:
After that it's working fine. |
Try to premit access to the application called " (root) Application as root" |
I am using afwall donate on my Mi8, running Miui 10 under Android 8.1 rooted with Magisk 16.0 stable. Init.d is working and fix boot data leak is working as well (I think so - made the test with 00test)
For logging I am using Busybox.
Afwall+ is not working great at this time.
If I am switching from wifi to mobile data (or the way around) everything is blocked and I need to reboot my phone, than it is working. By applying the rules by hand (even turning firewall off and on again) there is still no connection.
I don't know if I should write it here - the logs are stopping all the time, I need to turn logs off and on for having logs again.
And one side question: by choosing to apply the rules after a certain amount of time after start, within this time everything is blocked, right? I didn't find any description for this feature
IPv4rules.log
The text was updated successfully, but these errors were encountered: