Local Proxy Mode does not work with KernelSU root

[L4Ph]

Please answer the following questions for yourself before submitting an issue.

• I am running the latest version
• I checked the documentation and found no answer
• I checked to make sure that this issue has not already been filed

AdGuard version

4.0

Environment

- OS:Android13
- Device:Pixel6a
- Firmware:

Root access

• Yes, I have it.

What filters do you have enabled?

No response

What Stealth Mode options do you have enabled?

No response

Issue Details

Steps to reproduce:
1.Install KernelSU on your device
2.Grant root privileges to Adguard for Android using KernelSU Manager
3.Open Adguard → Go Settings→Filler→Network

Expected Behavior

Local Proxy can be used while giving root.

Actual Behavior

It's looping without opening.

Screenshots

Screenshot 1:

Additional Information

It works fine in v3.x.
It also works in Magisk, so I think it is an implementation issue in v4.x

[Versty]

@Katsuyuki-Karasawa Hi. Thank you for the feedback.
In order to investigate this issue, we would like to take a look into the logs from your device. Please follow the steps below.

1. Enable debug logging:
   Settings -> General -> Advanced -> Logging level -> Debug

2. Reproduce the issue, then remember the exact time when it happened

3. Collect logs:
   Settings -> General -> Advanced -> Export logs and system info

4. Sent this file to devteam@adguard.com:

   • mention the 4579 number in the subject
   • specify the exact time when the issue occurred

[Versty]

@Katsuyuki-Karasawa Did you send the logs?

[Versty]

@Katsuyuki-Karasawa Also, the system bug report would be useful in this case.

The issue is closed due to inactivity. Please reopen if you find some time to send us the files requested above.

[LordArrin]

Same bug with kernelsu on android 14, poco f3.

[LordArrin]

adguard_logs_4.2.118_1412_044107.zip

[LordArrin]

@adguard-bot help

[sfionov]

@LordArrin According to your log, DNS protection cannot start. This might happen when firewall restricts binding to 127.0.0.1, or when lo interface is down. Can you please try without DNS protection?

[LordArrin]

@LordArrin According to your log, DNS protection cannot start. This might happen when firewall restricts binding to 127.0.0.1, or when lo interface is down. Can you please try without DNS protection?

Yeah, without dns all works fine.