AdguardTeam / AdguardTeam/CoreLibs

Cosmetic filtering doesn't work with wireguard running.

オープン
#1,732 コメント 31 件 リアクション 1 件 担当者 0 名 GitHub で見る
compatibility needs tech clarification Priority: P4
主要言語
言語のデータがありません
スター
52
フォーク
10
PR マージ指標
30日以内にマージされた PR はありません

説明

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

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

### AdGuard version

4.0.601

### Environment

```markdown
NA
```

### Root access

- [X] 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. Turn on automatic proxy filtering mode (root) in adguard.
2. Turn wireguard on (applies to both kernel mode and userspace mode).
3. Whitelist wireguard from adguard routing as advised for all such apps based on different vpn protocols.
4. Install adguard system certificate using magisk to enable https filtering in all apps.
5. Use apps, specifically browsers and the ones based on system webview.

### Expected Behavior

DNS, HTTPs and Cosmetic filtering should work in all apps on both IPv4 and IPv6 network as stated in redesigned nightly release notes with adguard correctly identifying which web request belongs to which app.

### Actual Behavior

Cosmetic filtering STOPS working in apps with filtering log showing all entries as DNS entries.

### Screenshots

_No response_

### Additional Information

I was about to file the issue earlier then suddenly found out that filtering starts working perfectly when IPv6 filtering is disabled in adguard advanced setting leading to completely disabling IPv6 in whole system. But this leads to network unstability within few minutes.

I also found that routing adguard dns filtering using another dns based app made the setup work as expected. The app has its several options including choosing between its own iptables or system iptables.

All these concludes that adguard root automatic proxy needs to make the iptable reconfiguring part more compatible with wireguard so that all features work just like they're supposed to work in automatic proxy mode as stated in release notes.

コントリビューションガイド

このリポジトリのコントリビューションガイドは索引されていません

評価

この issue はまだ評価されていません。

新しい issue をメールで受け取る

初心者向けの GitHub issue を短くまとめたダイジェスト。