PowerShell / PowerShell/Win32-OpenSSH
Windows 10 ssh Doesn't support TUN tunneling even if we add a TAP-Windows adapter
Open
@tgauth is already working on this.
Since Oct 16, 2023.
Issue-Upstream Parity
- Dominant language
- No language data
- Stars
- 8.3k
- Forks
- 819
- PR merge metrics
- No merged PRs in 30d
Description
Prerequisites
- Write a descriptive title.
- Make sure you are able to repro it on the latest version
- Search the existing issues.
Steps to reproduce
Windows 10 ssh Doesn't support TUN tunneling. (No. 3. in this issue: https://github.com/PowerShell/Win32-OpenSSH/issues/1647)
We add a TAP-Windows adapter:
C:\Program Files\OpenVPN\bin>tapctl create --name tap102
{A2A21221-9F22-46B1-A430-FE9F4CD6D1B5}
C:\Program Files\OpenVPN\bin>tapctl list
{236FF470-24C2-4B57-B09C-EDECCAF70A7B} OpenVPN Wintun
{F4FFDCC0-6FD0-40DC-A32B-6A783217AE3F} OpenVPN TAP-Windows6
{A2A21221-9F22-46B1-A430-FE9F4CD6D1B5} tap102
C:\Users\User name>ssh -w 102:102 username@hostname
Tunnel interfaces are not supported on this platform
Tunnel device open failed.
Could not request tunnel forwarding.
Expected behavior
OpenSSH should support TUN interfaces on Windows.
Actual behavior
Tunnel interfaces are not supported on this platform.
Error details
No response
Environment data
C:\Users\informatika\.ssh>powershell $PSVersionTable
Name Value
---- -----
PSVersion 5.1.19041.1023
PSEdition Desktop
PSCompatibleVersions {1.0, 2.0, 3.0, 4.0...}
BuildVersion 10.0.19041.1023
CLRVersion 4.0.30319.42000
WSManStackVersion 3.0
PSRemotingProtocolVersion 2.3
SerializationVersion 1.1.0.1
Version
OpenSSH_for_Windows_9.4p1, LibreSSL 3.7.3
Visuals
No response
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.