search

AdguardTeam / AdGuardVPNForWindows

AdGuard VPN Windows app open bug tracker
https://adguard-vpn.com/
86 stars 6 forks source link

ssh client on the WSL #603

Open Lufan opened 9 months ago

Lufan commented 9 months ago

Issue Details

Hello. I'm having an issue that when I enable the VPN, the SSH tunnel doesn't get established (ssh: connect to host xx.xx.xx.xx port 22: Connection timed out). It's also not possible to select \wsl.localhost\Ubuntu\usr\bin\ssh as an excluded application.

This seems like a strange case - but is it possible to solve this somehow?

Proposed solution

No response

Alternative solution

No response

AlexandrPkhm commented 8 months ago

Hi @Lufan

In order to troubleshoot the issue, we need to better understand your current use case. Can you please provide the steps to reproduce for this particular issue?

AlexandrPkhm commented 8 months ago

@Lufan

Could you please let us know if there is any news on this issue?

Lufan commented 8 months ago

Hi @AlexandrPkhm, sorry for late response. Steps to reproduce:

  1. AdGuard VPN enabled; image

  2. create EC2 instance on the AWS and save SSH keys on the local machine, where installed Windows 11 as OS and WSL2 as a OS component;

  3. navigate to the AWS console and allow access to 22 from IP address used by VPN; image

  4. open WSL2 console and try to create SSH session to created EC2; (ssh -i ~/.ssh/name_of_private_key.pem ubuntu@addrs_of_server)

expected result - session established successfully; actual result - ssh return error ssh: connect to host xxx port 22: Connection timed out

next if disable VPN and change on the AWS console allowed IP address then SSH session successfully established and works;

p.s. when writing answer then i understand that WSL2 console - fully ignore enabled VPN and connecting to internet using my real IP - this is reason that SSH session not established as i added to allow list IP address from VPN.

this issue can be closed then. Sorry for wrong issue