Skip to content

Sharing WSL2's ligolo-ng Tunnel with Windows Host: Alternative to SOCKS Proxy? #152

@Byxs20

Description

@Byxs20

I'm currently using WSL2 as a proxy machine. After WSL2 successfully connects to Agent1 and runs autoroute + tunnel, is there any way to allow the Windows host to directly utilize the TUN interface created in WSL2?

I attempted to join Windows as Agent2 to the ligolo-ng proxy started by WSL2, but could not ping internal network services routed through Agent1 (e.g., ping 192.168.1.100 fails). As a workaround, I launched a SOCKS proxy using gost inside WSL2 for Windows to access internal services.

Is there a more direct/native method to:

  1. Bridge WSL2's TUN interface to Windows?
  2. Or configure route-sharing between the WSL2 agent (Agent1) and Windows host (as Agent2)?

Appreciate any insights to avoid proxy chain latency!

Metadata

Metadata

Assignees

No one assigned

    Labels

    questionFurther information is requested

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions