Filtering Log shows most of traffic that is explicitly allowed by the User Filter without the green background color

[SergeiShir]

After the latest upgrade, I encounter the following issue:
Most of the traffic that my User Filter allows is shown without a background color (and as "Status = Processed") instead of the green background (and as "Status = Whitelisted"). There is no apparent pattern - this issue occurs for different User Filter rules - rules for DNS connections, rules for connections from specific apps, rules for URL connections.
However, the traffic that is explicitly blocked the User Filter, is still always shown with the red background color.

Steps to reproduce

1. Open an app, or browse to some sites to initiate connections that are explicitly allowed by the User Filter.
2. Open Filtering Log.
3. Most of these connections are shown without a background color - when you open such log entries, it shows "Status = Processed" + "Filter Name = User Filter".
4. There are still connections that are shown with the green background - such log entries show "Status = Whitelisted" + "Filter Name = User Filter".

Expected behavior

All connections that are explicitly allowed by the User Filter should be shown as green

Actual behavior

Most of the allowed connections are shown without a background color

Screenshot:

Will be attached shortly

(1 of 2) Example of allowed connections that are shown without background color:

(2 of 2) Example of an entry:

Customer ID

Premium 1146569

Your environment

• Adguard version: 3.0.195n (1.3.94cl)
• Adguard filtering mode: VPN
• Device model: Google Pixel 2 XL
• Operating system and version: stock Android 9, security patch 05 Jan 2019
• Rooted or not? Not rooted
• Any other apps that can start VPN/Antiviruses/Cleaners etc. installed? No

Logs and Settings

adguard_logs_3.0.195_27Jan_09h30m.zip

[ameshkov]

@SergeiShir you have this issue with DNS requests only, right?

[SergeiShir]

Mostly with DNS rules, but also with rules for specific apps and with rules for URLs.

…

On Mon, Jan 28, 2019, 08:56 Andrey Meshkov ***@***.*** wrote: @SergeiShir <https://github.com/SergeiShir> you have this issue with DNS requests only, right? — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#2474 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AQ_2qOoQvIkLBZ58mnOrLzfD34yaXjUsks5vHp8UgaJpZM4aUmDz> .

[ameshkov]

@Revertron I guess it's caused by the CL 1.3 pull request you were implementing, please take a look.

Try unblocking requests from the filtering log to reproduce the issue.

[lancelot-moon]

This is actually duplication with mine.
Some whitelisted requests are correctly shown as "whitelisted", but others are not so (only processed).
#2471

Because AG think they're only processed requests, some whitelisted requests are without the light green background.

[SergeiShir]

Just upgraded to the latest Nightly.
The situation is much better (~85% are whitelisted as expected), but still there are many missed (just processed).
See the attached logs.

[Removed logs link for privacy reasons]

[ameshkov]

@SergeiShir plz send logs to devteam@adguard.com next time, it might be not okay to share the file here

[ameshkov]

@SergeiShir could you please show or describe a couple of examples of such wrongly "processed" requests?

[SergeiShir]

Can you GREP the attached logs for these 2 conditions?
Status = Processed
AND
Filter name = User Filter

If not, let me know...

[ameshkov]

Well, the filtering log events aren't written to the log file, the data there is raw. So the question is which requests representation in the filtering log is wrong.

[SergeiShir]

As requested, I sent the new log files to devteam email
Subject = Files for GitHub bug 2474
Sent = 17:34 GMT+2

I attached 2 sets of logs together with screenshots from the Filtering Log that show the problematic entries