Skip to content
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

No host being sent to upstream.proxy #794

Closed
Fndroid opened this issue Nov 30, 2020 · 4 comments
Closed

No host being sent to upstream.proxy #794

Fndroid opened this issue Nov 30, 2020 · 4 comments

Comments

@Fndroid
Copy link

Fndroid commented Nov 30, 2020

Steps to reproduce

  1. set upstream.proxy to a socks5 server
  2. do some network fetching

Expected behavior

dst.addr as a domain should be read from socks5 packet

Actual behavior

dst.add is now an IP address even if I do a domain fetch

Screenshot:

Customer ID

Your environment

  • macOS big sur 11.0.1
  • adguard for mac 2.5.1.928 release (CL-1.7.150)
@sfionov
Copy link
Member

sfionov commented Nov 30, 2020

Since DNS name is already resolved by browser before it intercepted by AdGuard, it is complicated and requires workaround (fake DNS server).

However, I created feature request in our filtering engine, you may track this issue there:

AdguardTeam/CoreLibs#1386

@Fndroid
Copy link
Author

Fndroid commented Nov 30, 2020

But I can find domains in the logs printer. Why's that?

@sfionov
Copy link
Member

sfionov commented Nov 30, 2020

AdGuard detects domain name in first packets of connection but this happens after connection is already established

@Fndroid
Copy link
Author

Fndroid commented Nov 30, 2020

Thank you for your patience and responses.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants