-
Notifications
You must be signed in to change notification settings - Fork 446
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
[ISSUE] [REGRESSION] tethering is broken by default in 3.5.3 #1297
Comments
I can confirm this on a different device. AFWall+ version is 3.5.3, AFWall+ Unlocker is 1.0.5, both installed from Aurora Store.
Workaround with Tether control rule group enabled works, and DNS works for WiFi tethering. I didn't enable logs before applying the Tether control rule group workaround, so no logs with this error. If someone really need them, I'm willing to revert the workaround and collect logs, but I don't see the point as they are being collected by another user. |
Can confirm this. I run AFWall on block-all-except-allow mode, and merely enabling this setting works to fix tethering. That is, I don't have to select anything in the column, everything is unchecked implying that everything is being blocked, including for the "All apps" row. Merely enabling "Tether control" as described in the OP, works to allow other phones to connect to this phone's WiFi hotspot. |
Same here with Sony XZ1C running lineage os 19.1., AFWall+ 3.5.3. Wifi tethering isn't working until I enable "tether control". In the System info section of the exported rules file I see tethering info changes from:
to:
|
Correction, bluetooth tethering seems to be broken until I explicitly check this new column for the "(tethering) - DHCP+DNS services" core app. |
Describe the bug
3.5.3 blocks DNS for tethering unless it's explicitly allowed via Preferences -> Rules/Connectivity -> Tether control rule group.
3.5.2.1 and prior versions allowed tethering without need to set thether rules up explicitly.
Firewall Logs
3.5.2.1
3.5.3
Smartphone (please complete the following information):
Additional context
Was also reproduced on other devices with LOS 18.1
The text was updated successfully, but these errors were encountered: