-
Notifications
You must be signed in to change notification settings - Fork 454
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
USB/Bluetooth Tethering fails on CM11 mako #257
Comments
Hi. Same issue on Samsung Galaxy S3 with AOSB KitKat 1.3.2 ROM.
Regards. |
Hi, USB tethering is not working for me also. Samsung S4 mini, CM11 M9, AFWall+ (v1.3.3) from F-Droid. For me WLAN tethering works without problem when Tethering (DHCP+DNS services) is allowed. Using same firewall rules USB tethering is not working. To be able to get DHCP address on a PC which is connected to my mobile I have to turn on Applications running as root (uid 0), DNS is not working unless I disable firewall. I even tried to enable Linux kernel (uid -11), but it just does not work. I can send logs, configuration or anything that is needed to resolve this issue. Kind regards, Edit: Just installed version 1.3.4 from F-Droid. It seems that problem remiains the same, did not tested thoroughly, if needed i can do it later. |
Same problem here on cm11. I'm getting a popup that says either of these two:
When I view the log, it says although I've allowed
Sorry for incomplete comment, ctrl+enter seems to submit the issue :( Wifi tethering works fine.. |
With AFWall (latest 1.2.9) turned on, the DHCP Service of the Android Device is blocked. Tethering is possible with static address. Incoming DHCP requests reach dnsmasq on Android, but the answer is blocked (Information collected with logcat and dhcpdump). Tethering, kernel, root apps and adb is turned on.
Interface tethering (Android): usb0
Interface inet (Android): wlan0
In AFWall Log it says during trying dhcp, that it blocked Packages to AppID:0 (Root), but this category is allowed for both wifi and 3g (Does it maybe need to be allowed for usb0 , which is not in the gui?).
Output of "iptables -L" for no firewall (working (iptnfw)) and with afwall turned on (not working (iptfw)) is presented.
iptnfw:
The text was updated successfully, but these errors were encountered: