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

Proxy IP no longer listed as "Remote address" #3562

Closed
infinitewaveparticle opened this issue Aug 30, 2020 · 4 comments
Closed

Proxy IP no longer listed as "Remote address" #3562

infinitewaveparticle opened this issue Aug 30, 2020 · 4 comments

Comments

@infinitewaveparticle
Copy link

Issue Details

  • AdGuard version:
    • 4.0 Nightly 1 **
  • Filtering mode:
    • Local VPN
  • Device:
    • Kindle Fire HD 10 7th Edition*
  • Operating system and version:
    • Android 5.1.1 *
  • Root access:
    • No

*Note: I've also noticed this happening on Samsung Galaxy phones too (running Android 7 & 8)
**Note: This bug has been happening since 3.5 RC 1.

Expected Behavior

AdGuard should list the proxy's IP and port as the remote address. It should also be sure to route traffic thru the proxy server.

Actual Behavior

Although checking my IP address still shows the proxy to be functioning properly, the "Remote address" portion of the filtering log now acts as if no proxy is enabled even though mine is enabled and apparently working. It instead lists the IP address of the server it's connecting to, as well as its port (usually 443 or 80). In versions prior to RC 1 my proxy server was always listed as the Remote address. Also, the occasional tcp tunnel that usually showed as connected to my proxy server now shows it connecting to the IP address of the website/server. See screenshots.

Screenshots

Screenshot:

proxyNotRemoteAddressBug

proxyNotRemote_and_tcpBug

Additional Information

I have logs saved of this happening. I am sending to devteam@adguard.com. Also, for some reason, in Github Issues there is no reply option for me... so this may be the only post I can make on this thread. Hopefully switching to a different browser will fix this.

@stale
Copy link

stale bot commented Oct 31, 2020

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the Wontfix label Oct 31, 2020
@stale stale bot closed this as completed Nov 7, 2020
@zzebrum
Copy link
Contributor

zzebrum commented Nov 26, 2020

@infinitewaveparticle is the problem still reproducing?

@sfionov
Copy link
Member

sfionov commented Nov 27, 2020

This is expected behavior, displaying outbound proxy IP:port in destination address was a bug.
However, I've created feature request in CoreLibs: AdguardTeam/CoreLibs#1385

@infinitewaveparticle
Copy link
Author

infinitewaveparticle commented Nov 28, 2020 via email

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

5 participants