-
Notifications
You must be signed in to change notification settings - Fork 455
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
Version 2.6.0 and 2.6.0.1 not allowing WiFi #591
Comments
Please post iptables rules. |
Can confirm. Just reverted to 2.5.2, rewrote iptables rules and it worked again. |
@vestingz Thank you so much for confirming. That's exceptionally helpful. Did you revert to 2.5.2 via F-Droid? When I tried to do that, it issued a severe warning about potential data loss, and given that AFWall+ is a root app, I didn't want to mess anything up. Any troubles with reverting? @ukanth Can you imagine any troubles with reverting from 2.6.0 to 2.5.2 via F-Droid? |
It should not, I need logcat/iptables rules to look at |
@Gitoffthelawn No, neither WLAN nor mobile worked so i downloaded the apk to my lap and manually installed 2.5.2 after uninstalling 2.6.0. |
@Gitoffthelawn No, before. sorry for being unclear. It seemed like the iptables of 2.6.0 allowed outbound traffic only on both adapters as Network Log recorded. Unfortunately i didn't save any logs, sorry. |
@Gitoffthelawn , I have not received any report. Please send it again. Also try to catch this output as well iptables -S ( in console) and send it to me. |
@Gitoffthelawn , May I know to which email id you are sending these emails. Because I'm not getting those. |
Yes, you may. :) I sent the first one to cumakt+afwall@gmail.com and the second to cumakt+github@gmail.com, so they should have both gone to cumakt@gmail.com |
Nope, not by email, but got it via the above link. it seems password protected. |
Spent a couple hours performing some experiments. Here's a summary of what I learned:
|
@Gitoffthelawn, Unfortunately I can't open the zip with the hint you provided. Also I tried reverting the change which might have caused this issue, purely based on my guess. If you can test this, would be great. @vestingz .. https://www.dropbox.com/s/rm6v7xurvna63fw/AFWall%2B%20TEST%202.7.0.apk?dl=0 |
@Gitoffthelawn , looks like you have spelled it wrong or I have some other firstname/lastname. I tried all combinations ! |
@Gitoffthelawn , Since you have uploaded the service which encrypts the zip, the password doesn't seems to work. |
@ukanth My apologies; the file definitely had an issue. Try this: http://dropjar.com/#1mqaazi6 This issue was getting cluttered, so I cleaned up what I could. You may desire to do the same. |
@ukanth Thanks for the link :) I will test within the next days. |
@vestingz Pastebin has been overloaded and was only showing this: http://pastebin.com/i/503.jpg What's "equal"? Do you have a url? |
@Gitoffthelawn paste.ee | 0bin.net | pastie.org | nopaste.me just to name a few. |
I have similar problem, I am not sure if it's the same or not. Have an UMI Zero phone with KitKat, I flashed a custom CyanogenMod rom on it (Lollypop), but I had problems with connecting to wifi networks. I used the newest stable release of afwall+ on it. I thought it's a bug in the rom, and after one month I flashed the original official rom (a fresh new install, not a backup file). Had the same issue, even though I tried a dozen of roms and configuration on it. I gave up, thinking that it must be a hardware problem. Now I got a Huawei P8 Lite phone (Android 6 Marshmallow). The wifi worked fine, even after unlocking the bootloader and rooting the phone. However after I installed the newest afwall+ from F-Droid, the wifi stopped working, showing the same symptoms as my UMI. Disabling afwall, downgrading or removing didn't help. I had a full backup of the working state of the system (with TWRP), restoring the backup didn't help either. I also tried to remove all iptable rules from terminal with the commands I found here: https://www.digitalocean.com/community/tutorials/how-to-list-and-delete-iptables-firewall-rules (The 'Flush All Rules, Delete All Chains, and Accept All' section). Mobile data works fine. Is there anything afwall+ may changed in the core system settings which could "survive" after factory reset or installing new roms? I heard that some system apps may try to ping google servers, and if they can't, some wifi networks may be blocked as it doesn't provide internet connection. I used afwall in "allow selected" mode, system processes were blocked too. (However enabling them didn't solve my problem.) I also try to use my Android without Google Account: Play Store, Youtube, GMail, Drive and other GApps are frozen with Link2sd. (I used my UMI for a year this way, and didn't have problem with wifi.) If you think that my problem is related to this issue, feel free to ask for logs or anything. I also appreciate any help or suggestion. |
This should be addressed in the latest release. Please feel free to reopen if required. |
Upgraded from v2.5.2 to v2.6.0 (F-Droid) on a KitKat device. WiFi and cell data working as expected with v2.5.2. With v2.6.0, cell data works perfectly, but WiFi gets no response.
Before I spend hours trying to figure it out (already spent 1 hour!), any idea why this would happen? No other changes made beside upgrading F-Droid to v2.6.0 and rebooting.
The text was updated successfully, but these errors were encountered: